CI test results
How is ZeroWeb doing?
Scheduled CI runs the same compatibility and performance checks over time. This page reads the results committed to the repository.
Loading the latest results…
Web compatibility
WPT reftest pass rate
Each point is the latest upstream WPT run for that month, plotted as the pass rate. The corpus snapshot version is included because the test set size changes between versions.
Coverage by WPT suite
All tracked suites
One row per WPT suite. Denominators differ across rows (reftest files vs. testharness subtests) and the unit is shown next to every number. Rows marked “Planned” have no data yet and will fill in as those goals run.
Weekly performance run
Performance at p95
All results come from the same class of GitHub runner, so changes in hardware do not distort the trend. Lower is better.
Methodology: the CSS rendering suite is a self-source reftest — the test and reference pages are both rendered by ZeroWeb and compared pixel by pixel, so it measures self-consistency, not a score judged by another browser. It must not be read as comparable to the full-suite scores that Chrome, Firefox and Safari publish on wpt.fyi. The other suites are testharness runs scored by assertion.
Corpus version: suites run against a fixed imported snapshot of upstream WPT (CSS rendering currently v1.10). The snapshot is updated over time, so denominators differ between rows and between months; every count is shown as passed / total.
Reference points, for scale only (different methodology — not directly comparable): mainline browsers pass ~96–98% of the full WPT suite (wpt.fyi); the Ladybird independent engine reports ~93% (ladybird.org).