Free tools for screenshots, test templates and bug reports
Docs
How Snag and FlowQA work, for the people setting them up and the coding agents working beside them. Start with your first bug, then hand it to your agent.
Start
- Report your first bug with Snag
Register, land in your workspace, install the extension, capture a bug, and what the team sees: a first session in ten minutes.
- Create your first regression test with FlowQA
Register with your site's address, let the AI agent explore it, get a generated or recorded test, read its assertions and run it again: what needs the desktop app and what does not.
- Set up with your coding agent
One page your coding agent follows end to end: connect to TestFinch, find the project, read and fix a bug, write and run a test, with a check after each step.
Snag
- Capture and triage bugs with Snag
What the extension, the phone app and the share sheet capture, how a bug moves across the board, and how it reaches the person or the agent fixing it.
FlowQA
- Schedules and CI for FlowQA
Run tests on a schedule or from your deploy pipeline, and get told when they fail.
- The TestFinch CLI
Run your tests from a terminal, an agent or CI, on cloud browsers or against localhost, and fix bugs from the shell.
- GitHub deploy hooks
Connect the GitHub App, pick a repo, and every successful deployment runs the regression and reports a check on the commit, or every pull request gets a check and one comment from its preview.
- Site notes: what a project knows about its site
The knowledge base explorations write and people correct, read before every run.
- When the AI agent asks a person
Which element, what value, may it follow a host, is it done: how questions and answers travel.
- Repairs: when a test fails on a changed page
FlowQA proposes one small change, proves it twice, and waits for your approval.
Agents and API
- Coding agents: write and run tests from your terminal
Connect Claude Code, Codex or Cursor to TestFinch, and the agent writes, runs and fixes FlowQA tests in your project.
- The FlowQA authoring guide for agents
What a coding agent reads before it writes a test: steps, assertions, openings, the loop, and three example tests.
- The TestFinch CLI guide for agents
What a coding agent reads before it uses the testfinch command: signing in, linking a repository, running tests, mapping a site, fixing a bug, and every exit code.
- The FlowQA API
Authentication, the routes for projects, tests, drafts, runs, explorations, repairs and schedules, and the errors they answer, for scripts, CI and agents.
Billing
- Billing questions
Runs, explorations, the trial, credits and how long files are kept.