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. The tests are checked out as a dependency from | 2 into the v8 test harness. The tests are checked out as a dependency from |
3 | 3 |
4 https://chromium.googlesource.com/external/github.com/tc39/test262 | 4 https://chromium.googlesource.com/external/github.com/tc39/test262 |
5 | 5 |
6 at hash 26e6fd7 (2015/10/01 revision) as 'data' in this directory. They are | 6 at a revision specified in the DEPS file as 'data' in this directory. They are |
7 fetched with 'gclient sync'. To update to a newer version, please change the | 7 fetched with 'gclient sync'. To update to a newer version, please change the |
8 DEPS file. | 8 DEPS file. |
9 | 9 |
10 Using a newer version, e.g. 'deadbeef' may be possible but the tests are only | 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: | 11 known to pass (and indeed run) with the DEPS revision. Example: |
12 | 12 |
13 cd data | 13 cd data |
14 git fetch | 14 git fetch |
15 git checkout deadbeef | 15 git checkout deadbeef |
16 | 16 |
17 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 |
18 harness adapter code since it uses internal functionality from the | 18 harness adapter code since it uses internal functionality from the |
19 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 |
20 have to update the test expectation file. | 20 have to update the test expectation file. |
OLD | NEW |