e2e-testing
End-to-end testing
An end-to-end test drives the app the way a user does and proves the outcome on screen or in a side-effect store. This skill keeps the owner's AGENTS.md journey contract separate from framework APIs. Use the framework already in the project; installing another framework needs the user's authorization. [owner AGENTS.md, End-to-End and Acceptance Tests and Pause and confirm; tester-army/e2e, writing tests]
Apply only the routes and checks for the selected job. Read a linked skill's named file from its installed folder when available, or from the linked source. Report an unavailable required reference instead of inventing it. [skill-authoring, DISTRIBUTION.md#composing-skills]
| The job | Read |
|---|---|
| Define one coherent journey, its actions and observable checks | JOURNEY-DESIGN.md |
Choose the implementation skill
Only the chosen framework's implementation guide is needed. The following are direct references to separately installable skills, not requirements to install all of them. [owner AGENTS.md, Prefer established dependencies; tester-army/e2e, writing tests; leancodepl/patrol, test setup; mobile-dev-inc/maestro-docs, setup]