[ why e2e ]
pick the model, the platform, and where it runs.
mix agent steps with deterministic checks.
[001]
open by default, read it, change it,
run it wherever.
[002]
write once, run everywhere.
web, iOS, Android.
[003]
agentic driven actions, precise locators,
deterministic assertions.
[004]
use any model, your api keys
or subscriptions.
[ how it works ]
e2e lives in your repo, runs in your terminal and ci, and works
with your coding agent. verification becomes part of building.
tests/checkout.e2e.ts >describecheckout>testpays for the cart with a test card
import { describe, test } from '@e2e-dev/web';import { expect } from 'e2e';describe('checkout', { session: 'member', tags: ['payments'] }, () => {test('pays for the cart with a test card', async ({ app, agent, screen }) => {await app.open('/shop');await agent.act('add two items to the cart, then go to checkout');await expect(screen.getByRole('heading', 'Checkout')).toBeVisible();await agent.act('pay with the card {card}', {params: { card: '4242 4242 4242 4242' },});await expect(screen.getByTestId('order-status')).toHaveText('Paid');await expect(screen.getByText('Thank you for your order')).toBeVisible();});});
$ npx e2e run tests/checkout.e2e.ts
RUN e2e v0.22.0 ~/my-app
✓ web tests/checkout.e2e.ts (1 test) 2.14s ✓ checkout > pays for the cart with a test card 2.14s ✓ agent.act "add two items to the cart, then go to checkout" 742ms ✓ agent.act "pay with the card {card}" 586ms Test Files 1 passed (1)
Tests 1 passed (1)
Cache 2 replayed
Duration 3.45s (startup 1.31s)
main · localtypescript · 1 test · 2 replayed · 0 model calls[ community ]
npx e2e initThe 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
[ for enterprise ]
choosing a testing framework is a decision for years, not weeks.
e2e is built in open source.
your-repo
appcomponentslibpublictests
auth.e2e.tscheckout.e2e.tswallet.e2e.tsaccount.e2e.tsonboarding.e2e.tssearch.e2e.tssettings.e2e.tse2e.config.ts
package.jsonmain · locale2e · open sourcee2e is open source and your tests are plain files in your repo.
the only thing that locks you in is that it just works.
cloudyour cloud• you
ciyour pipeline• you
modelyour provider• you
api keyyour env• you
datayour infra• youe2e runs on your machines and in your pipeline, with the
coding agent and model provider you already approved.
[ at scale ]
[ faq ]
yes. the framework is open source and stays free. you run it on your own machines and in your ci, with your own model.
no. verified steps are cached and replay without calling the model. if a step needs to adapt to a change in your app, the model figures it out again and updates the cache.
on your infrastructure: your machines, your ci, your cloud. you bring your own model and api key. your model provider processes the requests needed to run agent steps.
start small: describe a few critical flows in plain language and run them next to your current suite. move the rest over as you go.
[ resources ]
guides, live sessions and ready-made examples. read them yourself,
or paste a link into your coding agent and ask it to set things up.
[ get started ]
npx e2e init2,521,485
3M
14k
60