Test Execution
Regression Manifests
Compile a baseline crawl into a deterministic manifest for exact replay. Ensures consistent regression testing.
Regression Manifests
Regression manifests enable deterministic replay of a baseline crawl — visiting the exact same pages and performing the exact same interactions every time.
Why Manifests?
Exploration crawls have inherent variance — different runs may discover pages in different order, interact with different elements, or find different states. Regression manifests solve this by compiling a known-good crawl into a fixed blueprint.
How It Works
- Crawl your site — run a normal exploration crawl
- Set as baseline — click "Set as Baseline" on the crawl results page
- Manifest is compiled — pages, interactions, and their order are extracted from the baseline
- Run regression — click "Run Regression" to replay the manifest exactly
Setting a Baseline
From any completed crawl page, click Set as Baseline. This compiles a manifest containing:
- All discovered pages in crawl order
- All interactions per page (click actions, form submits)
- Expected page count and state count
Running a Regression Crawl
From the crawl page or the New Crawl modal, select Regression mode. The crawler will:
- Visit each manifest page in order
- Execute each recorded interaction
- Capture screenshots and DOM state for comparison
- Report matched vs missing pages and states
Manifest Policy
| Option | Description |
|---|---|
allowNewPages | Accept pages discovered that are not in the manifest |
strictPageOrder | Pages must be visited in exact manifest order |
Exploration vs Regression
| Exploration | Regression | |
|---|---|---|
| Pages | Discovers new pages | Visits only manifest pages |
| Interactions | Discovers new interactions | Replays recorded interactions |
| Consistency | Varies between runs | Deterministic |
| Speed | Slower (discovery overhead) | Faster (no discovery) |