-
-
Notifications
You must be signed in to change notification settings - Fork 406
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
[Merged by Bors] - Add ES5 and ES6 Conformance calculation to boa_tester #2690
Conversation
Codecov Report
@@ Coverage Diff @@
## main #2690 +/- ##
==========================================
- Coverage 49.36% 49.30% -0.06%
==========================================
Files 397 396 -1
Lines 39568 39776 +208
==========================================
+ Hits 19533 19612 +79
- Misses 20035 20164 +129
... and 28 files with indirect coverage changes Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It seems that the Test262 comparator fails because the current "main" branch doesn't have the new fields in JSON. I guess they should be optional fields.
Yep, just noticed too, I've just added |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the contribution! I just have a small suggestion for development ease :)
05d0659
to
cacdddb
Compare
This is calculated based the tests es5id or es6id
I've separated the |
Opened #2706 to solve the CI issue. We can merge that PR after we agree on the new data model here and this PR after that. |
this allows us to organize total, passed, ignored, and panic stats by es version
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the contribution! Looks good to me
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me! :)
Ok, gonna merge #2706 and then run CI on this. |
Wouldn't it be better to merge your PR into this branch to check CI? Not sure why run it on main... |
Because #2706 doesn't target |
No idea what's happening here... I have seen it before though during testing. It worked fine if I wrote to a clean or non-existing dir, but if I tried to overwrite an older schema it'd fail... didn't think serde cared about the overwritten schema... |
Yeah, serde is very strict with serializations. Our best option here would be to derive |
All good now! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Great contribution!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me! :)
bors r+ |
This is calculated based the tests `es5id` or `es6id`. Judging by [this](tc39/test262#1557) it's probably not the best method of doing it, but the alternative would require a lot of rework on the boa_tester so that it can pull an older version of the test262 spec which has it's own problems since there's not really an "ES5" only version. I would think that if we're 100% passing on es5id's then it's safe to assume boa supports es5 (assuming test262's es5id is covering all the es5 cases) This Pull Request fixes/closes #2629. It changes the following: - Store `spec_version` in TestResult based on the tests `es[6/5]id` - Count all es5, es6 and their test outcome during `TestSuite::run()` - Print the conformance. I'm serializing the `spec_version` outcomes so that it can be displayed in test262 github page. I'd like to work on that too if possible. Let me know if there's anything more I should cover in this PR, I'll gladly do it :) Co-authored-by: jedel1043 <jedel0124@gmail.com>
Pull request successfully merged into main. Build succeeded: |
This is calculated based the tests
es5id
ores6id
.Judging by this it's probably not the best method of doing it, but the alternative would require a lot of rework on the boa_tester so that it can pull an older version of the test262 spec which has it's own problems since there's not really an "ES5" only version.
I would think that if we're 100% passing on es5id's then it's safe to assume boa supports es5 (assuming test262's es5id is covering all the es5 cases)
This Pull Request fixes/closes #2629.
It changes the following:
spec_version
in TestResult based on the testses[6/5]id
TestSuite::run()
I'm serializing the
spec_version
outcomes so that it can be displayed in test262 github page. I'd like to work on that too if possible. Let me know if there's anything more I should cover in this PR, I'll gladly do it :)