- Apr 03, 2019
-
-
Frank Yung-Fong Tang authored
I somehow missed the last line last time I proposed https://github.com/tc39/test262/pull/2111
-
ta7sudan authored
Add test that a Proxy instance with getPrototypeOf trap use instanceof operator on a function (#2107)
-
- Apr 02, 2019
-
-
Leo Balter authored
Update test to allow 'narrow' style for all types
-
Frank Yung-Fong Tang authored
CLDR 35 change "and" to "&" for the list form pattern "short" see https://unicode.org/cldr/trac/ticket/11520 Also compare https://www.unicode.org/repos/cldr/tags/release-34/common/main/en.xml against https://www.unicode.org/repos/cldr/tags/release-35-beta/common/main/en.xml Notice the addition of <listPattern type="standard-short"> <listPatternPart type="start">{0}, {1}</listPatternPart> <listPatternPart type="middle">{0}, {1}</listPatternPart> <listPatternPart type="end">{0}, & {1}</listPatternPart> <listPatternPart type="2">{0} & {1}</listPatternPart> </listPattern>
-
Leo Balter authored
Refactor `with` statement tests for parsers
-
Leo Balter authored
Refactor misc. statement tests for parsers
-
Leo Balter authored
Refactor literal tests for parsers
-
Richard Gibson authored
* Add tests for string representations of Date objects with negative years Ref https://github.com/tc39/ecma262/issues/1035 Ref https://github.com/tc39/ecma262/issues/1407
-
Leo Balter authored
Improve content and style of contribution guidelines
-
Frank Yung-Fong Tang authored
-
Frank Yung-Fong Tang authored
Based on the changes in https://github.com/tc39/proposal-intl-list-format/pull/43 We now allow 'narrow' style for all types
-
- Apr 01, 2019
-
-
Mike Pennisi authored
The tests for the parsing of the `with` statement 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 and instead express the expectations with literal source text. Rename the files to make each test's purpose more clear.
-
Mike Pennisi authored
These tests are syntactically equivalent to `test/language/statements/with/12.10.1-7-s.js` and may therefore be removed without degrading coverage. While `test/language/statements/with/12.10.1-9-s.js` differs slightly in the pattern used to enable strict mode, the relevant behavior of the "use strict" directive prologue is expressly tested via `test/language/directive-prologue/func-expr-inside-func-decl-parse.js`.
-
Mike Pennisi authored
Previously, some tests verified two independent concerns simultaneously: syntactic validity and runtime completion value. The former is relevant for ECMAScript runtimes and parsers alike, but the latter is only observable by runtimes. Express expectations regarding syntactic validity using literal program code so they can be used by parsers. Maintain the original tests which rely on eval in order to preserve coverage for statement completion values.
-
Mike Pennisi authored
The tests for the parsing of various statement 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 and instead express the expectations with literal source text. Rename the files to make each test's purpose more clear.
-
Mike Pennisi authored
These tests are ostensibly designed to validate parsing of Regular Expression literals--specifically those which use Unicode escape sequences to declare flags. However, because the syntax is expressed in terms of a string literal and then evaluated dynamically, the escape sequences in use have no bearing on the program code which is ultimately parsed. These tests therefore do not extend coverage in any meaningful way and may be removed.
-
Mike Pennisi authored
The tests for the parsing of literal values 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 and instead express the expectations with literal source text. Rename the files to make each test's purpose more clear.
-
Mike Pennisi authored
The production under test is also used in the following file: test/language/literals/numeric/legacy-octal-integer-strict.js That test expresses the syntax with literal source text, making it useful for parsers. Remove this test in favor of the other.
-
- Mar 29, 2019
-
-
Richard Gibson authored
Per advice from @leobalter, based upon content from test/language/expressions/dynamic-import
-
Richard Gibson authored
-
Richard Gibson authored
"tag" has a specific and different meaning; the proper term for this page is "key" cf. https://yaml.org/spec/1.2/spec.html#id2761292
-
Richard Gibson authored
-
- Mar 26, 2019
-
-
Leo Balter authored
-
- Mar 25, 2019
-
-
Leo Balter authored
-
- Mar 21, 2019
-
-
Leo Balter authored
Transfer Travis jobs to CircleCI
-
- Mar 19, 2019
-
-
jugglinmike authored
-
Leo Balter authored
Refactor white space tests for parsers
-
Caio Lima authored
-
- Mar 17, 2019
-
-
Mike Pennisi authored
-
Mike Pennisi authored
-
- Mar 14, 2019
-
-
Leo Balter authored
Add missing feature tags
-
Leo Balter authored
* Add new tests to observe required leading line terminator Ref #2095
-
Leo Balter authored
-
- Mar 13, 2019
-
-
Leo Balter authored
-
Leo Balter authored
-
Leo Balter authored
Fix #2049
-
Leo Balter authored
Test cases for async function and async generator edge-cases
-
- Mar 12, 2019
-
- Mar 11, 2019
-
-
André Bargull authored
-
André Bargull authored
Issue: tc39/ecma262#1461 PR: tc39/ecma262#1470
-