Scenarios and catalog
Proof stores business intent separately from browser actions so coverage can survive markup changes and grow with the product.
Business flows
A business flow is a customer outcome worth protecting, such as “a customer can complete checkout” or “an administrator can revoke a member.” It carries priority, risk, confidence, provenance, and approval state, but no DOM selectors.
Scenarios and edge cases
A scenario makes one flow testable. It defines an intent, preconditions, success criteria, cleanup obligations, and a risk level. Discovery proposes the consequential happy path and justified edge cases it finds in source and runtime evidence.
Natural-language requests first pass through deterministic ambiguity policy. Proof records harmless assumptions and continues, but asks for clarification when uncertainty changes scope, credentials, permissions, financial or destructive side effects, or the observable meaning of success.
| Kind | Purpose |
|---|---|
| happy path | The primary successful customer journey. |
| validation | Invalid or incomplete input is handled safely. |
| empty state | The product remains useful without existing data. |
| permission | A role can do only what it is allowed to do. |
| lifecycle | Create, update, archive, and restore transitions. |
| retry | The product recovers safely after a transient failure. |
| destructive | Deletion and irreversible actions require correct safeguards. |
| integration failure | An external dependency fails or returns an unexpected result. |
| responsive | The outcome remains available at a constrained viewport. |
| accessibility | The flow works through accessible roles, names, and states. |
Success criteria and evidence
Each criterion declares the observable evidence required to count as success: URL, visible text, element state, network response, database effect, download, or screenshot. Protected criteria cannot be silently weakened during healing.
From exploration to deterministic catalog
- The browser explorer reasons through the scenario from screenshots and semantic page state.
- An independent verifier checks every required outcome.
- Proof normalizes the successful attempt into a selector-independent semantic trace.
- The compiler produces a standalone Playwright test with accessible locator preferences and secret references.
- The candidate must pass three deterministic validations before becoming active.
Coverage links and pull requests
Coverage links connect a scenario to routes, files, APIs, schemas, and other product surfaces at a specific repository revision. Pull-request selection uses these explainable links, then performs exact-commit rediscovery so the catalog can expand when new behavior appears.