Use case

Regression testing that keeps up with every release

Your team covers the whole product, not just the feature in the ticket. Composal runs the flows that matter on every change and reports what broke, with the steps and evidence to reproduce it.

Read the docs
Regression run · whole product
Sign up and verify emailPassed
Invite a teammate to a projectPassed
Change a plan, then check the invoice newFailed
Export a reportBlocked
Reset a passwordPassed
Upload and reprocess a fileRunning

Where the time goes today

Regression coverage falls behind

Tests are written for the new capability and miss how it interacts with what already works.

Manual passes do not scale

Breakathons and acceptance runs follow checklists. People tire, and the same scenarios get skipped or rushed each release.

Expected behaviour lives in people’s heads

What should happen is spread across tickets and testers, with no shared record for the next person to use.

1

Discover the product

Point Discovery at your app. Agents map its screens, features and flows, so you do not write every test by hand.

2

Keep expected behaviour in one place

Scenarios are plain-English files in your repository, reviewed like code and run on every change.

scenarios/checkout.yamlinvite-teammate.yamlreset-password.yaml
# invite-teammate.yaml
name: Invite a teammate
persona: Admin
steps:
- Open Members, then Invite
- Send to a new address
outcomes:
- Invite appears as pending
3

Hunt beyond the scripts

Deep Scan sends a team of agents into one area to try what the scripts never covered, including messy inputs and interrupted flows.

Plan change
Invoice viewbug
Coupon entry
Seat limitsbug
Refund
Tax settings
4

Hand each failure over with proof

Every bug arrives with expected and actual behaviour, reproduction steps and a recording, ready for the developer.

Finding · Invoice view
P2Invoice total ignores the new seat count
ExpectedTotal reflects the 12 seats on the plan.ActualTotal still shows the old 10 seats.
1. Open Billing and choose the Team plan.2. Add two seats and save.3. Open the invoice preview.
Recording

Full-platform regression

The flows that touch existing features run on every change, not only the new one.

Less repetitive manual testing

People spend their time on judgement calls. Agents repeat the same checks the same way every time.

Evidence, not opinions

Each failure ships with its recording and steps, so triage starts from facts.

See every use case