ComposalAPI and performance testing
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 →Gatling
Performance tests as code with scalable execution
Gatling supports performance testing with code-based simulations in Java, JavaScript, and other supported languages, plus browser recording and a no-code builder in its platform. Its documentation covers CI execution and scaling tests through Gatling Enterprise. Teams can model request flows and user injection profiles, then analyze performance results.
What each tool does
“With setup” means you supply code or configuration. “Not confirmed” means support for this workflow needs checking with the vendor.
| Workflow | Composal | Gatling |
|---|---|---|
| Run browser journeys | Yes Run saved browser Scenarios and return recordings and reproducible Findings. | Not confirmed Check whether this product includes this workflow in your intended plan and setup. |
| 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. | With setup Connect its specialist checks to your development workflow using supported integrations. |
| Performance measurement and load testing | No Use a dedicated tool for this specialist workflow alongside Composal’s browser verification. | Yes Gatling supports performance testing with code-based simulations in Java, JavaScript, and other supported languages, plus browser recording and a no-code builder in its platform. Its documentation covers CI execution and scaling tests through Gatling Enterprise. Teams can model request flows and user injection profiles, then analyze performance results. |
Where each fits
Choose Gatling when performance testing is a release requirement and your team wants test-as-code, browser recording, or managed distributed execution.
Try this evaluation
Select a journey with a known request sequence and a realistic peak-traffic profile.
- 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?