Verify one critical flow across the supported browsers
A flow only ever tested in one browser, run across the supported set with a trace kept from each.
The ticket
Run one critical flow across every supported browser and fix what differs.
Acceptance criteria
- The flow completes in each supported browser
- A trace from each run is attached
- Differences found are fixed or documented with a reason
- The browser list matches what the product actually claims to support
What lands as proof
One trace per browser, which turns a claim of cross-browser support into something a reader can check.
Why teams defer it
- Everybody develops in the same browser, so differences surface through support tickets rather than tests.
- Running the other browsers locally needs a harness nobody has set up yet.
Questions
- What does the agent actually change?
- The ticket is scoped to one outcome: run one critical flow across every supported browser and fix what differs. 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 a trace per browser 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.