Use case

Find the edge cases before the big release does

Before a major release you want every important flow checked and every risky area pushed hard. Composal runs your Scenarios and a Deep Scan across what changed, and hands you the bugs with the steps to reproduce them.

Read the docs
Release 2.0 · before you ship
All ScenariosPassed
Deep Scan · Billing 2 bugsNeeds a look
Deep Scan · OnboardingClean
Deep Scan · ExportsPartly covered

Where the time goes today

The manual pass is a room full of checklists

A group of people follows a script for days. They get numb on repetitive steps, and the findings tend to be the obvious ones.

Scripts only find what they were told to

Tests cover the new capability and the paths you thought of. The strange interaction with an older feature is nobody’s script.

You learn the result at the worst moment

The surprises arrive in production, after the announcement.

1

Run everything you have written down

Every saved Scenario runs against the release candidate, in parallel, with a result for each.

Every saved Scenario, in parallel
Sign up and verify emailPassed
Invite a teammatePassed
Change a planFailed
Export a reportPassed
2

Deep Scan the risky areas

Teams of agents push on the areas that changed: wrong formats, duplicate submissions, reloads in the middle of a flow, and cases nobody scripted.

Billingbug
Onboarding
Exportsbug
Settings
3

Compare it with your manual pass

Run both on the same release and see which bugs each one found. Every Composal finding comes with a recording and steps.

Manual pass
Follows the checklist
Composal
Also tries what the list left out

A release you can sign off

Know what was checked, what failed and what could not be reached.

Consistent, tireless coverage

The last scenario gets the same attention as the first.

Hours back for your team

People review findings instead of following scripts.