test-planner

To generate a test strategy from software specifications, you need audited spec/ documents. The tool processes these inputs to produce a SWEBOK Ch04-aligned test strategy, ensuring verifiable quality early in the development cycle.

A test matrix maps input-output pairs and boundary value sets to guide test design. You can create one by running the matrix generation mode on your spec/ documents to output structured TEST-MATRIX markdown files for comprehensive coverage.

Yes, you need a spec auditor before generating test plans. The tool requires specifications to exist in the spec/ directory and to have been audited by spec-auditor to ensure accurate traceability and performance scenario generation.

You plan performance scenarios by deriving tests directly from non-functional requirements in your specs. This approach targets specific p99 latency and throughput goals, outputting the results to a dedicated PERF-SCENARIOS.md file.

To ensure traceability between test cases and API contracts, you generate tests that explicitly link back to use cases, invariants, and API contracts. This provides full traceability across the generated test plan and matrix files.

The best way to structure test planning outputs for SWEBOK compliance is to use mode-based generation across planning and matrix modes. This creates distinct TEST-PLAN.md and TEST-MATRIX files aligned with SWEBOK Chapter 04 standards.