-
Notifications
You must be signed in to change notification settings - Fork 943
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
Externalize tests #1881
base: gh-pages
Are you sure you want to change the base?
Externalize tests #1881
Conversation
the data-*,js modules once externalized
- so it becomes possible to automate the updating of the test results - so it becomes possible to create custom Compat Tables for specialized environments
Would it be ok to update the min nodejs version to 14 or 18? Want to use parseArgs either natively (Node 18) or via @pkgjs/parseArgs (Node 14) |
f37974c
to
d9b3de6
Compare
Add update flag to runners for automatic updates to the result-*.json files based on the results of the runner
d9b3de6
to
1e13886
Compare
properties like constructor, __defineGetter__, __defineSetter__ , __lookupGetter and __lookupSetter__
Some res: {...} remained in the test-*.js files due to slightly different formatting used and therefor missed by the regex replace that was part of the conversion. As all the test results are extracted into .json files, data-commom is no longer used, thus removed
(re)marked this as Draft again, as I'm contemplating some additional changes, but would already appreciate some feedback on the general direction of extracting the results into their own json files. Has that any change of getting accepted? |
Any feedback anyone? Don't want to spend more time on this if the general direction of this PR, namely splitting the tests and results into separate files, is gonna be a no-go to begin with |
I guess the change in where the test results are stored would break the mechanism in Babel that downloads and converts the compat data, but imho it would be easy to adapt Babel accordingly |
Until such time when we can host proper custom compat tables based on the latest iteration of compat-table, see compat-table/compat-table#1881
@ljharb @chicoxyzzy any chance to get some feedback on the general idea to extract the results out from the data-*.js files and into .json files? Is it worth my time to finish this PR and get it out of draft status so it can be considered for merge? Or is this general idea dead in the water? |
It's a pretty major change so it's hard to develop an opinion about it, I think :-) |
Ok, but what does that mean exactly? 🙂 Does it mean you and/or others are actively thinking about whether or not this change is something you're willing to accept? Or do you need something additional from me to be able to make that decision? Or ....? |
It means I'm actively thinking about it. I can't speak for the other maintainers. |
This PR splits the tests and their results into 2 separate files, with the results being stored in JSON format, allowing automated modification, as to open up the possibility to eliminate the manual updating of test results
Additionally, this split makes it possible to create custom Compat Tables, for example with just all the different versions of one environment, including for example the nightly version. Note that are more enhancements possible for custom Compat Tables, even going as far as splitting this repo in a compat-table library and a Compat Table website (github pages) repo, but this are next steps imho
Is does mean that data-common.json is obsolete (and thus removed) as all the test results are not stored in JSON
Closes #1879
Closes #1493
Checks off on of the actions in #965
Building block for #614
Building block for #1790
Did the conversion of data-.js files > tests..js & results-*.json using the following script: