Proof and testing
Nothing reaches you without its proof.
Each pull request turns up with the evidence: tests that hold up, screenshots of what the agent saw, and coverage of the lines it changed. Behind all that is a test library your whole team can see.
What comes back with it
Proof you can read for yourself.
By Dawn runs the checks itself, at the commit it proves.
- Tests that hold upThe suites have to pass on the exact commit it’s proving. New or changed tests run 10 times by default, or up to 50, before they count.
- Screenshots in Chrome and SafariThe agent clicks through the app and shows you what it saw.
- Coverage of the lines it changedFrom your CI’s coverage report: how much of each pull request’s changed lines the tests ran, and which lines they missed, checked against your team’s target.
The test library
Your tests, out where the team can see them.
Test cases, suites, runs and plans sit next to the tickets, epics and releases they cover.
- HealthThe flaky and broken tests costing you the most, ranked by how many pull requests and how much CI time they’ve hit. One click puts a test in quarantine.
- Cases, step by stepWrite out the steps and what should happen at each one, for manual or automated cases. Press “Automate this case” and an agent gets a ticket to write the test.
- Runs, by a person or the AI testerGo through a build case by case yourself, or let the AI tester drive the browser and take a screenshot at each step. The suites run on your own CI and machines, not on our servers.
- Sessions and plansTimeboxed exploratory sessions with notes and bugs filed as you go, and sign-off plans for a release or a cycle, drafted by By Dawn and edited by you.
- Tests your agents writeNew tests from your agents stay in quarantine until a person approves them. Build library reads your repos and proposes a starting library, and none of it lands until you commit it.
How it works
How proof reaches you
- RunBy Dawn runs the suites at the commit being proved.
- RepeatNew and changed tests re-run until they’re stable.
- ShowScreenshots and coverage of the changed lines.
- AttachAll of it comes with the pull request.
Questions
Asked about proof and testing.
Where do the tests run?
On your own CI and your own machines. By Dawn runs the checks a mission needs on the machine doing the work, and reads your CI’s results.
Where does coverage come from?
From your CI’s coverage report, matched to the lines each pull request changed.
The waitlist