Skip to content

Latest commit

 

History

63 Commits

Folders and files

NameName
Last commit message
Last commit date
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

conformance testing

This repository runs upstream conformance test suites against pinned builds of Elide and publishes per-version reports. Suites:

Suite What it covers
test262 TC39's JavaScript conformance suite
wpt-wintertc a sparse Web Platform Tests subset for WinterTC / ECMA-429 APIs, including fetch
cpython-core CPython 3.12 Lib/test/test_* modules and packages
javac-jtreg OpenJDK langtools tools/javac through jtreg, compiling with Elide
node-api sparse Node.js core JavaScript API tests

Tracking: Compliance Testing meta (elide-dev/runtime#1172), Test262 (elide-dev/runtime#1173).

Compatibility

Generated by bun run testsuite --update-summaries from the latest committed reports.

Last updated: 2026-09-30T17:31:58.679Z

Latest compatibility pass rates

Suite Version Digest Pass rate vs expectations Regressions New passes
cpython-core 1.6.0+b8edacc63 7aa30129531a 90.8% 100.0% 0 0
javac-jtreg 1.6.0+b8edacc63 7aa30129531a 93.0% 100.0% 0 0
node-api 1.6.0+b8edacc63 7aa30129531a 81.8% 100.0% 0 0
test262 1.6.0+b8edacc63 7aa30129531a 93.0% 100.0% 0 0
wpt-wintertc 1.6.0+b8edacc63 7aa30129531a 95.5% 100.0% 0 0

Pass rate counts every test in the selection, including skipped/suppressed ones. vs expectations is the share of tests at or above the checked-in baseline (only regressions count against it).

How it works

A Bun/TypeScript harness drives each suite through its best native runner and normalizes the results. Each run executes inside a Docker image with a pinned Elide, so every elide run is a fast local subprocess. Results are compared against a checked-in expectations baseline: new failures are regressions, tests that newly pass advance the floor, and a --ratchet run locks the gains in.

Skips never inflate the numbers above: a skipped test still counts as a non-pass in Pass rate. Every skip has a written reason in expectations/<suite>.toml; see why tests are skipped.

Quick start

bun run setup                                        # deps + suite submodules
bun run testsuite --elide nightly --suite test262 --log
bun run testsuite --elide nightly --all-suites --log

Further reading

About

conformance testing

Resources

Contributing

Stars

1 star

Watchers

0 watching

Forks

Used by

Contributors

Languages