If es5conform is not evolving at all and test262 is, I agree that we should
switch to use that instead. Since we have sputnik tests running already and
they
are currently being updated in the sputnik repository, I think we should
start
by only running the es5conform/ietestcenter portion of this. Once the test
support is in the repository for that, we should transfer the buildbots to
use
that and remove support for es5conform.
Does that make sense to you?
http://codereview.chromium.org/6711063/diff/1/test/test262/harness-adapt.js
File test/test262/harness-adapt.js (right):
http://codereview.chromium.org/6711063/diff/1/test/test262/harness-adapt.js#newcode68
test/test262/harness-adapt.js:68: (test.precondition !== undefined) ?
test.precondition.toString() : '',
Let's get rid of the long line. :)
http://codereview.chromium.org/6711063/diff/1/test/test262/jquery.js
File test/test262/jquery.js (right):
http://codereview.chromium.org/6711063/diff/1/test/test262/jquery.js#newcode28
test/test262/jquery.js:28: function $() {}
This seems annoying to have to do. If we cannot get rid of jquery
dependency, we should rename the file to jquery-mock.js or something
like that.
http://codereview.chromium.org/6711063/
--
v8-dev mailing list
[email protected]
http://groups.google.com/group/v8-dev
