Common questions
Questions people ask before connecting a project.
A pull request review runs existing tests against the preview, repairs definitions on a temporary branch, and investigates the changed behavior. Coverage reviews update the shared tests against your validation environment.
Results include issues and their recordings. See the documentation for details.
Ripplo tests a server you point it at, usually the preview environment for the pull request. Start a review by commenting @ripplo review on the pull request, or turn on Review every push so each preview deploy starts one.
Choose New review → Coverage from Reviews to update the shared tests after changes merge.
Each run creates the data it needs before the first click, through your app's own APIs from the test user's browser session, and tears it down when the run ends. Ripplo holds no database credential. Runs never share data, so they can run at the same time and leave your dev database as it was.
If Ripplo cannot create the data a workflow needs, it warns you and asks either for test data or for an API it can use. Date-dependent data, like a payroll due on a given day, is created the same way. Ripplo does not simulate the passage of time or run tests that last for hours.
Yes. Think of a workflow as one route through your app: the pages a user visits and the buttons they press. Ripplo writes each route once and runs it many times with different starting data.
Take generating a W-2. On screen it is the same route in every US state, so Ripplo writes one workflow and runs it fifty times, once per state, each starting with that state's payroll data. Where a state needs different screens, it gets its own workflow.
Run npx ripplo setup in your app’s repository. It installs the GitHub App, creates an OpenID Connect connection, and prints the three RIPPLO_IDP_ variables to register in your app's auth library, outside production. Choose New review → Coverage from Reviews to create coverage. Comment @ripplo review on a pull request with a preview deployment to check its changes.
See the documentation for details.
A job is one review that Ripplo finishes: a pull request review, a coverage review, or a review you start from the dashboard. Every job costs the same. A review that fails or that you cancel does not count.
Each plan includes a number of jobs a month. When you reach it, Ripplo starts no new jobs until the month resets. An admin can set a monthly cap on the billing page to allow extra jobs at $2.50 each. The billing page shows where you stand.
No. Ripplo runs against the dev, preview, or staging environment you point it at, and signs in only where you add the sign in with Ripplo connection. It never needs your production database or your users' data.
Yes. A review clones your repository with a read-only token to work out which workflows cover the change, then writes the ones that are missing. The clone is deleted when the review finishes. The reviewer's log keeps the parts of your code it read.
Three things: your account and billing details, your workflows, and your review results with a recording of each run. Account, workflow, and review data lives in our database on AWS. Recordings live in Amazon S3.
Ripplo keeps your account, workflows, and review results until you close your organization or ask us to delete your data. You can delete your organization from the dashboard, or email mail@ripplo.ai to delete specific data or everything.
Synthetic monitoring watches production after a release ships. Ripplo runs on the pull request, before merge, so it catches the bug before it reaches production.
Ripplo also checks your database. A payroll run that saves the wrong withholding amount fails, even when the screen looks right.