# Split a suite that mixes unit and integration tests into separate tiers

A suite where fast tests wait behind slow ones, split so each tier runs on its own command.

Category: Test suite consolidation
Source: https://letsship.ai/use-cases/split-a-mixed-test-suite
Published: 2026-08-25

## Goal

Separate a mixed suite into a fast unit tier and a slower integration tier.

## Acceptance criteria

- Each tier runs from its own command
- The unit tier needs no external services
- Both tiers run in the pipeline, with timings recorded separately
- No test is dropped in the split

## What lands as proof

Two timings where there was one, and a test count that adds up to what the suite had before.

## 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: Split {suite} into unit and integration tiers

Description: Separate a mixed suite into a fast unit tier and a slower integration tier.

Acceptance criteria:
- Each tier runs from its own command
- The unit tier needs no external services
- Both tiers run in the pipeline, with timings recorded separately
- No test is dropped in the split

Before you create the issue, find a suite in this repository that mixes fast and slow tests and replace {suite} with it.
```

## Questions

### What does the agent actually change?

The ticket is scoped to one outcome: separate a mixed suite into a fast unit tier and a slower integration tier. 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 each tier runs on its own command with its own timing, 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.
