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/expressions/object/setter-param-eval-strict-ou...

20 lines
464 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
/*---
Add path attribute.
2014-07-25 00:41:42 +02:00
es5id: 11.1.5-1-s
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: >
Strict Mode - SyntaxError is thrown when 'eval' occurs as the
Identifier in a PropertySetParameterList of a PropertyAssignment
that is contained in strict code
Refactor object initializer tests for parsers 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.
2018-01-21 05:56:35 +01:00
negative:
phase: parse
tools: enforce restriction on YAML negative key The phase field must precede the type field for negative tests to have a consistent style and be able to parse easier. Related to the goal of https://github.com/tc39/test262/issues/1997 Added this check to the linting script and updated tests accordingly.
2022-01-06 13:01:51 +01:00
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
flags: [onlyStrict]
---*/
Rename to $DONOTEVALUATE per @leobalter's suggestion
2018-10-11 16:59:24 +02:00
$DONOTEVALUATE();
Replace runTestCase with assert.throws [test/language/expressions]
2015-08-11 17:42:41 +02:00
Refactor object initializer tests for parsers 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.
2018-01-21 05:56:35 +01:00
void {
set x(eval) {}
};