| OLD | NEW |
| 1 This directory contains code for binding the test262 test suite | 1 This directory contains code for binding the test262 test suite |
| 2 into the v8 test harness. To use the tests check out the test262 | 2 into the v8 test harness. The tests are checked out as a dependency from |
| 3 tests from | |
| 4 | 3 |
| 5 https://github.com/tc39/test262 | 4 https://chromium.googlesource.com/external/github.com/tc39/test262 |
| 6 | 5 |
| 7 at hash c6ac390 (2015/07/06 revision) as 'data' in this directory. Using later | 6 at hash 26e6fd7 (2015/10/01 revision) as 'data' in this directory. They are |
| 8 version may be possible but the tests are only known to pass (and indeed run) | 7 fetched with 'gclient sync'. To update to a newer version, please change the |
| 9 with that revision. | 8 DEPS file. |
| 10 | 9 |
| 11 git clone https://github.com/tc39/test262 data | 10 Using a newer version, e.g. 'deadbeef' may be possible but the tests are only |
| 11 known to pass (and indeed run) with that revision. Example: |
| 12 |
| 12 cd data | 13 cd data |
| 13 git checkout c6ac390 | 14 git fetch |
| 15 git checkout deadbeef |
| 14 | 16 |
| 15 If you do update to a newer revision you may have to change the test | 17 If you do update to a newer revision you may have to change the test |
| 16 harness adapter code since it uses internal functionality from the | 18 harness adapter code since it uses internal functionality from the |
| 17 harness that comes bundled with the tests. You will most likely also | 19 harness that comes bundled with the tests. You will most likely also |
| 18 have to update the test expectation file. | 20 have to update the test expectation file. |
| OLD | NEW |