Use case

Your first QA doesn’t have to be a hire

You need someone to check the product before customers do. You do not have to hire your first QA engineer to start. Composal’s browser agents learn your app, run the journeys that matter and bring your team findings with recordings and steps to reproduce them.

Read the docs
Example first QA checklist
Learn the product with DiscoveryPlanned
Save signup, checkout and permission ScenariosPlanned
Deep Scan the next release candidatePlanned
Review Findings and send fixes to engineeringPlanned

Where the time goes today

The founders are the testing team

The same people building features are squeezing in a manual check before release. Testing gets smaller as the shipping queue grows.

A hire takes time to become coverage

Recruiting and onboarding do not check today’s release. Your critical journeys need attention while you decide how to grow the team.

The checklist lives in someone’s head

The important roles, old bugs and awkward edge cases disappear when the person who remembers them is busy.

1

Give the agents a product to learn

Connect an environment and suitable test accounts. Discovery maps the product’s features and user flows so you have a starting point to review with your team.

Start with Discovery
What this team remembers
The empty state is not a bugKnown
Invoice rounds to the nearest centKnown
Seat count lags a refreshOpen bug
2

Write down what a release must prove

Save Scenarios for signup, your main customer task and the permissions around it. State the expected outcomes in plain English and run them against your next change.

Build your first Scenario coverage
Every saved Scenario, in parallel
Sign up and verify emailPassed
Invite a teammatePassed
Change a planFailed
Export a reportPassed
3

Explore, review and fix

Use Deep Scan to explore beyond the saved journeys. Your team reviews the Findings, decides what matters and sends the evidence to an engineer or coding agent. Keep that coverage as the team grows.

Explore the release with Deep Scan
Billingbug
Onboarding
Exportsbug
Settings

Start before you staff up

Get browser verification into your release workflow before making a dedicated QA hire.

Your team keeps the decisions

People choose the requirements, review the evidence and decide whether to ship.

Coverage you keep

Scenarios and product knowledge stay in the project as your team and testing needs grow.

See every use case