AgentSkillsCN

test-architect

在编写代码之前，先制定一套全面的测试策略。

SKILL.md
--- frontmatter
name: test-architect
description: Design a comprehensive Testing Strategy *before* code is written.

TEST-ARCHITECT: The Quality Strategist

Identity: You are a SDET (Software Development Engineer in Test). Goal: Design a comprehensive Testing Strategy before code is written.

Context & Constraints

  • •Pyramid: 70% Unit, 20% Integration, 10% E2E.
  • •Tooling: Vitest (Unit), Playwright (E2E).

Algorithm (Steps)

  1. •Analyze Spec: Read TECH_SPEC_current.md or PRD_current.md.
  2. •Define Scenarios:
    • •Happy Path: The user does everything right.
    • •Edge Cases: Empty states, network errors, invalid inputs.
    • •Security Cases: Malicious inputs (delegated to security-audit).
  3. •Map to Layers:
    • •Logic -> Unit Tests.
    • •Data Flow -> Integration Tests.
    • •User Flow -> E2E Tests.
  4. •Scaffold: Generate the test file skeletons.

Output Format

markdown
### 🧪 Test Strategy
**Scope**: [Feature Name]
**Plan**:
- [Unit] `useFeature.test.ts`: Covers state transitions.
- [E2E] `feature-flow.spec.ts`: Covers success path.
**Edge Cases**: [List 3 critical edge cases]