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

Question: Test specific old version #1557

Closed
msuperina opened this issue May 15, 2018 · 3 comments
Closed

Question: Test specific old version #1557

msuperina opened this issue May 15, 2018 · 3 comments

Comments

@msuperina
Copy link

Is there a test suite targeting specific older versions of the ECMA-262 standard ? If not, is there a way to automatically filter out test cases which would target later versions ?
Specifically, I would like to test if a js engine is compliant to the first version https://www.ecma-international.org/publications/files/ECMA-ST-ARCH/ECMA-262,%201st%20edition,%20June%201997.pdf

@msuperina msuperina changed the title Test specific old version Question: Test specific old version May 15, 2018
@leobalter
Copy link
Member

Test262 only aims at the latest working drafts from Ecma262 + Stage 3 proposals.

This is also a way to provide a best cost of maintenance in terms of necessary human hours.

Also, each new edition of Ecma262 deprecates the previous edition in order they are not a standard anymore, and servers only as historical documents.

I don't know of any version of Test262 for anything before ES5.

Today you could fetch test files in this repo using the es5id tags, but they would be very incomplete considering changes in many of the pre-existing API and syntax.

@msuperina
Copy link
Author

Thank you for your answer, your sentence

each new edition of Ecma262 deprecates the previous edition in order they are not a standard anymore

is the key point I was wrongly missing.

I will try your suggestion about es5id tags.
In the meanwhile I found those archives https://github.com/tc39/archives/tree/master/test262-www/old which seem worth an inspection.

@jugglinmike
Copy link
Contributor

See also #569

bors bot pushed a commit to boa-dev/boa that referenced this issue Mar 20, 2023
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>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants