summaryrefslogtreecommitdiff
path: root/test/language
Commit message (Collapse)AuthorAgeFilesLines
* Add optional chaining testsMaximilian Goldstein2021-04-1338-0/+1131
| | | | | Change-Id: Ia87313a2756dfbc3d90128ac77cd4dc6c8c137df Reviewed-by: Ulf Hermann <ulf.hermann@qt.io>
* test/language/expressions: Add nullish coalescing testsMaximilian Goldstein2019-12-0424-0/+1360
| | | | | | | | | Copies a few tests for nullish coalescing straight from the newest test262 master branch so that we can test https://codereview.qt-project.org/c/qt/qtdeclarative/+/283241 . Change-Id: I312e96c1e2934d2933421371d58bfce670f244ae Reviewed-by: Ulf Hermann <ulf.hermann@qt.io>
* numeric literal seperators: test change in CodePoint production (#1464)Valerie2018-02-285-0/+274
|
* Add test for eval-in-function template tags (#1457)Daniel Ehrenberg2018-02-271-0/+35
| | | Thanks to Caitin Potter for highlighting this test case.
* Revert "Additional tests for QuantifiableAssertion" (#1458)Leo Balter2018-02-2612-220/+0
|
* Merge pull request #1456 from littledan/quantifiedassertionDaniel Ehrenberg2018-02-2612-0/+220
|\ | | | | Additional tests for QuantifiableAssertion
| * Additional tests for QuantifiableAssertionDaniel Ehrenberg2018-02-2612-0/+220
| | | | | | | | | | | | | | | | | | | | | | | | - Tests that lookahead and lookbehind are not extended to QuantifiableAssertion, as in https://github.com/tc39/ecma262/pull/1102 - Additional tests verifying some more combinations of cases for QuantifiableAssertion being invalid in Unicode mode. Based on the tests in https://chromium-review.googlesource.com/c/v8/v8/+/926102 These tests pass on V8 (if the throw for early errors is removed to work around a V8 issue where RegExps don't have early errors).
* | async-iteration: move existing throw/return tests to AsyncGeneratorPrototype dirValerie R Young2018-02-2215-794/+0
| |
* | async-iteration: add esid for 'esid: pending' testsValerie R Young2018-02-2235-37/+214
|/
* Add tests for the behavior of INT32_MIN (-2147483648) as exponent with the ↵Jeff Walden2018-02-141-0/+18
| | | | exponentiation operator and with Math.pow (which shares the same core algorithm in the spec, but might be differently implemented in actual implementations). (#1445)
* Fix typo intialize(r) -> initialize(r)Adrian Heine2018-02-1264-64/+64
|
* Prefer spaces to tabs if it is not syntax related testsYusuke Suzuki2018-02-087-7/+7
| | | | This patch changes tabs to spaces for newly added tests.
* features: [numeric-separator-literal]Rick Waldron2018-02-0852-0/+74
|
* Revert "Revert "Tests for NumericSeparatorLiteral. Closes gh-1051" (#1188)"Leo Balter2018-02-0852-0/+1466
| | | | This reverts commit 8422147c17aa3f4061e524a8f88c251a3b371ecf.
* Test for change to cache templates by site, not contents (#972)Daniel Ehrenberg2018-02-0512-54/+159
| | | | | | | | | | | | | | * Test for change to cache templates by site, not contents These tests are against a specification change based on discussion in https://github.com/tc39/ecma262/issues/840 The tests here passed on SpiderMonkey but failed on other implementations, which implement the current specification. * Add a test that caching is by source location, not function identity * Update existing tests to reference the spec properly
* Merge pull request #1404 from jugglinmike/refactor-for-parsers-functionLeo Balter2018-02-0553-182/+260
|\ | | | | Refactor function literal tests for parsers
| * Refactor function literal tests for parsersMike Pennisi2018-02-0348-182/+260
| | | | | | | | | | | | | | | | | | A number of tests for the parsing of function literals were expressed using `eval`. This made the tests more complex than necessary and also prevented the tests from providing value to ECMAScript parsers. Remove the use of `eval` in the relevant tests and instead express the expectations with literal source text.
| * Improve file namesMike Pennisi2018-02-0350-0/+0
| |
* | Fix typo in comments (Standart -> Standard)Zirak2018-01-297-7/+7
|/
* Refactor object initializer tests for parsersMike Pennisi2018-01-2517-79/+105
| | | | | | | | | A number of tests for the parsing of object initializers were expressed using `eval`. This made the tests more complex than necessary and also prevented the tests from providing value to ECMAScript parsers. Remove the use of `eval` in the relevant tests and instead express the expectations with literal source text.
* remove unnecessary method syntaxJosh Wolfe2018-01-2512-108/+108
|
* Order of evaluation tests for infix numeric operatorsJosh Wolfe2018-01-2512-0/+1658
|
* BigInt and Number type mismatch tests for infix operatorsJosh Wolfe2018-01-2512-0/+385
|
* Remove duplicate esidsAndré Bargull2018-01-257-7/+0
|
* Remove unused includesAndré Bargull2018-01-252-2/+0
|
* Update remaining tests to use 'parse' instead of 'early' error phaseAndré Bargull2018-01-259-9/+9
|
* Rename sec-delete-operator test, mark non-obvious syntaxRick Waldron2018-01-171-6/+13
|
* fixup! Refactor DeleteExpression tests for parsersMike Pennisi2018-01-171-0/+2
|
* Refactor DeleteExpression tests for parsersMike Pennisi2018-01-1729-452/+48
| | | | | | | | | | | | A number of tests for the parsing of the DeleteExpression production were expressed using `eval`. This made the tests more complex than necessary, and also prevented the tests from providing value to ECMAScript parsers. Remove the use of `eval` in the relevant tests and instead express the expectations with literal source text. Remove superfluous tests which only differed in the runtime semantics of source text that could not be evaluated due to syntax errors.
* Frontmatter: updates to ForIn/OfBodyEvaluation testsRick Waldron2018-01-113-9/+40
|
* Fix: various lint fixesRick Waldron2018-01-114-4/+4
|
* Fix: various lint fixesRick Waldron2018-01-1013-13/+21
|
* Fix: esid sec-runtime-semantics-classdefinitionevaluationRick Waldron2018-01-101-1/+1
|
* Fix: esid sec-generator-function-definitionsRick Waldron2018-01-108-16/+8
|
* Fix: es6id -> esid sec-additional-syntax-numeric-literalsRick Waldron2018-01-102-2/+2
|
* Fix: es6id -> esid sec-html-like-commentsRick Waldron2018-01-105-5/+5
|
* Fix esid: static-semantics-hasproductionintailposition => ↵Rick Waldron2018-01-1028-28/+28
| | | | sec-static-semantics-hascallintailposition
* Resolving conflicts in class-fields src templatesRick Waldron2018-01-058-12/+16
|
* Rename negative test "phase" for module resolutionMike Pennisi2018-01-056-6/+6
|
* Rename negative test "phase" for parsingMike Pennisi2018-01-052101-2101/+2101
| | | | | | | | | | | | | | Early errors may result from parsing the source text of a test file, but they may also result from parsing some other source text as referenced through the ES2015 module syntax. The latter form of early error is not necessarily detectable by ECMAScript parsers, however. Because of this, the label "early" is not sufficiently precise for all Test262 consumers to correctly interpret all tests. Update the "phase" name of "early" to "parse" for all those negative tests that describe errors resulting from parsing of the file's source text directly. A forthcoming commit will update the remaining tests to use a "phase" name that is more specific to module resolution.
* Infix operator ToNumeric coercion tests for BigInt operandsJosh Wolfe2018-01-0536-0/+4979
|
* Frontmatter: fixup "description: |" to "description: >"Rick Waldron2018-01-051-1/+1
|
* Frontmatter: fixup "info: >" to "info: |"Rick Waldron2018-01-051392-1391/+1391
|
* Restore & update existing static class field cases/templatesRick Waldron2017-12-218-0/+144
|
* Remove static private/public fields unsupported tests.Rick Waldron2017-12-212-21/+0
|
* Add tests that public and private static fields are unsupportedDaniel Ehrenberg2017-12-212-0/+21
|
* Regenerate testsDaniel Ehrenberg2017-12-21222-11407/+48
|
* Remove static fields testsDaniel Ehrenberg2017-12-216-264/+0
| | | | | | Static fields were broken up from instance fields and demoted to Stage 2 in the November 2017 TC39 meeting. This patch removes the test262 tests which test static class fields.
* Merge pull request #1375 from jugglinmike/refactor-for-parsers-assignmentRick Waldron2017-12-1911-151/+137
|\ | | | | Refactor AssignmentExpression tests for parsers
| * Refactor AssignmentExpression tests for parsersMike Pennisi2017-12-1011-151/+137
| | | | | | | | | | | | | | | | | | | | | | | | A number of tests for the parsing of the AssignmentExpression production were expressed using `eval`. This made the tests more complex than necessary, and also prevented the tests from providing value to ECMAScript parsers. Remove the use of `eval` in the relevant tests and instead express the expectations with literal source text. Remove superfluous "onlyStrict" restriction from tests by declaring the probe binding prior to assignment.
View Lorry Controller Status