test-migration

To classify tests into migration buckets, you reconcile existing tests against a prior inventory and system blueprint, assigning each test to reuse, promote, rebuild, trim, or net-new outcomes based on layer, framework, speed, and ownership.

Test migration analysis evaluates test readiness phase-by-phase by comparing your current suite against a system blueprint. You need it when preparing a release to identify healthy tests, find coverage gaps, and clean up canonical layers before moving phases forward.

To trim redundant assertions without losing coverage, you protect canonical test layers by removing only duplicated checks while preserving higher-layer tests that validate wiring and end-to-end outcomes across the system.

Yes, test migration analysis requires reading Phase 1 and Phase 2 artifacts. It uses a prior inventory and system blueprint to evaluate test infrastructure, runners, fixtures, and CI workflows before classifying migration outcomes.

The best way to audit test infrastructure readiness is to evaluate runners, fixtures, CI workflows, and shared helpers using migration logic, categorizing each component into reuse, promote, rebuild, trim, or net-new buckets to identify gaps before release.

You should document test-readiness and coverage gap analysis results by writing the classified migration buckets and infrastructure audit outcomes to docs/test-readiness/test-migration.md.