Documentation
Documentation
How Fire Your QA works, what it needs and how to run it.
What Fire Your QA is
Fire Your QA is an AI QA engineer. It tests changes to your web app in a real browser, then reports back with a verdict, screenshots, evidence and a short narrated video. It has two parts:
- The
qacommand tests a branch, ticket, pull request or scenario, by hand or automatically for every merge. - Regression suites are automated tests for every area of your app, written by agents and run in your CI.
Both share a library of reusable test steps that grows with every run.
What it needs
- Your repositories, and a staging or test environment of your app.
- An API key from your AI provider: Anthropic, OpenAI or Google.
- Access to your ticket system, docs and team chat, so it can read context and publish results.
- For parallel runs, a machine that runs private copies of your app. We set this up with you.
Founding customers get all of this set up with them. You don't need to install anything to start.
Verdicts
| Verdict | Meaning |
|---|---|
| PASS | The change does what the ticket describes, and nothing nearby broke. |
| FAIL | At least one finding, with expected against actual and where it comes from. |
| INCONCLUSIVE | Only when something outside your code blocked the test, and it is named in the report. |
Next steps
Read the quick start to see a first run, or the CLI reference for every command.
Fire your QA backlog,
not your team
Let agents test every pull request, keep your regression suites green and send your team clear reports, videos and bug tickets.