Inspect the sample test catalog#

The sample-site catalog contains standalone Markdown tests and nested section.md files. It covers the profile form/navigation, intentional buggy and fixed persistence, plain HTML, and the branding/recording prototype.

Inspect before running#

From a configured SnagBadger checkout:

node tooling/testing/plan.mts inspect --catalog examples/test-plans/sample-site

Inspection reports selectable references, inherited tags, alternatives and unselectable coverage gaps without operating a browser. Definitions and needed ancestor settings validate when reached. Catalog format explains the fields.

Follow one definition#

Read fixed save survives in-page navigation, then its fixed section and root section. The inherited setup supplies the host URL, fresh context, and mode; the leaf defines the specific behavior.

The root asks for a screenshot, leaves video optional, and forbids real tracker submission. Recorder cases can strengthen evidence requirements. Destination SAMPLE is illustrative metadata, not credentials or a working transport.

Interpret intentional failures#

The buggy-mode persistence tests assert the product expectation and should fail on the intentionally buggy host. Their known-failure tags identify that purpose; there is no xfail schema silently converting failures into passes. The fixed-mode tests assert the corrected behavior.

Catalog presence is not execution evidence. Run only through a verified runtime and active coordinator, keep actual observations, and distinguish missing proof from an observed behavior failure.

To adapt the catalog, preserve stable IDs where the scenario stays the same and replace sample URLs/fixture guidance deliberately. Authoring guide shows a minimal definition and selection guide explains tags and IDs.