Flows captures your browser actions and converts them into production-ready test scripts. Playwright, Cypress, Puppeteer. AI-powered selectors that survive UI changes.
Record once, export to the testing framework your team already uses. Full Page Object Model support, clean code, ready for CI/CD.
TypeScript or JavaScript with async/await. Full Page Object Model generation.
Modern E2E with built-in assertions and automatic waiting. cy.* commands.
Headless Chrome automation. Direct CDP access for advanced scenarios.
Not a toy. We use Flows daily on client projects. Every feature exists because we needed it.
Intelligent selector generation using data attributes, ARIA roles, and text content. Creates stable locators that survive UI changes without breaking your tests.
Automatically detects network requests, animations, and loading states. Generates appropriate waits without hardcoded timeouts that flake.
Auto-generates visibility, text content, and state assertions. Add custom assertions with a single click.
Review and modify recorded steps. Add variables, loops, and conditions directly in the UI before exporting.
Connect Flows to AI agents via Model Context Protocol. Let Claude or other LLMs control browser automation directly.
Give Flows a URL and requirements. It explores, designs, creates, runs, and heals tests autonomously.
Playwright crawls the site, discovers forms, buttons, and navigation
AI architects a test suite from the element catalog
Step groups, elements, and flows persisted automatically
Suite runs with setup and teardown before and after each test
Self-healing selectors fix themselves at runtime, zero maintenance
Claude IS the designer. Explore-only mode returns the element catalog, and Claude designs the suite directly. No external API key needed.
Connect via MCP, call flows_generate_from_prompt with a URL and requirements. Works with any MCP-compatible editor.
Set a Google, OpenRouter, or OpenAI API key. The AI explores, designs, and creates without human input.
We automated with AI - every test passed, nothing worked. That's why we build tools that keep humans in the loop.- BetterQA Engineering
Generate full test suites from a URL, or let Claude analyze failures and fix selectors - all via MCP (Model Context Protocol).
The Flows MCP server is now publicly available. Install it globally and connect to Claude Desktop or Claude Code:
npm install -g @betterqa/flows-mcp
View on npm registry
Add to your MCP config:
{
"mcpServers": {
"flows": {
"command": "npx",
"args": ["@betterqa/flows-mcp"]
}
}
}Add to claude_desktop_config.json:
{
"mcpServers": {
"flows": {
"command": "npx",
"args": ["-y", "@betterqa/flows-mcp"]
}
}
}Debug flows without the extension running. Data syncs to ~/.flows/
Get human-readable analysis of failures: timeouts, stale elements, click interception
Score your flows for stability, identify brittle patterns before they break
Claude finds alternative selectors from your element library
Tell the AI what to test
Playwright explores the site
AI designs and creates suite
Run tests, auto-heal failures
Results sync to BugBoard
flows_generate_from_prompt
One-shot: URL + requirements to full test suite
flows_explore
Discover site elements with Playwright
flows_create_from_design
Create suite from AI-designed JSON
flows_analyze
Debug failures, suggest fixes
flows_fix_selector
Apply selector fixes
integration_run_and_report
Run flows and submit to BugBoard
See how Flows and BugBoard work together. 15 minutes to understand your testing needs.
Need help with software testing?
BetterQA provides independent QA services with 50+ engineers across manual testing, automation, security audits, and performance testing.