docs(migrate): add a TesterArmy migration guide
Merged
KR
17d ago+255+255+012345678901234567890123456789-10-10-01234567890123456789
TesterArmy saved tests live in TesterArmy's cloud, and there was no guide for moving them into e2e. Every other runner we support (Playwright, Cypress, Selenium, Detox, Maestro) has one.
- New page
docs/migrate/testerarmy.mdx, under Migrate after From Maestro. It has a copyable agent prompt: connect thetesterarmyMCP server, runnpx e2e init, port the project settings, then rewrite one group at a time withget_test. - Two tables cover the mapping. One maps project settings (environments, credentials, TOTP,
agentInstructions, memories, viewport, schedule) to e2e config. The other maps step types and groups (act,assert,login,files,screenshot,javascript,prepTestId,runMode) to e2e calls: an agent call, or a locator call when the step needs no judgment. Features e2e lacks are marked "Not yet" (accessibility audit, inbox credentials,temporaryEmail, microphone, mobile photo-library files) or "No equivalent" (browser region, web search). - The guide only reads from TesterArmy. The agent never creates, edits, deletes, or runs anything there. TesterArmy never returns passwords, so each credential reads its password from an environment variable.
migrate-to-e2eskill: TesterArmy is now in the detection table, and a new### TesterArmysection treats each saved test as a source file and each group as a slice. It allowsrun_testandrun_grouponly when the user agrees. For when to use a locator instead of the agent, it points to the guide.- The sidebar icon is TesterArmy's official black mark (
testerarmy-mark-black.svgfrom the brand kit), redrawn as one path on its pixel grid (8 KB) and cropped to the mark. coding-agents.mdx,AGENTS.md,CONTRIBUTING.md, and the plugin README now list TesterArmy among the runners.
Verified
Ran it locally: yes
- Docs site (
tester-army/e2e-sitewithE2E_DOCS_DIRset to this branch): the page renders, the prompt copies, both tables and tabs render, and the icon matches its Migrate neighbors in light and dark mode. - Every e2e anchor and API on the page was checked against
docs/andpackages/*/src. Every TesterArmy tool, field, and step type was checked against the TesterArmy app source. - I did not run a real migration against a TesterArmy project.
| Light | Dark |
|---|---|
Made with Claude Opus 5.5 in Claude Code.