[ open source · built for agents ]
the enterpriseverification layer foreverything agents build
[ what changes for your team ]
your agents write code faster than your team can verify it
coding agents write more code than any team can check by hand. e2e builds verification into every pull request, so quality scales with the output.
releases stop waiting
on testingthe suite runs on every pull request, so there’s no testing phase left to wait for.
coverage keeps up with
your code.covering a new flow takes minutes, so every feature goes live with its own tests.
tests heal themselves when
the ui changes.design changes stop turning into maintenance work, so engineers spend their time on features.
[ lower model costs ]
tokens are spent once,not on every run.
The model works out each step the first time. e2e remembers it, so every next run replays from cache at a fraction of the cost. The agent only comes back when your UI changes.
cumulative tokens cost
- without e2e
- 500x
- model cost
- with e2e
- 100.8x
- model cost
- total savings
- ~79.8%
- lower model cost
[ security and data ]
everything runsinside yourinfrastructure.
e2e runs on your machines and in your CI, with the coding agent and model provider you already approved. We never receive or process your data.
book a callyour repo
Tests live next to your code and go through review.
your apps and devices
Web, mobile, desktop or any other platform, including internal builds.
your model
Any provider, with your own keys and contracts.
your ci
Runs on every pull request, in the pipeline you have.
[ rollout process ]
our engineers roll it outwith you, then step back.
the people who build e2e work with your team through the rollout. once it runs on its own, they step back, and they come back for the next project.
[phase 1]
scope.
pick the flows that matter and agree what success looks like, in numbers.
[phase 2]
build.
we set e2e up on your builds and your model, and work through what’s specific to your stack together.
[phase 3]
migrate.
your most important flows and test cases move to e2e, next to the suite you run today.
[phase 4]
roll out.
e2e moves into your ci and onto your devices, and out to the teams that need it.
[phase 5]
hand over.
e2e runs on its own from here. we stay a message away for whatever comes next.
The future is verification-engineering. Proofs, (e2e) tests, benchmarks, linters… Some tests will be deterministic, some agentic. This looks great.
Guillermo Rauch
@rauchg
e2e looks great!
David Cramer
@zeeg
this is fire 🔥 congrats man
vansh patel
@vanshdevx
the mix of deterministic and agentic APIs sounds like a powerful approach
Brjan | AI Builder
@MrBrjan
oh shit I was building this but this is better than the thing I was building
Christian Genco
@cgenco
verification loops are the future. This massively enables that.
Tanay Kumar
@TanayKmr
وجود حل يدمج بين العهد القديم والجديد في أختبار البرمجيات بشكل سلس كان تحدي خلال الشهور الماضية ولكن الوضع اختلف مع e2e شي رهيب ان يقوم بعمل كاش للخطوات لتقليل التكلفه عند اعاده الاختبار مالم تتغير خطوات الاختبار حل واعد جداً 💪
translated from arabicSeamlessly combining the old and new approaches to software testing has been a challenge in recent months. That changed with e2e: it's great that it caches steps to cut the cost of re-running tests as long as the steps don't change. A very promising solution.
Salah Alkhwlani
@SalahAlkhwlani
congrats @TesterArmy team! you have really done some exceptional work with e2e, and i'm glad we got to be part of the launch 👏
Danny Prevoznik
@DanielPrevoznik
Love it!!! Testing it right now!
Danny Suárez 🍄🟫 d/acc
@dannysuarez
Suena interesante, tengo que echarle un ojo. Yo de momento resuelvo con Playwright generado por AI, a lo mejor es hora de cambiar...
translated from spanishSounds interesting, I need to take a look. For now I get by with AI-generated Playwright, maybe it's time to switch...
Carlos Castellanos
@karloscodes
just started using it and i'm already in love w this. Demo coming soon🙂↕️
Rami Maalouf
@rami__maalouf
This looks like magic 🪄 can’t wait to give it a go
Antonie Huang
@antoniehuang
wait the mix of deterministic + agentic apis is the bit tho. pure agent e2e always felt flaky in ci
anytan
@anytanreal
The agentic mobile testing game just changed.
Expo
@expo
congrats on the launch! looks amazing
Enzo Manuel Mangano
@reactiive_
Test your apps with X Premium or SuperGrok @o_kwasniewski really cooked with this, you write tests in natural language, the agent uses tokens only once, it remembers what it did for all future runs
Miłosz Jankiewicz
@Jaaneek
Esto tiene una pintaza espectacular! He hecho 2-3 pruebas rapidas y wow... 👇🏼
translated from spanishThis looks spectacular! I did 2-3 quick tests and wow...
Carlos Beneyto
@CarlosBeneyto
it's fantastic. Just use it. trust me
Caleb Panza ☾
@CalebPanza
this looks interesting for reducing token usage when testing web and mobile apps. it mixes deterministic and non deterministic testing, along with caching actions so you don’t have to call the model multiple times
Elliott Callender
@the__elliott
npx e2e just saved me 0.60$ on this coffee order, thanks @TesterArmy 🙏 Works out of the box with @expo EAS Simulator 😎
szymon
@szdziedzic
you have no idea how long I've been begging for this
Kevin Rajan
@_kvnloo
use e2e alongside @poteto's verification skill and you have a reliable workflow for mobile development.
Saeed
@stringsaeed
This is very interesting. Most e2e tests either break on every UI tweak or hand the whole run to an agent that burns tokens redoing the same clicks. e2e (TesterArmy) mixes both: stable locators where you know them, agent steps where you don’t - and caches the agent passes so the next run replays without calling the model again. Web, iOS, Android. BYO model. Basically: Let AI figure it out once, and then replay without cost.
Hrobjartz
@hrobjartz
I like the action replay. An unchanged login screen shouldn’t need a fresh opinion every time CI runs.
Ryan Gilpatric
@RyanGilpatric
playing around with e2e two days in the row. it's amazing, the hybrid approach super useful! kudos to @TesterArmy team
dimasike
@dimasike_
We’ve all been building our version of this, but this is better. Well done!
Jean-Michel Lemieux
@jmwind
the future of end-to-end testing is partially agentic, partially deterministic. glad that libraries like e2e build in this area, supporting both mobile and web development from day one. it was also a pleasure to collaborate with Oskar on making @agent_device, which is a driver behind mobile support, more reliable in deterministic flows. let's go! write some tests!
Michał Pierzchała
@thymikee
yeah this is it. once agents write the code, the scarce skill is deciding what to prove vs what to agent-test. mixing both in one harness feels right
Vamshi
@idohodl
Can't wait to review this migration 🔥
Piotr Trocki
@trozee_dev
Needed this. Pure agentic e2e flakes hard in CI. Mixing deterministic assertions with agent steps, plus BYO model and infra, is the only setup that stays useful once agents actually drive real UIs.
Edwin | AI Systems
@EdwinAI_Systems
A probarlo! Me encanta este concepto mix de instrucciones deterministas y agenticas. Lo mejor de todo es que tiene cache de los steps hechos por agentes.
translated from spanishTime to try it! I love this mix of deterministic and agentic instructions. Best of all, it caches the steps the agents take.
Javo 🧉
@javicerodriguez
Ya lo estoy probando pero toca tener cuidado con el consumo de tokens ando construyendo algo hibrido usando e2e y playwright
translated from spanishAlready trying it, but you have to watch token usage. I'm building something hybrid with e2e and Playwright.
Danny Suárez 🍄🟫 d/acc
@dannysuarez
Love this. I’ve been doing the same thing in a vacuum.
dgaspard
@dgaspard
This is very cool! I was thinking about building something similar for @DispatchinoAI
Amr
@Amr0Khalid
@TesterArmy E2E is amazing 🙌. It found a form submission case I haven't covered. Basically a http 500 left the user with no error message during failure. Was easy to miss on my happy path tests.
Nandy
@parzival1l
[ faq ]
what engineeringleaders ask us.
Straight answers to what developers and CTOs ask before they switch.
[001]is the framework free for enterprise use?
Yes. e2e is Apache-2.0 and stays free. You pay only when our engineers help you roll it out or build something custom.
[002]what happens to our data?
It stays with you. e2e runs on your machines and in your CI, and nothing is sent to our servers. Your model provider processes the requests needed to run agent steps, under the keys and contracts you already have.
[003]how do we move from the tool we use today?
Start with the flows that break most. We describe them in plain language and run them next to your current suite, then move the rest over as they prove themselves.
[004]does it work with our agents and platforms?
Yes. e2e works with the coding agent and model you already use, and its engine is swappable, so the same tests run on web, mobile, desktop or anything else.
[005]what does an enterprise agreement include?
The engineers who build e2e: migration of your suite, setup in your CI, anything your stack is missing, and a direct line to the team once it runs on its own. The framework itself stays free.
