TesterArmy e2e
TesterArmy e2e quickstart: a small web test first
Initialize a project, choose an engine and verify a deterministic assertion before adding AI
What you will learn
- Inspect generated setup
- Run without an agent step
- Add one adaptive action
Before you start
- A disposable app or test account
- A web or mobile engine
- A deliberate model-provider choice for agent steps
Use two runs and one controlled UI mutation before trusting cached actions
Key takeaways
- The starter command does not install dependencies by itself.
- A no-model test isolates engine setup.
- Agent actions need a safe target account.
Inspect generated setup
The README starts with `npx e2e init`; the pinned quickstart says the interactive initializer asks for web or mobile engine and a model provider. It previews file changes before writing.
A non-interactive `npx e2e init --yes` example writes starter files but does not install dependencies. Read the generated config, target URL and start command before running the suite.
Run without an agent step
The quickstart includes a first example that opens an app and asserts visible content without calling a model. This isolates engine, app startup and locator issues before model configuration enters the picture.
For web, the engine package uses Playwright browsers. For mobile, use the mobile engine with an available simulator or emulator. Do not treat the two target configurations as interchangeable.
Add one adaptive action
Only after the deterministic test passes should you add `agent.act` and a following assertion. Pick a disposable account or fixture because the agent may click and type in the app.
Choose a supported provider or local model deliberately. We did not authenticate a provider or run an initializer; the commands are documented steps, not an installation report.
Decision guide
| Criterion | Option A | Option B |
|---|---|---|
| Best when | You need predictable behavior and easy auditing | You need adaptive optimization and have reliable telemetry |
| Main risk | May leave performance on the table | Can become difficult to explain or debug |
Implementation steps
- 1
Run the initializer and inspect proposed files.
- 2
Make a no-model assertion pass.
- 3
Add one bounded agent step and verify its result.
Copy-ready example
npx e2e init
# Review the written config and example before running the suiteFrequently asked questions
Can I start without an API key?
Yes, the quickstart includes a no-model test; agent steps need a configured model route.
Will init configure a mobile simulator for me?
It can write mobile config, but a working simulator or emulator still needs to be available.
Sources
- TesterArmy e2e / README.mdSource checked 2026-10-14
- TesterArmy e2e / docs/quickstart.mdxSource checked 2026-10-14
- TesterArmy e2e / docs/reference/runner.mdxSource checked 2026-10-14
- TesterArmy e2e / docs/reference/engine.mdxSource checked 2026-10-14