TestFinch

DocsStart

Report your first bug with Snag

This is the first ten minutes with Snag: an account, your workspace and first project, the browser extension, one captured bug, and what the team sees. Nothing here needs a desktop install.

1. Create your account#

Open the Snag page on testfinch.com and choose Start free, or go straight to app.testfinch.com/register. Registration is one screen: your name, your email, and what you want to do first. Choose "Report bugs"; coming from the Snag page, it is already chosen. There is no password: we email you a link and a six-digit code. Open the link, or type the code on the "Check your email" screen; both end in the same place, whichever browser opens the link. Nothing is created until you confirm your email, and an expired link offers a new one that keeps what you filled in.

If you already have an account, sign in at app.testfinch.com/login. If you sign in there without a workspace of your own, the app asks what you want to do first on one "Set up your workspace" screen.

2. Land in your workspace#

Confirming creates your workspace, with you as its admin, and a first project. Both are named for you, from your email's domain or your own name, and you can rename them in settings. A project gets a short key (three characters) that prefixes every bug's reference, such as ANA-12. You land on that project's Overview, with "Get your first result" at the top and the Bugs track first: install the Snag extension, file your first bug, invite a teammate. The checklist is for the workspace's admins. Each step turns done by itself from what you did; "Hide this" puts the card away for you on this project. The Feedback workspace, where you can send us feedback, sits last in the workspace menu as "Send feedback to TestFinch", and it opens only when you choose it.

3. Install the extension#

"Add to Chrome" on the checklist opens Settings, then Extension and apps, which links to the Chrome Web Store listing. Chrome, Edge, Brave and other Chromium browsers install it the same way. After installing, open the extension, choose Sign in with email, then Sign in with your TestFinch account; it opens TestFinch in a tab once to connect, and from then on it knows your workspace and projects. The step turns done once the extension has signed in that way, or once you file a bug from it. On Android, install Snag from Google Play and share a screenshot or a screen recording into it from any app. On iPhone, request the TestFlight beta from the same settings page.

4. Capture a bug#

Open the page where the bug happens and click the Snag launcher the extension adds to the page, or the extension's icon. Choose a region, the full page, or record up to 90 seconds of the tab when the bug only shows in motion. While you browse, the extension keeps the last clicks and navigations, console errors and failed requests in memory; they are attached automatically, you do not have to collect them. Mark up the screenshot if it helps (circle the problem, blur what should not be shared), give the bug a title, pick the project, and file it.

5. What the team sees#

The bug appears in the project's Inbox column with its reference. Opening it shows the screenshot or recording, the page and browser, the trail of steps that led there, the console errors and the failed network requests from around the capture. Triage happens on the card: severity, assignee, labels, a release. Columns run from Inbox through In progress and Fixed to Verified and Closed.

6. Invite a teammate#

"Invite" on the checklist opens the invite dialog. A member works on the board with you; a reporter, such as a client tester, files bugs and sees only their own. Invited people get an email whose link signs them in and lands them on the project, or on the workspace's projects. Members and reporters see one short card instead of the checklist: a reporter is asked to install the Snag extension until their first bug, and a member is pointed at the project until they open it.

7. Next#

  • Tell Slack: Settings, then Integrations, connects a workspace channel; each project can post to its own.
  • Give your coding agent the tracker: Agents has the connection details for Claude Code, Cursor and other MCP clients; the agent reads the bug with its evidence and marks it fixed.
  • Prove the fix: the Tests track of the same checklist points the AI agent at your site, and a bug can be reproduced as a test from its trail that keeps running after every deploy. See the FlowQA first-test guide.
  • Try Team: on Free, the checklist offers a 14-day trial of Team with no card; a plan button on the pricing page starts it for you when you register.