Checks and reports

A check is one go at one feature. Tada opens a real browser for each person the feature needs, walks every test of that feature step by step, and ends Passed or Failed. Every check opens as a report.

What starts a check

What happened	What Tada checks
A deploy finished on staging or a pull request preview	The feature the pull request ships, in full, with a film. Every other feature is re-checked quietly, as a guard.
You pressed Check now on a feature	Every test of that feature that is switched on
You asked Rivet to check it	Every feature of the app
A schedule came due	Every feature, on that environment. See App settings.
Your coding agent called verify_feature	The tests the agent sent

Tada also starts checks of its own: while it learns a new app, when it tries a test Rivet just wrote, and once a night on each app’s staging address. The nightly check shows a feature that has started Failing before a pull request meets it.

What counts toward your plan

• A pull request counts as one check, however many features your app has. The feature it ships is the check you pay for. The quiet guard checks of the rest never count.
• Checks you start, and checks a schedule starts, count when they end Passed or Failed.
• A check that didn’t finish never counts. That one is on Tada.
• Checks Tada starts on its own never count.

See pricing for what each plan includes.

Read a report

Open a check from Tests (filter by Started by: Pull request), from a feature’s Checks list, or from the link on the GitHub check. It opens as a report.

• The heading says what was checked, for example Report on #482.
• Demo is the film of a check that passed, with a chapter for each test. For a failed check the film is titled What broke, on film.
• Results lists each test: Passed, Failed or Not reached. Open a test to read its steps.
• What broke names the step that stopped the check, what Tada did, what it expected and what it saw.
• The cast shows who played these tests.
• Check details says when, where and on what the check was made.

From a report you can:

• Share demo, on a check that passed. See Demos.
• Copy as bug report, on a check that failed. It copies the test, the step, what was expected and what was seen, with a link back to the report.
• Re-check the feature against the app’s current address.
• Accept as expected, when the app changed on purpose and the test should follow it.

A failed check’s film is private to your workspace. It has no share link.

A guard check, made quietly beside a pull request, has results and no film.

When a check runs out of time

A check has a time limit. One that runs out of time ends as Didn’t finish, not Failed, because it proved nothing about your app.