How We Build Test262 Report
We are building test262.report daily from a run of all Test262 material (34,657 conformance test files at the time of this writing) in each of the 4 major engines, in default and strict modes, as well as in module code when ES Modules are present. We’ve built our testing bots using open source tools that we contribute to or maintain. We use Test262-harness as our runner and eshost to normalize host runtime environment disparities. We use jsvu to install the latest engine binaries.
Who is Test262 Report For?
Roadmap for Test262 Report
In addition to Test262 Report, we would like to report on more areas of the Web Platform for developers. Our criteria are test completeness and veracity. We are already contributing to WPT (Web Platform Tests), and working with the Google Chrome ecosystem infrastructure team on the results collection behind wpt.fyi, so WPT is an obvious next candidate.
We are excited to launch, maintain and continue to improve Test262 report. We welcome your feedback, feature requests and bug reports on the public issue tracker for Test262 Report at github.com/bocoup/test262-report-issue-tracker. We will continue to improve the veracity and completeness of these reports, and are eager to collaborate with the community, our partners, and funders to make the Web Platform more predictable for developers.