From your website to reliable tests
Map your app, choose the behavior that matters, and check it again as your product changes.
Map your app
Start with your website URL. Proof explores the app in a browser and records the pages, actions, and possible tests it finds. You can correct its understanding before you choose which tests to write.
Review the selected tests and their expected results before you confirm. After Proof writes and verifies them, run saved tests and inspect the evidence. See Context and tests and the run guide.
What Proof does
Proof turns confirmed cases into saved browser tests. Each test uses Playwright, a browser testing tool, to execute saved browser programs.
Confirm expected results and permitted actions before Proof writes tests. Fresh browser verification must pass before new coverage becomes active.
Use the website workflow
Use Projects for mapping and Tests for saved tests. Runs use saved browser programs without model calls. Repair is an explicit action. Use the coding-tool connection to request a specific feature test or run saved versions.
The CLI, Slack, Jobs API, GitHub, and monitoring references describe a separate earlier workflow. They do not operate on mapping tests.
Key terms
A Test verifies confirmed expected behavior. A Finding describes an observed concern and its evidence.
An Environment holds a website URL and account settings. Mapping proposes cases. Writing creates and verifies tests. A Run executes saved tests.