Pull request checks, with a report for every check

Tada checks a feature each time a pull request deploys. It opens the build in a real browser, signs in, works through the feature the way a QA engineer would, and posts the verdict on the pull request as a check named Tada: Passed or Blocked.

A code review reads the diff. Tada opens the build and uses it, so a feature that stopped working is caught on the pull request that broke it.

What you can do

• Connect an app through GitHub. Install the Tada GitHub App and pick the repository.
• Name the feature to check. Tell Rivet, the QA inside Tada, in your own words. She writes the test and saves it to the feature.
• Get the verdict on the pull request. When a pull request deploys, Tada checks the feature and posts Passed or Blocked. You can also start a check by hand.
• Read the report. One verdict, a result for each test, and for anything Blocked, the step where it stopped and what the page showed instead. The feature reads Failing until a check passes again.
• Share the demo. A feature's demo is the newest film of it passing, on a link anyone can open without signing in.

The cast

A test can have more than one person in it: an admin sends an invite, and a teammate accepts it. Each person in the cast has a name, a face and a voice, and Tada films a check with several people like a call. Tests with more than one person are switched on per workspace for now.

Plans

The Free plan includes 40 checks a month. Paid plans start at $29 a month. Pricing lists what each plan includes.

Get started

Create an account, connect GitHub, and tell Rivet the first feature you want checked. The docs cover each step: Add an app, Checks on pull requests, Verdicts and Rivet.