How to read ZeroWeb WPT and performance results
Understand self-source reftests, assertion-based suites, changing corpus sizes and p95 benchmarks before comparing results.
What WPT means
Web Platform Tests is a shared test suite for web platform behavior. ZeroWeb imports fixed snapshots and tracks selected suites. A tracked subset is not the complete upstream suite.
Self-source reftests
For the CSS rendering series, ZeroWeb renders both the test page and the reference page and compares their pixels. This measures self-consistency. Both pages can share the same defect and still match, so a pass alone does not prove Chrome-equivalent rendering.
Assertion-based suites and browser comparisons
Testharness suites report assertions about observable behavior. Separate Chrome comparisons inspect page output or interactions against another browser. These methods answer different questions and should not be merged into one compatibility percentage.
Keep the denominator
Always read passed / total, unit, corpus version and date together. A row counted in files differs from one counted in subtests. Planned suites have no measurement; they are not zero-score tests. The monthly rendering series takes the latest recorded result for each month, not an average.
Read performance within its conditions
The data page reports p95 values from the recorded benchmark series and identifies its runner class. Compare the same metric, unit and environment. A runner-class label alone cannot prove identical hardware or eliminate measurement noise. The page's newest data date can come from one suite while another chart remains older.
Inspect the published tables and their raw-data links. Sources: metrics generator, test runner, WPT documentation.
Engineering guides
How ZeroWeb tests AI-autonomous software engineering
A browser gives AI development a long-running test case: architecture, code, debugging and verification must work together.
ZeroWeb Rust browser architecture: from request to pixels
Follow the page pipeline and the boundaries between the browser application, embeddable WebView, engine and rendering infrastructure.
Getting started with ZeroWebView and ZeroBrowser
Prepare a local checkout, launch the desktop browser and inspect the WebView API before embedding the experimental engine.