Case study

We pointed Ripplo at Formbricks

Formbricks is an open-source survey platform we had never touched. We let Ripplo run against it for an afternoon. It found five bugs in user workflows.

49workflows53tests5bugs found
Browse the live project

Watch Ripplo catch a bug

Deleting the last response crashed the modal. Here is the run that caught it, frame by frame, with the check that failed.

Could not load this page.

Five bugs in user workflows

Each one links to the report, the diff, and the run that caught it.

Deleting the last response crashed the detail modal

The modal guarded on a stale index instead of the derived response row, so removing the final response threw instead of closing.

Publishing a draft rewrote stored question headlines

Opening the editor round-tripped headlines through a rich-text export that persisted cosmetic bold tags into survey content.

Deleting a workspace landed you in the wrong organization

The redirect hint was written to a different localStorage key than the redirect read, sending users to a stale org.

Duplicating a survey silently dropped 19 settings

The copy lost PIN protection, reCAPTCHA, email verification, scheduling, and redirect settings. Publish the duplicate and the PIN is gone.

Long menus rendered items off the top of the screen

The shared dropdown had no max-height binding, so the add-question type list overflowed with no way to scroll.

How the explorer navigates the app

Four workflows from the model, with the clicks and the state each one leaves behind. Each step declares what's reachable from where, so Ripplo can move from one workflow into another and keep going.

Create the first survey in an empty workspace
open the workspace→start from scratch→create surveychanges surveys
Publish a draft survey
open the editor→open settings→publishchanges surveys
Answer a published link survey
open the share link→fill an answer→submitchanges responses
Delete a response
open the responses tab→expand a response→choose delete→confirmchanges responses
Highlighted: an 11-step route the explorer took through all four — create a survey, publish it, answer it, delete the answer.

Each workflow you add widens what the explorer can reach. It runs paths nobody wrote and still knows what should be true when it gets there.

See the workflows and the state binding →