BlogFlowQA
An Octomind alternative: where to take your generated Playwright tests
Octomind shut down at the end of May 2026. Teams that liked auto-generated tests from a URL with a pull-request check can get the same shape, with a human-reviewed plan and tests that must fail on a broken page before they are kept, at a published price.
Octomind generated Playwright tests from a URL and ran them on pull requests; according to AI QA Directory's list of AI testing tools that have shut down, the product was turned off at the end of May 2026 and the company wound down by the end of June. If that was your workflow, FlowQA gives you the same shape: point it at a URL, get a suite, run it on every deploy. It adds two steps that address why generated tests often did not earn trust: a plan you review before tests are written, and a check that each test passes twice on fresh sessions and fails on a page broken the way its assertions describe.
What Octomind offered#
Auto-generated end-to-end tests from a URL, cloud runs, schedules and a pull-request integration, at published prices. Its last prices, as reported by TestMu AI, a competing vendor and checked there on 27 October 2026, were Basic at $89 a month with 240 cloud runs and Pro at $589 a month with 1,800 runs; Octomind's own site is offline, so we could not check them there. Neither source we could check says whether a free tier or trial was still offered at the end, so we leave it out. It was a well-made hosted Playwright with generation on top. The same TestMu AI page says Octomind's farewell letter cited a lack of market validation, which is a lesson about the category: a better hosted Playwright on its own did not sell.
What is the same in FlowQA#
- Point the agent at a URL and it maps the site and generates tests.
- Run on every deploy from your pipeline, with the result as a status and a message when it fails.
- Cloud browsers included, local runs free.
- Tests are exportable; your suite is yours.
What is different#
You review the plan first. After mapping, the agent proposes journeys with their outcomes. Crossing off the irrelevant ones and correcting the outcomes is where generated suites go from plausible to useful.
Every explored test must be able to fail. A generated test that passes tells you little until it has failed on a broken page. FlowQA replays each test twice on fresh sessions, then hides the text or element its assertions look for and runs it again; a test that still passes is not kept. That shows the test is repeatable and its assertions can fail, not that they check the right thing, so the assertions are still worth a read. A test whose only assertion is a URL cannot be broken from inside the page, and is marked as unchecked.
Repairs wait for a person. When a page changes, one small repair is proposed, replayed twice on fresh sessions, shown with its reason, and approved or rejected.
The agent asks when it cannot know. A code from an inbox, which of two buttons, whether to follow a link to another host. Answers are kept.
Bugs and tests in one workspace. Snag captures what slipped through, with the screenshot, steps, console and network; a bug becomes a test; a failing test files a bug; your coding agent works with both over MCP.
Prices, side by side#
Octomind's last prices as reported by TestMu AI, against FlowQA's monthly prices as of 27 October 2026; both are monthly.
| Octomind (last reported) | FlowQA | |
|---|---|---|
| Free | Not confirmed by a source we could check | 1 project with up to 100 saved tests, 10 of them AI-generated each month (50 with your own model key); 1,000 cloud test runs a month |
| Entry | $89 a month, 240 cloud runs | $49 a month, unlimited tests, 3,000 cloud test runs, 3 explorations |
| Growth | $589 a month, 1,800 cloud runs | $149 a month, 15,000 cloud test runs, 10 explorations, 15 members |
| Generated tests | Not reported | 10 credits per accepted test beyond the allowance, 2 with your own model key |
| Trial | Not confirmed by a source we could check | 14-day trial of Team, no card |
Moving over#
Export what you can from your old suite as a list of journeys: start page, steps, outcome. That list is the plan. Give it to the agent with your staging URL and a test account, review what it proposes, and let it generate and check the tests. How long that takes depends on how many journeys you bring and how many questions the agent has to ask about your site.
FlowQA explores your site, writes the tests, keeps each one only once it fails on a page broken the way its checks describe, and runs them after every change.
See FlowQA