How do Recus and e2e compare for web QA?
Recus is a hosted workflow for exploratory browser testing and reviewable findings. e2e from the TesterArmy team is an open-source TypeScript framework combining deterministic checks, agent goals and exploration, with local and CI execution for web and mobile. Evaluate Recus for a hosted exploratory pass; evaluate e2e when owning tests and runtime configuration in your repository matters.
By Recus · Reviewed · Vendor-sourced, not an independent benchmark
Where each option fits
Recus
Consider Recus for browser exploration around new or changing workflows, especially when the team wants to inspect findings before deciding which regression tests to maintain.
e2e
An open-source TypeScript testing framework from the TesterArmy team, combining agent goals, deterministic checks and exploration. Evaluate it when you want tests and model/runtime configuration in your repository.
Source: e2e product overview ↗Hosted exploratory findings or tests and execution owned in your repository?
TesterArmy and e2e are separate products. TesterArmy’s site says new registration is closed and service continues for existing accounts until January 15, 2027. Its team directs users to e2e; moving tests requires explicit migration. Evaluate Recus separately against the browser tasks you need to preserve.
| Decision | Recus | e2e |
|---|---|---|
| Test ownership | Start a browser scan and review its findings in the Recus workflow. | TypeScript tests, configuration and model choice live with your application. |
| Execution modes | Inferred checks and selected UI/route discoveries, bounded by access and runtime limits. | Mixes deterministic assertions with agent goals; also offers an explore command. |
| Repeating a journey | A fresh exploration does not promise the same actions or full regression coverage. | Verified agent actions can replay from cache; agent assertions still use a model. |
Try the same concrete workflow
Open an authenticated settings page, reveal a dialog and save a change. Compare exploratory discovery with a committed test that asserts the same setting after a reload.
- Specify session setup and the exact saved-state expectation before testing.
- Change a label and inspect whether the test replays, invokes an agent or cannot continue.
- Record which artifacts can be rerun in CI and which findings still need human confirmation.
Pricing and evidence
This guide does not claim a price or performance advantage. Vendor descriptions establish product scope; they do not prove comparative bug detection or reliability. Check Recus pricing and the vendor’s current terms, then record total trial cost, human review time, and confirmed defects.
Read the migration considerations →What Recus does—and where it stops
Recus studies a reachable web interface, plans browser checks, follows selected discoveries, and returns findings with available screenshots, recordings, and action history. Inferred expectations need human review. Login barriers, unsupported capabilities, and run budgets can leave paths untested. A completed run is not proof of exhaustive coverage.
Questions about this testing workflow
Is e2e the same product as TesterArmy?
No. The team describes e2e as a separate open-source framework. TesterArmy is winding down, with existing access scheduled to end January 15, 2027. Check the transition announcement before planning a migration.
Does e2e require every action to be scripted?
No. Its documentation includes agent goals and an explore command alongside deterministic locators and assertions. Compare the mode you intend to use rather than describing it as a purely scripted runner.
Does a cached action mean every e2e run avoids model calls?
No. Its documentation distinguishes replayable verified actions from live agent assertions and other agent operations. Measure your actual workload instead of assuming all checks become deterministic.
Sources and review method
Product descriptions were checked against the linked vendor sources on November 17, 2026. They establish documented scope, not comparative performance. Recus wrote this guide; the suggested trial is a proposed evaluation, not a measured result.
Use the reproducible evaluation method →Compare real results on your own app.
Keep access, test data, scope, and time budget consistent. Review confirmed bugs and missed paths before selecting a tool.
Try Recus →