Skip to main content

Module conformance

Module conformance 

Source
Expand description

The in-app test runner behind day test (docs/testing.md). The in-app test runner (docs/testing.md): runs the #[day::test] cases the binary registers, each drive op as the dayscript step it names, and answers the tests and run_tests steps day test sends. A run is one main-loop task: between a drive’s awaited ops the app’s loop turns, so a native transition settles and a capture paints exactly as they do between a script’s steps.

Structs§

Outcome
One test’s outcome, the shape conformance.json records (docs/testing.md).
RunReport
What a finished run answers.
Shot
A capture a test took, for the runner to write beside the evidence.

Enums§

ShotPolicy
Which captures a run keeps.

Functions§

listing
What tests answers: every registered test, before any runs.
run_tests
Answer a run_tests step: start the run on its first call, then report “running” until the task finishes, when the report is handed over once and the run forgotten. Retryable while running, so the runner’s own wait loop polls it.