cc07503bd9
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
19 lines
686 B
Plaintext
19 lines
686 B
Plaintext
This directory contains code for binding the test262 test suite
|
|
into the v8 test harness. To use the tests check out the test262
|
|
tests from
|
|
|
|
https://github.com/tc39/test262
|
|
|
|
at hash 595a36b (2014/08/10 revision) as 'data' in this directory. Using later
|
|
version may be possible but the tests are only known to pass (and indeed run)
|
|
with that revision.
|
|
|
|
git clone https://github.com/tc39/test262 data
|
|
cd data
|
|
git checkout 595a36b
|
|
|
|
If you do update to a newer revision you may have to change the test
|
|
harness adapter code since it uses internal functionality from the
|
|
harness that comes bundled with the tests. You will most likely also
|
|
have to update the test expectation file.
|