Skip to content
Snippets Groups Projects
  1. Jul 17, 2015
  2. Jun 18, 2015
    • Mike Pennisi's avatar
      Update handling of directive prologues · 29ecced6
      Mike Pennisi authored
      Some tests specifically concern the application of the `use strict`
      directive as it appears in JavaScript source code. These tests should
      *not* be run with the `onlyStrict` flag because relying on the test
      runner to enable strict mode makes the semantics of the source code
      irrelevant. Update these tests to use the `noStrict` flag.
      
      Other tests concern language semantics that are only valid in strict
      mode, but the mechanism for enabling strictness is inconseqential.
      Update these tests to use the `onlyStrict` flag and remove any redundant
      `use strict` directive prologues contained within.
      
      Still other tests are valid both within and outside of strict mode.
      In keeping with the majority of other tests, do not specify any
      restrictions on the environments in which these tests may be run.
      29ecced6
    • Mike Pennisi's avatar
      Fix invalid tests · ef1fddd5
      Mike Pennisi authored
      ef1fddd5
  3. Dec 07, 2014
  4. Jul 30, 2014
    • Sam Mikes's avatar
      tools, harness: support new YAML frontmatter · c33bf0e0
      Sam Mikes authored
      parseTestRecord: add support for YAML frontmatter
      parseTestRecord: initial unit test for test record parser
      parseTestRecord: refactor for testing
      
      factor old parsing; add YAML parsing
      
      runner: support "includes" from YAML frontmatter
      
      support frontmatter "includes" in python runner
      use test.includes if present instead of scanning test code with regex
      
      harness: factor individual functions out into files
      
      tools: handle YAML errors
      
      tolerate missing keys in dictionary (flags, includes)
      report filename when empty frontmatter block
      new option --list-includes to test262.py
      
      harness: factor helper functions into separate files
      
      sth: remove extra close-paren (syntax error)
      
      test_common: TDD; failing parse of YAML
      
      common: use parseTestRecord (YAML-aware)
      c33bf0e0
    • 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
  5. Feb 29, 2012
  6. Feb 07, 2012
  7. Nov 04, 2011
  8. Sep 25, 2011
  9. Sep 24, 2011
  10. Sep 23, 2011
  11. Sep 14, 2011
Loading