Structured Test Planning FAQs

Question 1

Does this skill support parallel test execution?

Accepted Answer

Yes, it includes specific guidelines for identifying parallelizable test cases based on shared state and side effects, helping to optimize your CI/CD pipeline.

Question 2

Can I link test plans to implementation documents?

Accepted Answer

Absolutely. Every generated test plan includes a mandatory header section for implementation references, ensuring a clear link between requirements and verification.

Question 3

What is the recommended size for a single test plan?

Accepted Answer

To prevent errors and maintain focus, test plans are limited to a maximum of 400 lines, 15 test cases, and 5 modules per file.

Question 4

How does this skill handle large codebases without hitting memory limits?

Accepted Answer

The skill employs a 'Divide & Conquer' strategy, breaking analysis into phases: discovery, module analysis, and specific test design, ensuring only relevant file content is loaded at once.

Question 5

Where are the test plans and progress logs stored?

Accepted Answer

All output is standardized within a `test-plans/` directory, containing individual markdown files for different test types and a centralized `PROGRESS.json` for status tracking.

Structured Test Planning

Key Features

Use Cases

Structured Test Planning

Key Features

Use Cases