test-hardening

Test Hardening Skill

Convert verified QA Contract criteria (G#N, AC#N) into permanent automated tests. Ensures passing scenarios become regression tests.

When to Use

• After qa-commit returns GREEN for a commit
• After debug skill fixes an issue (Phase 7: Harden)
• Before pushing PR (ensure all criteria have tests)
• Manually with "use test-hardening skill"

Input: Verification Report

From qa-commit's Verification Report:

• List of passed G#N (Gherkin scenarios)
• List of passed AC#N (acceptance criteria)

Phase 1: Analyze Criteria

1.1 Categorize by Test Type

1.2 Check Existing Tests

Grep: "G#[N]" or "[scenario name]" in test files

Skip if test already exists.

Phase 2: Generate Backend Tests (G#N)

For each passed G#N without existing test:

2.1 Template

// apps/api/src/[feature]/__tests__/[feature].test.ts

describe('[Feature Name]', () => {
  // G#1: [Scenario name]
  it('should [expected behavior]', async () => {
    // Arrange
    const input = { /* test data */ };
    
    // Act
    const response = await request(app)
      .[method]('[endpoint]')
      .send(input);
    
    // Assert
    expect(response.status).toBe([status]);
    expect(response.body).toMatchObject({ /* expected */ });
  });

  // G#2: [Scenario name]
  it('should return [error] when [condition]', async () => {
    // Test implementation
  });
});

2.2 Generate Test

1. Extract endpoint, method, expected response from G#N
2. Create test file if not exists
3. Add test case with G#N reference in comment
4. Run test to verify it passes

npm run test -- --grep "[scenario name]"

Phase 3: Generate Storybook Stories (AC#N - States)

For state-based AC#N:

3.1 Template