Scenarios

Save the whole broken state. Hand it to anyone.

Bundle mocks and transforms into a named app state — "Guest checkout with expired card" — and flip the entire set in one click.

"Repro steps: log in as the demo user, add two items, wait for the third-party quote to time out…"

"I've tried four times. I can't get it into that state."

Send a scenario instead. Same mocks, same responses, same bug.

Record & flip a scenario

Pick Payment declined — four toggles light up at once.

  • Scenario cards with override counts and routes
  • One dropdown flips the whole state
  • Same switch as a curl PUT for CI

Record one instead of building one.

Hit Record scenario, click through the flow in your app, hit stop. FlowMock shows you every request it captured and you tick the ones that define the state. It creates the overrides for you — including splitting one endpoint into several overrides when the query or body differed. The fastest scenario is the one you didn't have to write.

In-product visual

Name them after the user story.

"Guest checkout with expired card" beats "scenario 3". Every scenario gets an id (scn_…) and a URL-friendly slug, so a link in a ticket is a working reproduction, not a paragraph of instructions.

In-product visual

Reproducible dates, reproducible fakes.

Freeze the scenario's clock and every relative date inside it holds still. Seeded fake values derive from the scenario id, so everyone activating it sees the same generated names and emails. A demo recorded in March still demos in August.

In-product visual

Layer a one-off on top.

Activating a scenario replaces the previous one — clean slate, no residue. Individual mocks stack on top of it, so you can take "Empty store" and add one extra 500 for the edge case you're chasing, without forking the scenario.

In-product visual

One call from CI.

PUT a session with the scenario id, run the suite with x-flowmock-session, then tear down. The state your tester found by hand becomes the state your pipeline asserts on.

In-product visual

Activate a scenario from CI

curl -X PUT "https://api.flowmock.dev/api/v1/sessions/ci-42" \
  -H "Authorization: Bearer fmk_…" \
  -H "Content-Type: application/json" \
  -d '{"project":"checkout","environment":"staging","scenario":"scn_paymentDeclined"}'

Take the library with you.

Export a project's mocks and scenarios and import them into another. New environment, new project, same test states — without rebuilding them by hand.

One URL change. That's the whole integration.

Free plan, no card, two-minute setup.