Catch regressions before you ship

Turn your product flows into repeatable tests. Keep them running on every change to catch regressions.

Terminal
$ com verify scenarios run a-tester-*.yaml no-cookie-*.yaml --wait
Watch run verification_run_dXwVaxj561r2SAEKlNZQB3Mk: https://composal.ai/vex/verify/composal/runs/…
Queued run verification_run_dXwVaxj561r2SAEKlNZQB3Mk.
passed A tester adds and renames an environment then archives only that environment
passed A tester creates a scenario and sees its saved instructions after reopening
passed A tester edits a scenario and sees the new steps without changing its neighbor
passed A tester filters environments and restores the saved environment after clearing search
passed A tester opens a completed run and reviews each scenario result and replay evidence
passed A tester opens Verify and navigates between a project and its overview
passed A tester prepares Discovery with a project environment and cancels before launch
passed A tester reviews credential setup without exposing or changing credentials
passed A tester selects two scenarios and reviews one grouped run before cancelling
passed A tester writes and edits project knowledge then archives the disposable guide
blocked No cookie popups on Vex website and docs
error: run verification_run_dXwVaxj561r2SAEKlNZQB3Mk blocked; see https://composal.ai/vex/verify/composal/runs/…
$

Test in plain English

Write tests the way you describe a user journey.

Run what matters

Run relevant tests for each pull request.

Catch regressions

Flag when a flow that worked before breaks.

1

Build your tests

Turn mapped flows into repeatable tests, or write your own to cover more user flows.

2

Check every change

Run the relevant tests on each pull request or feature.

3

Review and fix

See what passed and what broke, with recordings and evidence. Send failures to your coding agents to fix.

What you can do with it

  • Fix with agent

    Hand the failure to Codex, Claude or Cursor, or copy the prompt. It links back to the run and its results.

  • Retry Verification

    Start a new attempt from the same screen, with the same setup and your latest Scenarios.

  • Replay any step

    Pick a step and the recording jumps straight to it, so you see what went wrong.

  • Run them from your terminal

    Try Scenario files without saving them, and get one line of results for each Scenario.