# Composal vs WebdriverIO

WebdriverIO provides one programmable setup across several application surfaces and testing styles. Composal concentrates on hosted web QA: Scenarios, Discovery, Deep Scan and evidence for agent handoff.

## 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](https://composal.com/docs/verify)

## WebdriverIO

JavaScript multi-platform automation

WebdriverIO is an open-source Node.js automation framework for browsers, web components, native and hybrid mobile apps, desktop apps and extensions. Its runner supports WebDriver and WebDriver BiDi protocols.

## What each tool does

| Workflow | Composal | WebdriverIO |
| --- | --- | --- |
| [Run browser journeys](https://composal.com/product/scenarios) | ✓ Yes: Run saved browser Scenarios and return recordings and reproducible Findings. | ✓ Yes: Runs browser journeys as authored tests; teams define and maintain the test flow. |
| [Map application workflows](https://composal.com/product/discovery) | ✓ 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](https://composal.com/product/deep-scan) | ✓ 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](https://composal.com/product/scenarios) | ✓ Yes: Author Scenarios around the intended user outcome, then review the steps and expected results. | – With setup: Write executable tests, scripts, or structured keywords to define the steps and expected results. |
| [Run or inspect from a terminal](https://composal.com/product/cli) | ✓ Yes: Use the CLI to start and inspect verification runs and their Findings. | – With setup: Run configured tests through the product’s supported developer tools or CI integration. |

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

## Where each fits

Choose WebdriverIO when a JavaScript team needs to share test conventions across browser, mobile or desktop coverage. Choose Composal when the immediate need is to verify a running web app and return actionable findings.

## Try this evaluation

Test a web journey plus one mobile or desktop interaction if both are in scope. Compare the value of WebdriverIO’s shared runner against Composal’s exploratory findings and the time spent adapting the same test.

### 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?

## Related comparisons

- [Composal vs Robot Framework](https://composal.com/compare/composal-vs-robot-framework.md)
- [Composal vs Katalon Studio](https://composal.com/compare/composal-vs-katalon.md)
- [Composal vs Tricentis Tosca](https://composal.com/compare/composal-vs-tosca.md)

[All comparisons](https://composal.com/compare.md)