e2e vs Testsigma Atto
e2e (e2e (formerly TesterArmy)) and Testsigma Atto (Testsigma) side by side on public data, as of Nov 21, 2026.
e2e shipped 8 stable releases in the past 90 days.
Which should you choose?
Choose e2e if
- you want to start free: it has a free plan, Testsigma Atto does not
- you want code you can read, fork or self-host (Apache-2.0)
- you need to run local models
- you want to switch between model providers (3 documented against 0)
- you work in the terminal
- you want to run it unattended in scripts or CI
Built from documented features, official prices, status pages and usage data on this page; it does not judge output quality.
Side-by-side numbers
| Metric | e2e | Testsigma Atto |
|---|---|---|
| Gid Score | 51 | — |
| Usage data as of | Nov 21 | Nov 20 |
| Rank by Gid Score | #39 | — |
| Downloads, last 7 days | 1.6M | — |
| Downloads, 7-day change | up 88.4% | — |
| Downloads, 30-day change | — | — |
| VS Code installs | — | — |
| Marketplace rating | — | — |
| GitHub stars | 14.1K | — |
| Homebrew installs, 30 days | — | — |
| Hacker News mentions, 30 days | 1 | 0 |
| Latest stable release | 0.24.0 · 2d ago | — |
| Stable releases, 90 days | 8 | — |
| Terminal-Bench (best run) | — | — |
| Price | Free (OSS) | Custom |
| Incidents, last 30 days | — | 2 |
| License | Apache-2.0 | Proprietary |
| First released | July 2026 | — |
| Interfaces | CLI, SDK, MCP server | Web app |
| Models | — | — |
A dash means there is no public data for that metric as of Nov 21, 2026.
e2e
A TypeScript SDK, runner and CLI for end-to-end tests of web and mobile apps in which agent steps carry out natural-language tasks in real browsers, simulators or emulators; an agent step is recorded once a later check passes and replayed on the next run without model calls, handing back to the agent when the app changed.
Pricing: Free and open source (Apache-2.0) with your own model; the company also sells a separate hosted testing service.
Latest release 0.24.0:
- #1891 847a09e Thanks @KrzysztofMoch! - Breaking: test.extend() fixtures are set up on demand, as in Playwright and Vitest.
- A fixture that exists for its side effect (it seeds data, installs a build, starts a watcher) and that no test names needs auto: true: [fn, { auto: true }] runs for every test, [fn, { scope…
- A fixture that relies on another one running first names it: task: async ({ project, agent }, use) => {}.
- A test body, a hook, and a fixture function destructure their first parameter. async (fixtures) => {}, async (_, use) => {}, a rest property ({ app, ...rest }), and a bound function (fn.bind())…
Testsigma Atto
AI coworker in the Testsigma platform that uses specialised agents to plan, write, run, heal and analyse tests for web, mobile, API and Salesforce apps, with Windows desktop and SAP also covered. Agents map commits to stories, update locators when the UI changes, report coverage gaps and write release reports; a human approves before anything ships. It connects to CI/CD tools, Jira, Slack and coding assistants such as Claude Code. The docs label Atto as beta.
Pricing: Pro and Enterprise plans, both by custom quote.
e2e vs Testsigma Atto: common questions
How do e2e and Testsigma Atto prices compare?
e2e: Free (OSS). Testsigma Atto: Custom. Prices come from each vendor's pricing page.
Is e2e or Testsigma Atto open source?
e2e is open source (Apache-2.0); Testsigma Atto is proprietary.
Do e2e and Testsigma Atto support local models?
e2e documents support for local models; Testsigma Atto's documentation does not.