Ripplo

Ripplo connects directly to your coding agent via MCP — so tests are generated as you build, not bolted on after the fact.

Your entire codebase is mapped into a workflow graph: pages and paths users actually take. Run bulk coverage checks with Playwright or agentic tests with configurable agent profiles like a malicious user, accessibility agent, the elderly, etc. Test locally as you build new features in ensure nothing breaks in prod.

Install with a single npx command

Key features

Workflow graph mapping — Ripplo auto-generates a live map of your application's states and transitions. No manual test spec writing to get started. The graph becomes your test coverage surface.

Bulk test runs — Run tests across any combination of workflows simultaneously. Schedule them to run on a cadence, after deploys, or on demand. Results surface in the Run Console — a live feed of what's running, what's queued, and what recently finished.

AI agent testing — Beyond functional coverage, Ripplo runs specialized agent profiles against your workflows: security probes, accessibility audits, UX friction analysis. Each agent runs with a defined goal and reports back with findings and Playwright-recorded failure paths.

Multi-agent simulation — Simulate concurrent users across N agent profiles and geographic locations in a single test run. Surface race conditions, latency failures, and region-specific issues before your users do.

Playwright-documented failures — Every failure includes a step-by-step reproduction path recorded via Playwright. No ambiguity about what broke or how to reproduce it. Hand it to any developer and they can get to a fix immediately.

Notifications and alerting — Get alerted when workflows fail via your preferred channel. Configure per-workflow thresholds and catch regressions the moment they happen, not during the next sprint review.

Run history and audit trail — Every test run is stored with full results history. Track coverage trends, compare runs across deploys, and maintain a record for compliance or incident review.

What makes Ripplo different

Most testing tools require you to write and maintain test specs manually — a significant time investment that small teams consistently deprioritize. Ripplo starts with the graph and generates coverage from your actual application structure, not from tests someone had to author.

The agent layer is also distinct. Rather than just checking whether things work, Ripplo checks whether things work well — catching accessibility violations, security surface issues, and UX friction that functional tests miss entirely.

And unlike enterprise-focused QA platforms, Ripplo is built for teams that don't have a QA org. The defaults are opinionated, the setup is fast, and the output is actionable for developers, not test managers.

What you can expect

• Ship with confidence without adding QA headcount
• Catch regressions before users do, automatically
• Get failure reports that are immediately actionable — no hunting through logs
• Test across concurrent users and geos without building infrastructure to do it
• Maintain a test history that grows with your product