Checksum vs e2e
Checksum (Checksum) and e2e (e2e (formerly TesterArmy)) side by side on public data, as of Nov 21, 2026.
e2e has 84.1x the weekly package downloads of Checksum (1.6M against 19K). e2e shipped 8 stable releases in the past 90 days.
Which should you choose?
Choose Checksum if
- you want the one gaining users faster (downloads up 30% in 30 days, +11% in the last 7)
Choose e2e if
- you want to start free: it has a free plan, Checksum does not
- you want code you can read, fork or self-host (Apache-2.0)
- you need to run local models
- you want to use your own model API key
- you want to switch between model providers (3 documented against 0)
- you want subagents or several agents working in parallel
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 | Checksum | e2e |
|---|---|---|
| Gid Score | 31 | 51 |
| Usage data as of | Nov 20 | Nov 21 |
| Rank by Gid Score | #157 | #39 |
| Downloads, last 7 days | 19K | 1.6M |
| Downloads, 7-day change | up 11.0% | up 88.4% |
| Downloads, 30-day change | up 30.5% | — |
| VS Code installs | — | — |
| Marketplace rating | — | — |
| GitHub stars | — | 14.1K |
| Homebrew installs, 30 days | — | — |
| Hacker News mentions, 30 days | 0 | 1 |
| Latest stable release | — | 0.24.0 · 2d ago |
| Stable releases, 90 days | — | 8 |
| Terminal-Bench (best run) | — | — |
| Price | Custom | Free (OSS) |
| License | Proprietary | Apache-2.0 |
| First released | — | July 2026 |
| Interfaces | Web app, CLI, API, MCP server, Messaging apps | CLI, SDK, MCP server |
| Models | — | — |
A dash means there is no public data for that metric as of Nov 21, 2026.
Trends
Checksum
Generates Playwright end-to-end and API tests, runs them in CI and repairs failing tests automatically as the code changes.
Pricing: Priced by the number of workflows and tests maintained, with no per-seat or per-run fees; no public prices.
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())…
Checksum vs e2e: common questions
How do Checksum and e2e prices compare?
Checksum: Custom. e2e: Free (OSS). Prices come from each vendor's pricing page.
Is Checksum or e2e open source?
e2e is open source (Apache-2.0); Checksum is proprietary.
Which is more popular, Checksum or e2e?
e2e has a Gid Score of 51 against 31 for Checksum. The score combines package downloads, editor installs, GitHub activity and attention, updated daily.
Do Checksum and e2e support local models?
e2e documents support for local models; Checksum's documentation does not.