rakovi4/test-spec

Generate Test Specifications

Generate BDD-style test specifications for a story in 6 categories. Each category produces two files: main (critical tests) and extended (nice-to-have tests).

Usage

/test-spec "Story name"
/test-spec 5              # By MVP story number
/test-spec                # Interactive selection

Workflow

Phase 1: Context & Story Selection

Read before generating: ProductSpecification/BriefProductDescription.txt, ProductSpecification/stories.md, ProductSpecification/ExpectedLoad.txt, story folder (stories/*/): mockups, *.md, endpoints.md, interview.md.

Parse input: by name ("Login/Logout"), by number (5), or interactive (list and ask).

If interview.md exists, extract:

• Business rules and constraints → map to API test scenarios
• Explicit edge cases (column transitions, task ordering, concurrent edits) → map to extended tests
• External API error modes → map to integration tests
• Rate limits and performance constraints → map to load tests

Prerequisite analysis (mandatory): Read the story's Prerequisites section and Validation Rules table. For each prerequisite (Board exists, Column exists, etc.), generate guard scenarios in BOTH API and UI tests following the Prerequisite Guard Checklist in test-spec-format.md. Cross-reference existing stories (e.g., Story 5 tests/01_API_Tests.md sections 0-1, tests/02_UI_Tests.md section 0) for established blocker patterns.

Phase 2: Generate Test Files

Load .claude/templates/spec/test-spec-format.md for category formats, ordering principles, and BDD rules.

Create files in ProductSpecification/stories/NN-story-name/tests/:

Main files (critical ~27-34 total tests):

• 01_API_Tests.md, 02_UI_Tests.md, 03_Load_Tests.md
• 04_Infrastructure_Tests.md, 05_Security_Tests.md, 06_Integration_Tests.md

Extended files in extended/ subfolder (nice-to-have edge cases):

• extended/01_API_Tests_Extended.md through extended/06_Integration_Tests_Extended.md

Add this header to extended files:

> These are additional edge case tests. Implement after core tests pass.

Phase 3: Summary

Report: folder path, files created, test counts per file.

Rules

• English, Gherkin in Markdown, DSL only (no technical details in steps)
• Main files: critical path (~27-34 total), Extended files: edge cases
• Reference ExpectedLoad.txt for load tests
• Security: generate stack-aware scenarios only — see relevance filtering and checklist in test-spec-format.md. Skip technologies not in the stack (NoSQL, LDAP, XXE). Skip cross-cutting concerns tested globally (security headers, CORS, HTTPS). Include IDOR for resource-by-ID endpoints (tasks/{id}, boards/{id}), JWT security for auth stories, input validation for task fields. Merge related scenarios (e.g., one SQL injection test covering all fields). Target 6-10 focused scenarios per story.