tyler.durden
/
test262
mirror of https://github.com/tc39/test262.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
test262/test/language/statements/for-in/var-eval-strict-init.js

16 lines
371 B
JavaScript
Raw Normal View History

Normalize testcase format This commit normalizes the test case format used across test262. It applies the following transformations: * Convert to YAML for frontmatter * Remove of trailing whitespace * Replace /r/n with /n except in chapters 6 and 7. * Copyright header always uses // comments * new includes attribute replaces $INCLUDE * No implicit assumptions about test environment other than $ERROR. Everything else appears in the include array. This includes "runTestCase" which is now included in a substantial number of tests.
2014-07-22 01:09:02 +02:00
// Copyright (c) 2012 Ecma International. All rights reserved.
Remove links to hg.ecmascript.org
2015-07-17 17:42:45 +02:00
// This code is governed by the BSD license found in the LICENSE file.
Normalize testcase format This commit normalizes the test case format used across test262. It applies the following transformations: * Convert to YAML for frontmatter * Remove of trailing whitespace * Replace /r/n with /n except in chapters 6 and 7. * Copyright header always uses // comments * new includes attribute replaces $INCLUDE * No implicit assumptions about test environment other than $ERROR. Everything else appears in the include array. This includes "runTestCase" which is now included in a substantial number of tests.
2014-07-22 01:09:02 +02:00
/*---
Relocate and refactor tests The tests for the parsing of `for/in` loops 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. Move the tests to the `for-in` directory to better reflect the grammar production that they test.
2018-09-24 03:32:15 +02:00
esid: sec-for-statement
Normalize testcase format This commit normalizes the test case format used across test262. It applies the following transformations: * Convert to YAML for frontmatter * Remove of trailing whitespace * Replace /r/n with /n except in chapters 6 and 7. * Copyright header always uses // comments * new includes attribute replaces $INCLUDE * No implicit assumptions about test environment other than $ERROR. Everything else appears in the include array. This includes "runTestCase" which is now included in a substantial number of tests.
2014-07-22 01:09:02 +02:00
description: "'for(var eval = 42 in ...) {...}' throws SyntaxError in strict mode"
flags: [onlyStrict]
Relocate and refactor tests The tests for the parsing of `for/in` loops 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. Move the tests to the `for-in` directory to better reflect the grammar production that they test.
2018-09-24 03:32:15 +02:00
negative:
phase: parse
type: SyntaxError
Normalize testcase format This commit normalizes the test case format used across test262. It applies the following transformations: * Convert to YAML for frontmatter * Remove of trailing whitespace * Replace /r/n with /n except in chapters 6 and 7. * Copyright header always uses // comments * new includes attribute replaces $INCLUDE * No implicit assumptions about test environment other than $ERROR. Everything else appears in the include array. This includes "runTestCase" which is now included in a substantial number of tests.
2014-07-22 01:09:02 +02:00
---*/
Update tests with DONOTEVALUATE
2018-11-13 23:48:29 +01:00
$DONOTEVALUATE();
Replace runTestCase with assert.throws [test/language/statements]
2015-08-11 17:43:01 +02:00
Relocate and refactor tests The tests for the parsing of `for/in` loops 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. Move the tests to the `for-in` directory to better reflect the grammar production that they test.
2018-09-24 03:32:15 +02:00
for (var eval = 42 in null) {}