Stretch Testing Skill

When to Use

• Running adversarial QA against the codebase
• Detecting BRD spec vs implementation mismatches
• Writing edge case tests for untested code paths
• Verifying state machine can't be bypassed
• Checking template outputs match BRD §9 schemas exactly

Methodology

1. Read Authority First

Before writing any test, read the relevant BRD section to understand expected behavior:

• State machine: BRD §6
• CLI commands: BRD §7
• Intake modes: BRD §8
• Output schemas: BRD §9
• Pack matrix: BRD §10
• Patch rules: BRD §12
• Promote criteria: BRD §13

2. Adversarial Test Categories

3. Test Output Format

it('B-XXX: <description of what should happen per BRD>', () => {
  // Arrange: set up the scenario
  // Act: trigger the behavior
  // Assert: verify BRD-expected result
});

4. Reporting Format

For each bug found:

• Bug ID: B-001, B-002, etc.
• Severity: CRITICAL / HIGH / MEDIUM / LOW
• Component: which src/ module
• Actual: what happens
• Expected: what BRD says should happen (cite section)
• Proof: test file path + test name

Test Files

• Adversarial tests go in tests/adversarial/
• Name pattern: stretch-<category>.test.ts
• Import helpers from tests/templates/helpers.ts

Do NOT

• Fix bugs — only find and document them
• Write tests without BRD reference for expected behavior
• Skip cleanup in afterEach (temp dirs, external files)
• Assume anything works until proven with a test