Developer: Testing

Router command that verifies implementations work correctly.

Key distinction: Testing verifies the software works correctly (Dev concern). Validation verifies it meets requirements (PO concern).

Routing

Input	Strategy
story <path>	Story Testing (unit/component)
feature <id>	Feature Testing (integration)
<path> (auto-detect)	Detect from path pattern

---

Strategy: Story Testing

Trigger: dev:test story <path> or auto-detected story path

Prerequisites

• Story status must be coded
• Implementation notes exist

Testing Approach

1. Auto-detect testing frameworks
2. Run automated tests when available
3. Generate checklist as supplement/fallback

Process

Phase 1: Context Loading

1. Read user story and acceptance criteria
2. Read implementation notes
3. Identify files created/modified

Phase 2: Framework Detection

Detected Testing Setup:
- Framework: Jest / Pytest / Go test
- Runner: npm test / pytest / go test
- Coverage: Available
- E2E: Playwright detected

Phase 3: Automated Testing

npm test -- --coverage
# or equivalent

Analyze:

• Pass/fail counts
• Coverage for modified files
• New vs existing tests

Check quality:

• Happy paths covered?
• Error cases tested?
• Edge cases handled?

Phase 4: Test Checklist

Create {story_path}/test-checklist.md:

# Test Checklist: {Story Title}

## Automated Tests

| Metric | Value |
|--------|-------|
| Total | 24 |
| Passing | 24 |
| Coverage | 87% |

## Manual Test Cases

### TC-001: {Test Name}
**Preconditions**: {setup}
**Steps**:
1. {action}
2. {action}
**Expected**: {result}
**Result**: [ ] Pass / [ ] Fail

### TC-002: {Error Case}
...

## Exploratory Notes
{observations}

## Issues Found
| ID | Description | Severity |
|----|-------------|----------|
| BUG-001 | ... | High |

## Summary
- [ ] All automated tests passing
- [ ] All manual cases executed
- [ ] No critical bugs
- [ ] Ready for dev documentation

Phase 5: Status Update

If all tests pass:

• Story status → tested

Create {story_path}/test-report.md:

# Test Report: {Story Title}

## Summary
- **Date**: {timestamp}
- **Result**: PASS / FAIL

## Automated
- Tests: 24/24 passing
- Coverage: 87%

## Manual
- Cases: 5/5 passed

## Issues
None / {list}

## Recommendation
Ready for documentation / Needs fixes

Output

✅ Story Testing Complete

Story: {title}

Automated Tests:
  ✅ 24/24 passing
  ✅ Coverage: 87%

Manual Tests:
  ✅ 5/5 passed

No issues found.

→ Next (DEV): dev:document story {story_path}

---

Strategy: Feature Testing

Trigger: dev:test feature <id> or auto-detected feature path

Prerequisites

• All stories must have status dev_documented
• All story tests passing

Focus

• Inter-story integration: Stories work together
• End-to-end flows: Complete user journeys
• Data consistency: Shared state handled
• Performance: Feature performs as whole

Process

Phase 1: Feature Analysis

1. Load feature.json and PRD
2. List stories and relationships
3. Identify integration points
4. Map E2E flows from PRD

Phase 2: Integration Test Planning

Based on:

• User flows from PRD
• Story dependencies
• Shared resources

Phase 3: Test Execution

npm run test:integration
# or equivalent

Phase 4: Integration Checklist

Create .hefesto/features/{id}/integration-tests.md:

# Integration Tests: {Feature Title}

## User Flow Tests

### Flow 1: {Name}
**Stories**: 001, 002, 003
**Steps**:
1. [ ] Complete story 001 action
2. [ ] Transition to story 002
3. [ ] Complete story 002 action
**Result**: [ ] Pass / [ ] Fail

### Flow 2: {Error Flow}
...

## Integration Point Tests

### IP-1: {Story A} → {Story B}
**Testing**: Data passing
**Steps**: ...
**Result**: [ ] Pass / [ ] Fail

## Performance Tests

### Perf-1: {Scenario}
**Threshold**: < 500ms
**Actual**: {measured}
**Result**: [ ] Pass / [ ] Fail

## Issues
| ID | Description | Stories | Severity |
|----|-------------|---------|----------|

Phase 5: Report & Status

Create .hefesto/features/{id}/integration-report.md

Update:

• workflow.feature_tested → true

Output

✅ Feature Integration Testing Complete

Feature: {title}

Results:
  User Flows:     ✅ 4/4 passed
  Integration:    ✅ 6/6 passed
  Performance:    ✅ 2/2 passed

Automated: 15/15 passing

No issues found.

→ Next (PO): po:validate feature {id}

---

Testing vs Validation

Aspect	Testing (Dev)	Validation (PO)
Question	Does it work?	Does it meet requirements?
Focus	Correctness	Completeness
Methods	Automated + manual tests	AC verification
Output	Test reports	Validation reports