Docs
How it works
The same documents the team builds from. Written for people setting the products up and for the agents working beside them.
Report your first bug with SnagAccount, project, the extension, a capture, and what the team sees: a first session in ten minutes.Create your first regression test with FlowQAAccount, a project pointed at your site, a recorded or generated test, its assertions, and a second run: what needs the desktop app and what does not.Schedules and CI for FlowQARun tests on a schedule or from your deploy pipeline, and get told when they fail.Repairs: when a test fails on a changed pageFlowQA proposes one small change, proves it twice, and waits for your approval.Site notes: what a project knows about its siteThe knowledge base explorations write and people correct, read before every run.When the explorer asks a personWhich element, what value, may it follow a host, is it done: how questions and answers travel.The explore-click benchmarkWhat the 97.5% on the FlowQA page measures, on which sites, how right is counted, what it does not show, and how to run it.Plans, allowances, credits and retentionHow a workspace is billed, what each plan includes, and what the limits mean in practice.The FlowQA APIProjects, tests, drafts, runs, schedules and the worker protocol, for integrations and agents.