# 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.

Category: Test coverage and flaky tests
Source: https://letsship.ai/use-cases/add-the-missing-end-to-end-test
Published: 2026-08-25

## Goal

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.

## Prompt

Copy this to an agent to open the ticket:

```text
Create a Linear issue in my team and assign it to the SHIP agent.

Title: Add an end-to-end test for {flow}

Description: 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

Before you create the issue, identify the flow in this repository whose failure would matter most and replace {flow} with it.
```

## 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.