Test262 Report is developed and mantained by Bocoup. It provides JavaScript developers with up-to-date information on the state of new and existing language features across implementations. Test262 Report checks for changes to Test262, the ECMA-262 (“ECMAScript” or “JavaScript”) test suite, and each engine every day. If Test262 changes, all engines are rerun through the new version of Test262. If one engine changes, only that engine is run through test262. If no engines change and Test262 does not change, no new runs are made.
We run Test262 test material via Test262-harness, which itself uses eshost to normalize host runtime environment disparities. We use jsvu to install the latest engine binaries.
This repository is used as a public issue tracker to report bugs and feature requests for the report itself. Thank you for taking the time to visit this issue tracker and share your feedback. We really appreciate it! Before submitting a new issue to document a bug or request a feature, take a look over the open and closed issues in the issue tracker, and see if there is an existing thread to contribute to. If not please open a new issue and follow the guidelines in our template. Thanks again :)!
You can read more about this project on the project about page or in our Test262 Report announcement on the Bocoup Blog.
The source code for the tools used to run Test262 test material across multiple engines is publicly available, free to use, and maintained by the Bocoup team. The systems for orchestrating these tools in CI for daily runs, the data produced by this system, and the Test262 Report website are internal to Bocoup. If you would like to incorporate the confromance data that we collect, or use these systems in some other way, please email reports@bocoup.com.
This project uses the Bocoup Code of Conduct. Please report behavior that violates the code of conduct directly to hr@bocoup.com.