Visual testing

Composal vs Percy

Percy reports visual deltas; Composal reports whether user journeys and exploratory behavior meet expectations. A screenshot difference can reveal a layout regression but may not establish that a form or permission flow works.

See where each fits ↓

Two workflows, side by side

Composal

Composal sends AI browser agents to use your running web app and check the outcomes you care about. Define journeys as plain-English Scenarios, map existing flows with Discovery, or explore for bugs with Deep Scan. Runs keep recordings and reproduction steps so your team or coding agent can investigate a Finding.

Verify documentation →

Percy

Visual regression review in CI

Percy captures rendered pages or components and compares them with baselines so teams can review visual changes with each code update.

What each tool does

“With setup” means you supply code or configuration. “Not confirmed” means support for this workflow needs checking with the vendor.

Composal and Percy workflow capabilities
Workflow	Composal	Percy
Run browser journeys	Yes Run saved browser Scenarios and return recordings and reproducible Findings.	With setup Captures or compares rendered pages through a configured test or visual workflow; confirm the supported runner.
Map application workflows	Yes Discovery maps key application areas and user journeys.	Not confirmed Check whether this product includes this workflow in your intended plan and setup.
Explore for unexpected issues	Yes Deep Scan explores the running application and reports reproducible issues.	Not confirmed Check whether this product includes this workflow in your intended plan and setup.
Describe checks in plain English	Yes Author Scenarios around the intended user outcome, then review the steps and expected results.	Not confirmed Check whether this product includes this workflow in your intended plan and setup.
Run or inspect from a terminal	Yes Use the CLI to start and inspect verification runs and their Findings.	Not confirmed Check whether this product includes this workflow in your intended plan and setup.
Visual regression baselines	No Use a dedicated tool for this specialist workflow alongside Composal’s browser verification.	Yes Percy captures rendered pages or components and compares them with baselines so teams can review visual changes with each code update.

Where each fits

Choose Percy when pull requests need repeatable screenshot comparisons and reviewers want to approve or reject visual changes.

Try this evaluation

Use a UI change that intentionally adjusts spacing and a second change that breaks the save action without altering the page appearance.

Coverage: Which user outcomes must this release prove, and which specialist checks must stay in your existing stack?
Setup: Who prepares accounts, test data, permissions and access to the deployment being tested?
Evidence: Can the engineer reproduce a reported failure from the recording and steps, without asking the tester to investigate again?
Ownership: Who updates the checks when the product changes, and can the team review what a passing result actually proves?