Skip to main content

Module report

Module report 

Source
Expand description

The reports this repository generates as web surfaces: the test run, the benchmark run, the UI conformance audit that is a section of the first, and the UI itself read once at a pinned commit, which a publication carries at the UI’s mount (snapshot, ADR 0141).

A report is a rendering of evidence somebody else produced. The suite writes its results, the benchmark run writes its own, and this module turns either into a directory under the generated web root: an index.html a person reads, the machine-readable results beside it, and the surface.json that declares what the directory is for. It renders; it never runs anything and never decides what passed.

The HTML is deliberately self-contained — its own style, no external asset, and every link relative — so that the same directory works at /tests, at /reports/tests or opened from disk. That is the whole of the “static-safe URL” problem, solved once by not creating it.

Re-exports§

pub use super::html;

Modules§

tests
The test report: the suite’s own results, rendered.
ui
The UI conformance report: what a browser found on every page of the built site.

Structs§

Origin
What a report says about where it came from, printed on every page.

Functions§

declare
What every report writes beside its rendering: the declaration that makes the directory a surface.
declare_if_absent
Declare a surface only when nothing has declared it yet.
directory
Where a report’s directory is, absolute.
write
Write one file inside a report’s directory, creating what it needs.
write_json
Write a value as pretty JSON beside a rendering: the evidence the page was made from, kept because a page nobody can check is not evidence.