Create Test Plan

Create Test Plan

Analyze what changed and generate a comprehensive test plan covering four escalating levels of testing depth.

Step 1: Determine Scope

Resolve scope using the first match:

1. User-specified — the user says what to test. Use that.
2. PR — a PR URL or number is provided. Fetch the PR details (title, description, changed files, comments) and read the changed code.
3. Conversation context — prior conversation contains recent work (a feature, fix, or refactor). Extract what changed, where it lives, and expected behavior.
4. App-level discovery — fresh context with no prior work. Examine the project (entry points, routes, commands, README) to identify the app's core user-facing flows.

If the resolved scope spans more than one git branch and the user named no single branch, cover each of them instead of only the branch currently checked out. Include scenarios that exercise them together where the branches can be combined in the working tree the plan's executor will have, and state the required branch state in each such scenario's steps.

Step 2: Determine Testing Approach

Always check for project-specific testing skills or MCP tools first. Use the fallbacks below when nothing project-specific is available:

• Web app → $agent-browser skill if available, otherwise Codex browser automation
• UI/native app → computer-use MCP
• CLI tool → direct terminal execution
• Library with no entry point → report that interactive testing is not applicable and stop

Step 3: Resolve the Output Path

Pick a slug for the test plan from the change under test:

• Lowercase
• Replace non-alphanumeric characters with hyphens
• Collapse consecutive hyphens
• Trim leading and trailing hyphens
• Truncate to 40 characters at a word boundary

If the work is anchored to an existing plan at .turbo/plans/<slug>.md, reuse that plan's slug verbatim.

The user may pass an explicit slug or output path; honor it.

Resolve a collision at .turbo/test-plans/<slug>.md by how the slug was chosen. A slug generated from the change under test takes -2, -3, and so on until the path is free; do not overwrite. For a slug reused from an anchoring artifact, use request_user_input to offer overwrite or a different slug, since a numeric suffix would break its pairing with that artifact. For a slug or path the user supplied, use request_user_input to offer overwrite, a numeric suffix, or a different slug.

State the chosen slug and the resulting test plan path before continuing.

Step 4: Analyze the Change

After identifying scope, read the actual code in depth to understand:

• What was added, modified, or removed
• Expected behavior (from PR descriptions, comments, commit messages, or specs)
• Assumptions the implementation makes
• Error paths and edge cases
• Other features or components that could be affected

Step 5: Generate the Test Plan

For each level, generate specific, actionable test scenarios tailored to the actual change. Each scenario needs exact steps and an expected outcome.

Confirm a scenario's starting state can be reached before writing it. When a precondition depends on a system the executor does not control (another team's service, an external platform), confirm a write path for it exists. Where the write path is uncertain or absent, write the scenario so it names what to attempt and what to record when the attempt fails.

Confirm any control, command, or other affordance a scenario names exists in the code before writing the scenario: search for the API that would implement it rather than inferring it from what the feature does. Where it cannot be confirmed, write the scenario against the outcome to verify and leave the executor to find the affordance.

When a scenario's pass condition is that nothing happens — no write, no call, no state change — pair it with a control that differs only in the dimension under test and whose expected outcome is that the effect does occur, since a lone negative scenario cannot distinguish the behavior under test from a harness that never reached it. When such a scenario injects a crafted payload, establish that the payload satisfies every validation layer between the injection point and the code under test, and state which layers the trace cannot settle: a payload rejected at a parse boundary produces the expected absence for the wrong reason. When the guard it targets rejects a repeat invocation, establish that the affordance the scenario drives can be invoked a second time, and name an entry point carrying no busy or pending state when the primary one has it: a repeat the entry surface refuses never reaches the guard.

Level 1: Basic Functionality

Does the feature work at all? Verify the happy path and the most obvious behavior.

• Core feature works as described
• Expected output/UI matches the spec or PR description
• No regressions in directly related functionality

Level 2: Complex Operations

Combine multiple actions in sequence. Verify state consistency across operations.

• Chain related operations (e.g., create, edit, rename, delete)
• Exercise different combinations of feature parameters
• Verify intermediate states are correct, not just the final result

Level 3: Adversarial Testing

Actively try to break the feature. Explore boundary conditions and unexpected inputs.

• Invalid, empty, or extreme inputs
• Rapid repeated actions
• An action re-applied to its own output, checked against what the feature intends on the second application
• Interrupting operations midway (cancel, disconnect, close)
• Resource limits (very large files, deep structures, long names)
• Permission and access edge cases

Level 4: Cross-Cutting Scenarios

Explore state interactions across system boundaries. These surface the hardest bugs.

• Concurrent modifications from different sources
• State transitions (online to offline to online, foreground to background)
• Interactions with other features that share state
• Race conditions between asynchronous operations

When a Level Does Not Apply

If the change is small enough that a level has no meaningful scenarios (e.g., a typo fix has no cross-cutting scenarios), note "N/A for this change" with a brief explanation.

Step 6: Present and Write

Output the plan as text. Then use request_user_input to ask for approval before writing.

Create .turbo/test-plans/ if it does not exist. Write the plan to .turbo/test-plans/<slug>.md using this format:

# Test Plan: <Feature/Change Name>

## Context

<Brief description of what changed and why>

## Approach

<Testing approach: agent-browser / Codex browser automation / computer-use / terminal>
<Dev server command if applicable>

## Level 1: Basic Functionality

- [ ] **<Test name>** — <Steps to perform> → Expected: <expected outcome>

## Level 2: Complex Operations

- [ ] **<Test name>** — <Steps to perform> → Expected: <expected outcome>

## Level 3: Adversarial Testing

- [ ] **<Test name>** — <Steps to perform> → Expected: <expected outcome>

## Level 4: Cross-Cutting Scenarios

- [ ] **<Test name>** — <Steps to perform> → Expected: <expected outcome>

Then call update_plan to mark this step completed and continue with the next step of the active workflow.

Rules

• Generate at least 2 scenarios per level, more for complex changes.
• Each scenario must have concrete steps and an expected outcome specific to the change.
• Tailor all scenarios to the actual change. Generic test advice is not useful.