TesterArmy rebranded to e2e on October 1, 2026 and announced an $8 million seed round on November 3, 2026 (e2e.com/blog/seed, fetched this run). The product changed along with the name: e2e is a free, open-source testing framework under Apache-2.0 - tests are files in a team's own repo from the start, run with their own CI and model, not rows in a hosted dashboard. What didn't carry over is the monitoring piece: e2e has no scheduler, no alerting and no status page, so it only runs where a pipeline tells it to. The original TesterArmy dashboard - the hosted product with natural-language steps and an hourly scheduler against Production - keeps running for existing accounts only until January 15, 2027. What follows covers both: what the legacy dashboard still costs before that shutoff, and where the real gap against ObserveOne sits now that the current product doesn't monitor anything at all.
e2e itself has no pricing page, because it has no price - free, open source, self-hosted, no tiers (e2e.com, fetched November 9, 2026). tester.army/pricing, the page the rows below were pulled from, now redirects logged-out visitors straight to e2e.com. The rows are what the legacy dashboard still charges existing accounts, pulled September 24, 2026, not re-checked live this run since that page no longer resolves publicly:
| Plan | Price | Detail |
|---|---|---|
| e2e (current product) | $0 | Open source under Apache-2.0, self-hosted. Bring your own CI, model and API key - there is no paid tier to upgrade to. |
| Free (legacy, sunsets Jan 15 2027) | $0 | 5 free test runs, 1 concurrent run, 2 projects, unlimited members, web and mobile support, no credit card required. |
| Hobby (legacy, sunsets Jan 15 2027) | $99/mo | Up to 250 test runs included, 3 concurrent runs, 2 projects, unlimited members, GitHub/Slack/webhook integrations. |
| Startup (legacy, sunsets Jan 15 2027) | $299/mo | Everything in Hobby plus up to 1,000 runs, 10 concurrent runs, unlimited members and 5 projects. Was marked "Most popular" on the legacy pricing page. |
| Enterprise (legacy, sunsets Jan 15 2027) | Custom | Everything in Startup plus an SLA via Slack Connect, white-glove onboarding, a strategic feature partnership, and SSO/SAML with custom integrations. |
There's no bill to manage on e2e itself. The planning question is whether a team still on the legacy dashboard migrates before January 15, 2027, or starts fresh on e2e and skips those tiers entirely - most teams evaluating TesterArmy today only have the second option.
Source: e2e.com and e2e.com/blog/seed (fetched November 9, 2026). Legacy tier pricing from tester.army/pricing, fetched September 24, 2026 - that page now redirects to e2e.com and can't be re-checked.
Nothing needs migrating if a test is written for e2e already - it's a file in a team's own repo from day one. Migration only comes up for a test still sitting on the legacy TesterArmy dashboard, which has to move before the January 15, 2027 shutoff:
On the legacy dashboard, tests are still plain-English steps saved server-side. Re-checked live this run: docs.tester.army/cli/agentic-usage (fetched November 9, 2026) still describes the CLI as "a control plane for the TesterArmy dashboard" that creates "dashboard tests", with no local spec file written, unlike a Playwright `.spec.ts`. e2e's own tests don't have this problem - describe the same flow to ObserveOne Autopilot, which compiles a plain-language description into a real Playwright file a team can read, diff and check into git, the same place e2e tests already live.
The legacy dashboard's own Configure Trigger ran a test group against Production hourly, daily, weekly, or from a webhook, with hourly as the finest setting (confirmed live September 24, 2026; behind a login we don't have, so not re-checked this run). e2e, the current product, has no equivalent of this at all - it runs only where a pipeline runs it, with no hosted scheduler. Either way, the closest match is an ObserveOne browser monitor's own schedule and alert channels; a five- or ten-minute check against Production was never available on the legacy scheduler and isn't available on e2e either.
The legacy dashboard advertised self-healing locators without publishing the mechanism. e2e's current docs describe something more specific: "agentic driven actions, precise locators, deterministic assertions" in the same test, mixing agent-driven steps that don't break when a selector changes with exact locators and assertions where certainty matters. ObserveOne's own chain works in a similar spirit - semantic locator, then XPath, then an AI re-learn pass - so this piece of a migration is closer to a wash than a downgrade either way.
The legacy dashboard exports what a test finds, not the test itself: its Jira integration turns an issue into a ticket carrying the description, expected versus actual behavior, reproduction steps and a screenshot link, re-checked live this run against docs.tester.army/integrations/jira (fetched November 9, 2026, unchanged from the earlier pull). That covers handing a bug to an engineer, not moving a test definition anywhere.
Ranked by how closely each one replaces TesterArmy. Every row links to a full side-by-side breakdown.
| Tool | Best for | Pricing | Comparison |
|---|---|---|---|
1 ObserveOneAI-powered synthetic monitoring and self-healing test automation | AI-First QA Teams | Free tier available, paid plans from $6/mo | vs TesterArmy |
2 MablIntelligent test automation platform for QA teams | QA Engineers | Custom quote-based pricing, no published tiers (free trial available) | vs TesterArmy |
3 PlaywrightOpen-source browser automation and end-to-end testing | Developers | Free and open source | vs TesterArmy |
4 CypressJavaScript end-to-end testing framework | Frontend Developers | Open source free. Cloud Team from $67/mo (10k test results) | vs TesterArmy |
5 SeleniumThe battle-tested open-source browser automation framework | QA Engineers | Free and open source | vs TesterArmy |
6 TestimAI-based stable end-to-end test automation | QA Engineers | Free Community tier after trial; Web/Mobile/Salesforce plans fully quote-based, no published price | vs TesterArmy |
7 BrowserStackCross-browser and device cloud testing platform | QA Teams | Paid from $99/mo (billed annually) | vs TesterArmy |
8 Ghost InspectorAutomated browser testing and website monitoring | QA Teams | Paid from $109/mo billed annually (free trial) | vs TesterArmy |
9 KatalonLow-code test automation for web, API, mobile and desktop | QA Teams | Free tier; Professional from $84/seat/mo (annual promo; list $184/seat/mo, $150 from the 4th seat) | vs TesterArmy |
10 New RelicObservability platform for every engineer | Developers | 100 GB/mo free data ingest, $0.40/GB beyond. Standard from $10/mo/user, Pro from $349/user/mo | vs TesterArmy |
e2e being free doesn't make it the right pick for every team. It covers real mobile builds - the same CLI that ran on the legacy dashboard can upload iOS Simulator apps and Android artifacts for mobile test runs, device-level coverage ObserveOne's own monitor types (browser, API, URL/uptime, SSL) don't attempt. Being open source and self-hosted also means no vendor can ever sunset the tests themselves out from under a team the way the legacy dashboard is about to; a team that picks e2e today owns the files regardless of what happens to the company behind it. And it runs the same suite against a GitHub pull request or a deploy preview before anything ships, catching a regression pre-release the way a pure production monitor was never built to.
No. It rebranded to e2e on October 1, 2026 and raised an $8 million seed round on November 3, 2026 (e2e.com/blog/seed, fetched November 9, 2026). The legacy TesterArmy dashboard stays live for existing accounts only until January 15, 2027.
No. e2e runs where a pipeline tells it to, with no hosted scheduler, alerting or status page. The legacy dashboard it replaced could schedule a test against Production hourly at best, but that product sunsets January 15, 2027 along with that capability.
Not the test itself. The Jira integration exports a found issue as a ticket with repro steps and a screenshot, but the test definition stays as a natural-language entry on the dashboard, with no downloadable file (confirmed live against docs.tester.army/cli/agentic-usage, November 9, 2026). A test written for e2e doesn't have this problem - it's a file in the repo already.
Nothing. It's open source under Apache-2.0 and self-hosted, with no paid tier (e2e.com, fetched November 9, 2026). The legacy dashboard it replaced charged Free/$99/$299/mo plus a custom Enterprise tier, but that pricing page now redirects to e2e.com and the product sunsets January 15, 2027.
Yes. Its CLI can upload iOS Simulator apps and Android artifacts for mobile test runs, and e2e.com advertises web, iOS and Android from one framework - device-level coverage ObserveOne's own monitor types (browser, API, URL/uptime, SSL) don't attempt.
If the need is a test defined as a file a team can review in a pull request, e2e already does that today, no migration story required. If the need is someone else watching Production on a schedule with alerting and a status page behind it, that's gone from this product entirely - describe the flow to Autopilot and compare a week of pass/fail history instead.
Start Free