Context and tests
Approve short project and user flow documents, then let Proof write and run tests from that context.
Context documents
Each Project has one connected repository, one master Markdown context document, and short Markdown descriptions of its main user flows. These descriptions explain the behavior. They are not test checklists. You review and approve the documents together.
Tests
A generated test describes one way to verify an approved user flow. It records the expected result, setup, success evidence, cleanup, and execution safety. Each test-writing run uses a fixed copy of the approved context.
Proof records harmless assumptions and continues. It asks for clarification when uncertainty could change scope, access, spending, destructive effects, or the expected outcome.
| 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 states the evidence needed for success. Evidence can include a URL, visible text, element state, network response, database effect, download, or screenshot. Proof cannot silently weaken protected criteria when it updates a test.
From exploration to a saved test
- Proof works through the test from screenshots and the current page state.
- It checks each required outcome.
- It saves the verified path without tying it to code selectors.
- It produces a standalone Playwright test with safe secret references.
- The test must pass three repeatable checks before it becomes active.
Coverage links and pull requests
Coverage links connect a test to routes, files, APIs, schemas, and other parts of a product at one repository revision. Proof uses these links to select tests for a pull request. It reviews new behavior so the catalog can grow when needed.