Add the missing end-to-end test for one critical path
The flow the business depends on, covered end to end with a trace attached to the pull request.
The ticket
Write an end-to-end test for one critical user flow and attach the run as evidence.
Acceptance criteria
- The test drives the real flow from entry to completion
- It runs against a preview environment, not a mocked stack
- A trace and screenshots are attached to the pull request
- It fails when a step of the flow is deliberately broken
What lands as proof
A browser trace and screenshots from the actual run, plus a demonstrated failure when the flow is broken.
Why teams defer it
- End-to-end tests are slow to write and slower to trust, so the first one never gets started.
- Without one already in place there is no harness, which turns a test into a project.
Questions
- What does the agent actually change?
- The ticket is scoped to one outcome: write an end-to-end test for one critical user flow and attach the run as evidence. Work that serves that outcome is in scope, and anything outside it is left for a separate ticket, so the pull request stays reviewable.
- How do I know the work is done?
- The pull request carries the evidence, not only the diff. Here that means browser trace and screenshots attached to the pull request, so a reviewer can confirm the result without reproducing the work locally.
- How much oversight does this need?
- The run stops once the plan is written. Somebody reads the approach and approves it before any code exists, which is the cheapest moment to redirect the work.