Get started

Tada checks your app the way a QA engineer would. It signs in the way your users do, works through a feature in a real browser, and tells you whether it works. Every check opens as a report. With GitHub connected, the verdict also lands on the pull request as a check named Tada.

How Tada works

• An app is one product Tada checks.
• A feature is something your app does, named the way your ticket names it.
• A test is one part of a feature’s proof, written as a few plain steps.
• A check is one go at one feature. It walks that feature’s tests and ends Passed or Failed.
• Every check opens as a report: each test’s result, the step that stopped a failed one, and the film.
• The cast is the people Tada plays in your app, such as an admin and the teammate the admin invites.
• A feature’s demo is the film of its newest passing check. You can send it to anyone.

No AI model decides a verdict on its own. A check follows the steps as written. A step that expects words passes only when those words are on the screen. A step marked as a judgment is answered by a model, and the report says so.

Set up Tada

1. Sign up at app.taada.dev with your email. Tada sends you a sign-in link. There is no password.
2. Add your app by pasting its link. GitHub is optional: connect it as well and Tada also checks your pull requests and can read your code. See Add an app.
3. Give Tada a feature to check. Hand your coding agent the ticket, or ask Rivet. Tada works out the tests that prove it. See Features and tests.
4. Press Check now on the feature and read the report.
5. With GitHub connected, deploy a pull request to staging or a preview. When the deploy finishes, Tada checks the feature the pull request ships and re-checks your other features quietly. The verdict lands on the pull request. See Checks on pull requests.

Where things are

• Tasks is the one list of what needs you: what Tada needs from you, such as a sign-in, and what looks broken in your app. See Tasks.
• Apps lists your apps. Open one for its overview.
• Tests lists your tests with their latest result. Filter by Started by: Pull request to see what each pull request was checked on.
• Features lists what your apps do, and whether each is Passing or Failing. See Features and tests.
• Issues lists every feature that is Failing right now. See Issues.
• Demos holds each feature’s current demo. See Demos.

Using a coding agent

Your coding agent can ask Tada to check a feature before it says it is done, including an app running on your own machine. See Check what your coding agent builds.