Test frameworks and automation

Composal vs Robot Framework

Robot Framework lets teams compose keyword-based suites and libraries for many kinds of automation. Composal provides a hosted browser QA workflow with Scenarios and additional exploratory Discovery and Deep Scan.

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 →

Robot Framework

Keyword-driven automation framework

Robot Framework is an open-source automation framework with readable text syntax and extensible libraries. Its ecosystem includes Browser and Selenium libraries for web apps as well as API and RPA options.

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 Robot Framework workflow capabilities
Workflow	Composal	Robot Framework
Run browser journeys	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	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.	With setup Write executable tests, scripts, or structured keywords to define the steps and expected results.
Run or inspect from a terminal	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.

Where each fits

Choose Robot Framework when reusable keywords, a broad extension ecosystem or non-web automation matter. Choose Composal when you need to check web behavior from a product workspace and hand findings to an agent.

Try this evaluation

Model a multi-step onboarding outcome with Robot keywords and as a Composal Scenario. Ask each workflow to surface an unanticipated invalid-invitation defect; compare maintenance, report context and handoff effort.

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?