Test Suite Management

Test Suite Management

Skill Purpose: Organize, tag, and maintain test suites to optimize coverage, speed, and reliability.

---

Core Skill Pattern

Objective: Structure tests to balance fast feedback with comprehensive coverage.

Universal Pattern:

1. Define suite taxonomy (smoke, regression, full)
2. Tag tests and group by purpose
3. Control execution order and concurrency
4. Track flaky tests and quarantine
5. Periodically prune obsolete tests

Key Decisions (Project-Specific):

• Suite boundaries and tagging conventions
• CI schedule for full vs partial runs
• Test ownership and maintenance cadence

---

Project-Specific Implementation Notes

Customize per project:

• Align suites with quality gates
• Keep smoke tests under a strict time budget
• Separate UI vs API suites

---

Example Implementation (Playwright)

// playwright.config.ts
import { defineConfig } from '@playwright/​test';

export default defineConfig({
  projects: [
    { name: 'smoke', grep: /​@smoke/ },
    { name: 'regression', grep: /​@regression/ }
  ]
});

---

Best Practices

1. Keep smoke suites small and stable
2. Tag tests consistently
3. Run full suites nightly
4. Track flaky tests with owners
5. Remove redundant coverage

---

Stop Conditions

STOP and escalate if:

• Suite taxonomy is unclear
• Flaky tests are blocking releases
• Test duration exceeds agreed budgets

---

Skill Version: 1.0.0