tyler.durden
/
test262
mirror of https://github.com/tc39/test262.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
5,192 Commits 18 Branches 0 Tags 142 MiB
Commit Graph

24 Commits

Author SHA1 Message Date
Gus Caplan a53f43e1ce
add missing newlines in tests 2019-11-10 20:18:56 -08:00
Mathias Bynens b9daa57dcb Rename to $DONOTEVALUATE per @leobalter's suggestion 2018-10-23 13:51:17 +02:00
Mathias Bynens e3feffb01e Move `throw "…"` for negative parsing errors to a helper function 
Closes #1634.
 2018-10-23 13:51:16 +02:00
Rick Waldron ffc46a667c BigInt: cleanup assertion messages (#1549) 2018-05-09 18:14:09 -03:00
Jeff Walden a19993e269 Add tests for the behavior of INT32_MIN (-2147483648) as exponent with the exponentiation operator and with Math.pow (which shares the same core algorithm in the spec, but might be differently implemented in actual implementations). (#1445) 2018-02-14 17:02:39 -05:00
Josh Wolfe 4455b1017e remove unnecessary method syntax 2018-01-25 14:00:43 -05:00
Josh Wolfe 9d066a8181 Order of evaluation tests for infix numeric operators 2018-01-25 14:00:43 -05:00
Josh Wolfe 186ec5d177 BigInt and Number type mismatch tests for infix operators 2018-01-25 14:00:10 -05:00
Mike Pennisi 136110378b Rename negative test "phase" for parsing 
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.
 2018-01-05 15:17:50 -05:00
Josh Wolfe 4f06f98771 Infix operator ToNumeric coercion tests for BigInt operands 2018-01-05 12:46:27 -05:00
Rick Waldron 92a2621901 Frontmatter: fixup "info: >" to "info: |" 2018-01-05 12:27:59 -05:00
Robin Templeton 609869638f [BigInt] arithmetic tests 2017-10-16 13:19:08 -04:00
Leo Balter 7765873c3e
Refactor tests for the BigInt construtor 2017-08-25 15:56:11 -04:00
Robin Templeton 37beb36524
add BigInt tests 2017-08-24 15:58:14 -04:00
Mike Pennisi 81d00def42 Force "early error" tests to fail if evaluated 
This pattern makes expectations more explicit by making test files more
literal.
 2017-06-28 11:24:36 -04:00
Mike Pennisi 7d4b1d28ae Re-format tests for SyntaxErrors 
Authored via the following command:

   $ find test -type f -print0 | \
       xargs -0 sed \
         -i 's/^\(\s*\)negative:\s*SyntaxError\s*$/\1negative:\n\1  phase: early\n\1  type: SyntaxError/g'
 2016-10-19 15:24:21 -04:00
Leo Balter e49d2661a8 Improve assertions comparing values to NaN (#690) 
The global isNaN is not precise at all, and Number.isNaN is an ES6 feature that makes it preferrable to use assert's sameValue for NaN values, as it handles it internally using the comparison.
 2016-07-01 11:22:55 -07:00
Mike Pennisi f7aa31b41f Remove over-specified tests 
Except for a small set of expected input/output pairs, both ES5 and
ES2015 define the expected return value of these methods in terms of an
"implementation-dependent approximation." This makes it inappropriate to
enforce expectations for specific values, even if expressed imprecisely.
 2016-04-18 14:36:49 -04:00
Gorkem Yakin ed32ae6f4a Convert "info" to "description" 2016-02-23 14:24:08 -08:00
Rick Waldron e0afd42914 descriptions and info 2016-02-23 16:42:11 -05:00
Rick Waldron 79dfcf3e85 Restore missing object definitions 2016-02-22 19:17:24 -05:00
Rick Waldron b92e68646d improved info and description 2016-02-22 16:49:00 -05:00
Rick Waldron 2a962f74be id => esid 2016-02-22 14:47:47 -05:00
Rick Waldron 2a112a3190 Exponentiation Operator tests 2016-02-22 14:47:47 -05:00