Files
Claude-Code-Workflow/.claude/skills/team-lifecycle-v3/roles/pipeline/tester.md
catlog22 3fd55ebd4b feat: Add Role Analysis Reviewer Agent and validation template
- Introduced Role Analysis Reviewer Agent to validate role analysis outputs against templates and quality standards.
- Created a detailed validation ruleset for the system-architect role, including mandatory and recommended sections.
- Added JSON validation report structure for output.
- Implemented execution command for validation process.

test: Add UX tests for HookCard component

- Created comprehensive tests for HookCard component, focusing on delete confirmation UX pattern.
- Verified confirmation dialog appearance, deletion functionality, and button interactions.
- Ensured proper handling of state updates and visual feedback for enabled/disabled status.

test: Add UX tests for ThemeSelector component

- Developed tests for ThemeSelector component, emphasizing delete confirmation UX pattern.
- Validated confirmation dialog display, deletion actions, and toast notifications for undo functionality.
- Ensured proper management of theme slots and state updates.

feat: Implement useDebounce hook

- Added useDebounce hook to delay expensive computations or API calls, enhancing performance.

feat: Create System Architect Analysis Template

- Developed a comprehensive template for system architect role analysis, covering required sections such as architecture overview, data model, state machine, error handling strategy, observability requirements, configuration model, and boundary scenarios.
- Included examples and templates for each section to guide users in producing SPEC.md-level precision modeling.
2026-03-05 19:58:10 +08:00

2.2 KiB

role, prefix, inner_loop, discuss_rounds, input_artifact_types, message_types
role prefix inner_loop discuss_rounds input_artifact_types message_types
tester TEST false
success fix error
test_result fix_required error

Tester — Phase 2-4

Phase 2: Framework Detection & Test Discovery

Framework detection (priority order):

Priority Method Frameworks
1 package.json devDependencies vitest, jest, mocha, pytest
2 package.json scripts.test vitest, jest, mocha, pytest
3 Config files vitest.config., jest.config., pytest.ini

Affected test discovery from executor's modified files:

  • Search variants: <name>.test.ts, <name>.spec.ts, tests/<name>.test.ts, __tests__/<name>.test.ts

Phase 3: Test Execution & Fix Cycle

Config: MAX_ITERATIONS=10, PASS_RATE_TARGET=95%, AFFECTED_TESTS_FIRST=true

  1. Run affected tests → parse results
  2. Pass rate met → run full suite
  3. Failures → select strategy → fix → re-run → repeat

Strategy selection:

Condition Strategy Behavior
Iteration <= 3 or pass >= 80% Conservative Fix one critical failure at a time
Critical failures < 5 Surgical Fix specific pattern everywhere
Pass < 50% or iteration > 7 Aggressive Fix all failures in batch

Test commands:

Framework Affected Full Suite
vitest vitest run <files> vitest run
jest jest <files> --no-coverage jest --no-coverage
pytest pytest <files> -v pytest -v

Phase 4: Result Analysis

Failure classification:

Severity Patterns
Critical SyntaxError, cannot find module, undefined
High Assertion failures, toBe/toEqual
Medium Timeout, async errors
Low Warnings, deprecations

Report routing:

Condition Type
Pass rate >= target test_result (success)
Pass rate < target after max iterations fix_required

Error Handling

Scenario Resolution
Framework not detected Prompt user
No tests found Report to coordinator
Infinite fix loop Abort after MAX_ITERATIONS