Skip to content
Snippets Groups Projects
  1. Feb 15, 2018
    • Robin Templeton's avatar
      BigInt TypedArray tests · 9232d65b
      Robin Templeton authored
      - add @jakobkummerow's changes
      - remove EOL whitespace
      - use 'Array.isArray' instead of 'instanceof Array'
      - check for BigInt type in toLocaleString tests
      - specify TypedArray constructor list for non-BigInt tests
      - update TypedArray harness test for BigInt
      - add a missing type coercion
      - disable more tests for Big(U)Int64Array
      - check for BigInt before using BigInt TypedArray constructors
      9232d65b
  2. Jan 05, 2018
  3. Dec 21, 2017
  4. Sep 11, 2017
  5. Sep 07, 2017
  6. Jul 14, 2017
  7. Jun 28, 2017
  8. Jun 23, 2017
  9. May 01, 2017
  10. Apr 15, 2017
  11. May 25, 2016
  12. Apr 21, 2016
  13. Apr 19, 2016
    • jugglinmike's avatar
      Correct invalid tests for the Date constructor · cf68c3be
      jugglinmike authored
      The millisecond representation of a given Date instance is dependent on
      the local system's time zone settings. In order to pass consistently
      across contexts, tests for this value must take the system configuration
      into account.
      
      Introduce a test harness utility function to encapsulate these concerns.
      Re-use this function across all test files that assert the exact
      millisecond representation of Date instances.
      cf68c3be
  14. Apr 15, 2016
  15. Apr 11, 2016
  16. Mar 15, 2016
  17. Feb 22, 2016
  18. Feb 19, 2016
  19. Feb 17, 2016
  20. Feb 13, 2016
  21. 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
  22. Apr 22, 2015
  23. Dec 09, 2014
Loading