Skip to content
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

Run against the tc39 testsuite #1662

Closed
mstoykov opened this issue Oct 8, 2020 · 2 comments
Closed

Run against the tc39 testsuite #1662

mstoykov opened this issue Oct 8, 2020 · 2 comments

Comments

@mstoykov
Copy link
Contributor

mstoykov commented Oct 8, 2020

This is already being done by goja here but arguably we can do it as well but with a newer version (we have string literals from babel which is the reason why goja is stuck to a version from 2017) and with more of the tests as again babel provides us with support for more of them.

I would also argue that we should run the WHOLE suite and codify the things that don't work so when they start work we actually find this out, through the tests breaking.

Given that this is likely to take a LOT of time on each run maybe we should break them apart in es5, es6, es7 ... test packages and probably run them in a separate runner in CI and maybe not locally, although of course that depends on just how slow it's going to be.

@mstoykov
Copy link
Contributor Author

mstoykov commented Nov 5, 2020

This currently is being worked on at https://github.com/MStoykov/k6-test262

@mstoykov
Copy link
Contributor Author

mstoykov commented Jan 8, 2021

closed with #1747

@mstoykov mstoykov closed this as completed Jan 8, 2021
@na-- na-- added this to the v0.30.0 milestone Jan 8, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants