Skip to content
Snippets Groups Projects
  1. Dec 07, 2014
    • Brian Terlson's avatar
      Move S9.9_A1/2 to proper locations · da465e73
      Brian Terlson authored
      The with statement tests were novel, but the tests for
      property accessors throwing errors for undefined & null
      were duplicates with S11.2.1_A3_T4/5 respectively.
      da465e73
  2. Aug 12, 2014
    • Sam Mikes's avatar
      bestPractice: supply error names to negative · 6b7e5d77
      Sam Mikes authored
      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
      6b7e5d77
  3. Jul 30, 2014
    • Brian Terlson's avatar
      Add path attribute. · 0defa373
      Brian Terlson authored
      0defa373
    • Brian Terlson's avatar
      Normalize testcase format · d4354d14
      Brian Terlson authored
      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.
      d4354d14
  4. Feb 29, 2012
  5. Feb 07, 2012
  6. Nov 04, 2011
  7. Oct 03, 2011
Loading