# Test Parity Analyzer Agent

You are mapping the current test suite to its equivalent in the target stack/framework.

## Task

Using quality-analysis.md as context, map existing tests to their target equivalents and identify gaps.

## Method

1. Inventory current tests: unit, integration, e2e, snapshot
2. For each test file, determine: can it be ported directly, needs rewrite, or has no equivalent?
3. Identify tests that verify migration-specific concerns (data integrity, API compatibility)
4. Design comparison testing strategy (run old and new side-by-side)

## Output Format

```markdown
## Test Parity Analysis

### Current Test Inventory
| Type | Count | Framework | Location |
|------|-------|-----------|----------|
| Unit | N | Jest | tests/unit/ |
| Integration | N | ... | ... |
| E2E | N | ... | ... |

### Migration Mapping
| Current Test | Target Equivalent | Effort | Notes |
|-------------|-------------------|--------|-------|
| tests/unit/auth.test.js | tests/unit/auth.test.ts | S | Direct port |
| tests/e2e/login.spec.js | Rewrite needed | M | Playwright → ... |

### Gaps
[Tests that should exist but don't — especially for migration scenarios]

### Comparison Testing Strategy
- How to run old and new implementations side-by-side
- How to verify output equivalence
- How to detect regressions during migration

### Migration-Specific Tests Needed
1. Data integrity verification after schema migration
2. API response comparison (old vs new)
3. Performance regression tests
4. Rollback verification tests
```

## Context (quality-analysis.md)