-
Notifications
You must be signed in to change notification settings - Fork 156
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Move test262 tests upstream #1853
Conversation
These are being moved to tc39/test262.
159ad10
to
da870e1
Compare
Codecov Report
@@ Coverage Diff @@
## main #1853 +/- ##
==========================================
+ Coverage 94.76% 94.78% +0.01%
==========================================
Files 19 19
Lines 10969 10969
Branches 1712 1712
==========================================
+ Hits 10395 10397 +2
+ Misses 559 557 -2
Partials 15 15
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report at Codecov.
|
Marked as draft, because I will need to update the submodule when the test262 pull request is merged. |
The Temporal test262 tests are being removed from tc39/proposal-temporal (see tc39/proposal-temporal#1853 ) and moved to tc39/test262 where they will continue to be developed. Run them from a git submodule so we can pull in new upstream versions when we are ready for them. Instead of cloning tc39/proposal-temporal to run the tests, we copy the relevant parts of its test262 CI script. The files expected-failures.txt, parseResults.js, and preprocessor.test262.cjs are copied from there as well.
Instead of an in-tree checkout use a git submodule of test262 so we can pin the tests to a particular commit and pull in updates when we are ready for them. Requires some changes in various paths. The tests that were currently marked as expected to fail were not added to upstream test262 yet, so they are removed from expected-failures.txt.
The tests now live in tc39/test262, so this is ready for review. |
The Temporal test262 tests are being removed from tc39/proposal-temporal (see tc39/proposal-temporal#1853 ) and moved to tc39/test262 where they will continue to be developed. Run them from a git submodule so we can pull in new upstream versions when we are ready for them. Instead of cloning tc39/proposal-temporal to run the tests, we copy the relevant parts of its test262 CI script. The files expected-failures.txt, parseResults.js, and preprocessor.test262.cjs are copied from there as well.
The Temporal test262 tests are being removed from tc39/proposal-temporal (see tc39/proposal-temporal#1853 ) and moved to tc39/test262 where they will continue to be developed. Run them from a git submodule so we can pull in new upstream versions when we are ready for them. Instead of cloning tc39/proposal-temporal to run the tests, we copy the relevant parts of its test262 CI script. The files expected-failures.txt, parseResults.js, and preprocessor.test262.cjs are copied from there as well.
The Temporal test262 tests are being removed from tc39/proposal-temporal (see tc39/proposal-temporal#1853 ) and moved to tc39/test262 where they will continue to be developed. Run them from a git submodule so we can pull in new upstream versions when we are ready for them. Instead of cloning tc39/proposal-temporal to run the tests, we copy the relevant parts of its test262 CI script. The files expected-failures.txt, parseResults.js, and preprocessor.test262.cjs are copied from there as well.
As discussed in tc39/test262#3002, this moves the test262 tests upstream, where they will continue to be developed. Includes changes to our package.json and CI setup to run the test262 tests using a git submodule, instead of an in-tree checkout, so that we can pull in updates from test262 when we are ready for them.