1. 17 Jun, 2015 1 commit
  2. 16 Jun, 2015 1 commit
  3. 10 Jun, 2015 3 commits
  4. 09 Jun, 2015 1 commit
    • arv's avatar
      Update Test262 to 5/30 · d869f4a4
      arv authored
      This updates the test runner to run all tests in both sloppy
      and strict mode.
      
      It also marks the test in the status file as failing in
      sloppy mode even if all it does is marking the test as
      [PASS, FAIL]. A future CL will have to validate that the
      tests pass and fail in the correct mode.
      
      Review URL: https://codereview.chromium.org/1136553008
      
      Cr-Commit-Position: refs/heads/master@{#28879}
      d869f4a4
  5. 01 Apr, 2015 1 commit
  6. 31 Mar, 2015 1 commit
  7. 30 Mar, 2015 2 commits
  8. 12 Mar, 2015 1 commit
    • arv's avatar
      Use path in name for test262-es6 · 36df5747
      arv authored
      For ES5 the file names always included the whole path, like this:
      
        ch15/15.2/15.2.3/15.2.3.14/15.2.3.14-1-3.js
      
      For ES6 this is no longer true:
      
        language/computed-property-names/basics/symbol.js
        language/computed-property-names/class/method/symbol.js
      
      To allow the status file to correctly identify the right test we need
      to change the reported test name to include the whole path.
      
      BUG=None
      LOG=N
      R=rossberg@chromium.org, machenbach@chromium.org
      
      Review URL: https://codereview.chromium.org/1001613002
      
      Cr-Commit-Position: refs/heads/master@{#27167}
      36df5747
  9. 31 Oct, 2014 1 commit
  10. 20 Oct, 2014 1 commit
  11. 11 Sep, 2014 1 commit
  12. 25 Aug, 2014 1 commit
  13. 22 Aug, 2014 1 commit
    • rossberg@chromium.org's avatar
      test/test262: update testcfg.py for new test262 · cc07503b
      rossberg@chromium.org authored
      testcfg.py:
      
      - update revision and MD5
      - remove non-mandatory harness files
      - use test parser distributed with test262
      - new attribute `suite.harnesspath`
      - new method GetIncludesForTest
      - GetSourceForTest: cache source on testcase
      - IsNegativeTest: use parseTestRecord
      - use 7-char sha hash [1]
      - DRY setting up paths to test262 suite, harness, etc
      - clean up helper fns
      
      harness-adapter.js:
      
      - add $DONE function to adapter [2]
      
      1: github tar file has 7-char sha embedded in dir name
      script cannot find directory to rename if they don't match exactly
      
      2: test262 uses a `$DONE` function for async tests with
      semantics like those of mocha's `done`.
      
      Briefly: done(arg) => if (arg) { /* failure */ }
      
      Implemented a version of this for v8, using v8-specific
      api (`print`, `quit`)
      
      BUG=v8:3513
      LOG=N
      R=jkummerow@chromium.org
      
      Review URL: https://codereview.chromium.org/478163002
      
      git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@23313 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
      cc07503b
  14. 21 May, 2014 1 commit
  15. 28 Feb, 2014 2 commits
  16. 20 Sep, 2013 1 commit
  17. 19 Sep, 2013 1 commit
  18. 10 May, 2013 1 commit
  19. 18 Apr, 2013 1 commit
  20. 15 Nov, 2012 2 commits
  21. 24 Sep, 2012 1 commit
  22. 05 Jun, 2012 1 commit
  23. 11 May, 2012 1 commit
  24. 16 Apr, 2012 1 commit
  25. 13 Apr, 2012 1 commit
  26. 28 Mar, 2012 1 commit
  27. 07 Mar, 2012 1 commit
  28. 16 Dec, 2011 1 commit
  29. 07 Oct, 2011 1 commit
  30. 26 Jul, 2011 1 commit
  31. 23 Mar, 2011 1 commit
  32. 21 Mar, 2011 1 commit
  33. 10 Jan, 2011 1 commit
    • ricow@chromium.org's avatar
      Enable sharding of individual testsuites in tools/test.py · b4ea8c7f
      ricow@chromium.org authored
      This patch enables two new flags for the tools/test.py script;
      --shard-count - giving the ability to split the tests to be run
      into shard-count chunks.
      --shard-run - giving the ability to specify which of the shards to actually run.
      
      Example
        tools/test.py -j15 --shard-count=2 --shard-run=1 mozilla
      would split the mozilla tests into two chunks and run the tests in the first chunk
      
      Running:
        tools/test.py -j15 --shard-count=2 --shard-run=1 mozilla
        tools/test.py -j15 --shard-count=2 --shard-run=2 mozilla
      is equivalent (in terms of test coverage) of just running:
        tools/test.py -j15 mozilla
      
      In addition, tests are now sorted before they are returned from the
      test specific ListTests methods (sputnik and mozilla tests where
      already sorted before they where returned).
      
      This change is needed to split a single test suite over two slaves on
      the waterfall.
      
      
      Review URL: http://codereview.chromium.org/6127003
      
      git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@6248 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
      b4ea8c7f
  34. 24 Aug, 2010 1 commit
  35. 15 Sep, 2009 1 commit