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/block/S12.1_A4_T1.js

22 lines
592 B
JavaScript
Raw Normal View History

All sputnik and ietestcenter tests converted to proposed new canonical form
2011-09-07 08:35:18 +02:00
// Copyright 2009 the Sputnik authors. All rights reserved.
// 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
/*---
info: The production Block can't be inside of expression
Add path attribute.
2014-07-25 00:41:42 +02:00
es5id: 12.1_A4_T1
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: Checking if execution of "y={__func}()" fails
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-01-31 00:57:28 +01:00
negative:
phase: early
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
---*/
All sputnik and ietestcenter tests converted to proposed new canonical form
2011-09-07 08:35:18 +02:00
Force "early error" tests to fail if evaluated This pattern makes expectations more explicit by making test files more literal.
2017-04-29 22:31:08 +02:00
throw "Test262: This statement should not be evaluated.";
All sputnik and ietestcenter tests converted to proposed new canonical form
2011-09-07 08:35:18 +02:00
function __func(){};
//////////////////////////////////////////////////////////////////////////////
//CHECK#1
bestPractice: supply error names to negative pilot directory for replacing flags: [negative] with negative: errorname ch07-7.2,7.3: add error names ch07-rest: insert error names rest of ch07 ch08: add expected error name ch11: add error name to negative ch12: put error name in negative ch13: add error name to negative only one test, did it manually ch15: add error name to negative: ch07: add error name to negative these tests used flags: \n - negative and so were not caught by the earlier naive grep for flags: [negative] --- changes suggested by @anba bestPractice - remove added NotEarlyError ch07,ch11 - expect ReferenceError (req'd by ES6) correct test descriptions to expect ReferenceError only enforce parsing as block statement by adding `;` remove needless include of $FAIL.js effectively, a rebase of all changes onto master Merge branch 'negative-addErrorName-work' into negative-addErrorName-bestPractice Merge branch 'saved-bestPractice-negative' into negative-addErrorName-work Conflicts: test/suite/ch11/11.13/11.13.2/S11.13.2_A2.2_T2.js test/suite/ch12/12.1/S12.1_A4_T1.js test/suite/ch12/12.5/S12.5_A2.js incorporate changes made on PR branch re-remove added NotEarlyError Merge branch 'negative-addErrorName-work' into negative-addErrorName-bestPractice Conflicts: test/suite/ch11/11.13/11.13.2/S11.13.2_A2.2_T2.js test/suite/ch12/12.1/S12.1_A4_T1.js test/suite/ch12/12.5/S12.5_A2.js ch15: correct negative regexes ch10: avoid use of not-NotEarlyError regex ch14 error regexps ch13 error regexps ch12: negative error matching Merge branch 'console-runner-checkError' into negative-addErrorName-work test262.py: check negative tests with regex implement checking of negative tests => negative: SyntaxError means that /SyntaxError/ must match stderr or test is reported as failure Fixes #78 expect real errors bestPractice: supply error names to negative pilot directory for replacing flags: [negative] with negative: errorname ch07-7.2,7.3: add error names ch07-rest: insert error names rest of ch07 ch08: add expected error name ch11: add error name to negative ch12: put error name in negative ch13: add error name to negative only one test, did it manually ch15: add error name to negative: ch07: add error name to negative these tests used flags: \n - negative and so were not caught by the earlier naive grep for flags: [negative] --- changes suggested by @anba bestPractice - remove added NotEarlyError ch07,ch11 - expect ReferenceError (req'd by ES6) correct test descriptions to expect ReferenceError only enforce parsing as block statement by adding `;` remove needless include of $FAIL.js Merge branch 'negative-addErrorName-work' into negative-addErrorName-bestPractice resolved Conflicts: test/suite/ch07/7.9/S7.9_A5.7_T1.js test/suite/ch11/11.13/11.13.1/S11.13.1_A2.1_T3.js test/suite/ch11/11.13/11.13.2/S11.13.2_A2.2_T1.js test/suite/ch11/11.13/11.13.2/S11.13.2_A2.2_T10.js test/suite/ch11/11.13/11.13.2/S11.13.2_A2.2_T11.js test/suite/ch11/11.13/11.13.2/S11.13.2_A2.2_T2.js test/suite/ch11/11.13/11.13.2/S11.13.2_A2.2_T3.js test/suite/ch11/11.13/11.13.2/S11.13.2_A2.2_T4.js test/suite/ch11/11.13/11.13.2/S11.13.2_A2.2_T5.js test/suite/ch11/11.13/11.13.2/S11.13.2_A2.2_T6.js test/suite/ch11/11.13/11.13.2/S11.13.2_A2.2_T7.js test/suite/ch11/11.13/11.13.2/S11.13.2_A2.2_T8.js test/suite/ch11/11.13/11.13.2/S11.13.2_A2.2_T9.js test/suite/ch11/11.3/11.3.1/S11.3.1_A2.1_T3.js test/suite/ch11/11.3/11.3.2/S11.3.2_A2.1_T3.js test/suite/ch11/11.4/11.4.4/S11.4.4_A2.1_T3.js test/suite/ch11/11.4/11.4.5/S11.4.5_A2.1_T3.js test/suite/ch12/12.5/S12.5_A2.js test/suite/ch12/12.6/12.6.3/S12.6.3_A4_T2.js negative: second half of @anba notes correct test descriptions to expect ReferenceError only enforce parse as block statement by adding `;` remove needless include of $FAIL.js ch12: specify type negative: @anba fixes bestPractice - remove added NotEarlyError ch07,ch11 - expect ReferenceError (req'd by ES6) bestPractice: supply error names to negative pilot directory for replacing flags: [negative] with negative: errorname ch07-7.2,7.3: add error names ch07-rest: insert error names rest of ch07 ch08: add expected error name ch11: add error name to negative ch12: put error name in negative ch13: add error name to negative only one test, did it manually ch15: add error name to negative: ch07: add error name to negative these tests used flags: \n - negative and so were not caught by the earlier naive grep for flags: [negative] expect a SyntaxError ch07: add error name to negative these tests used flags: \n - negative and so were not caught by the earlier naive grep for flags: [negative] ch15: add error name to negative: ch13: add error name to negative only one test, did it manually ch12: put error name in negative ch11: add error name to negative ch08: add expected error name ch07-rest: insert error names rest of ch07 ch07-7.2,7.3: add error names negative-errorname: pilot pilot directory for replacing flags: [negative] with negative: errorname bestPractice: supply error names to negative bestPractice: supply error names to negative pilot directory for replacing flags: [negative] with negative: errorname ch07-7.2,7.3: add error names ch07-rest: insert error names rest of ch07 ch08: add expected error name ch11: add error name to negative ch12: put error name in negative ch13: add error name to negative only one test, did it manually ch15: add error name to negative: ch07: add error name to negative these tests used flags: \n - negative and so were not caught by the earlier naive grep for flags: [negative] bestPractice: supply error names to negative negative-errorname: pilot pilot directory for replacing flags: [negative] with negative: errorname ch07-7.2,7.3: add error names ch07-rest: insert error names rest of ch07 ch08: add expected error name ch11: add error name to negative ch12: put error name in negative ch13: add error name to negative only one test, did it manually ch15: add error name to negative: ch07: add error name to negative these tests used flags: \n - negative and so were not caught by the earlier naive grep for flags: [negative] expect a SyntaxError negative: @anba fixes bestPractice - remove added NotEarlyError ch07,ch11 - expect ReferenceError (req'd by ES6) ch12: specify type negative: second half of @anba notes correct test descriptions to expect ReferenceError only enforce parse as block statement by adding `;` remove needless include of $FAIL.js expect real errors ch12: negative error matching ch13 error regexps ch14 error regexps add "description" header back remove now-unused includes remove needless include
2014-08-01 13:35:15 +02:00
y={__func;}();
All sputnik and ietestcenter tests converted to proposed new canonical form
2011-09-07 08:35:18 +02:00
//
//////////////////////////////////////////////////////////////////////////////