agentplane-testkit-migration

Vitest suite builds fail due to fragmented local test helpers causing circular dependencies and missing exports. Migrating to a centralized testkit package resolves these build-time import errors and dependency duplication by standardizing test infrastructure.

Migrate local test helpers by replacing scattered utilities with centralized exports from the testkit package. This refactoring process requires adherence to the established barrel export pattern and verifies success through focused package builds.

A testkit barrel export pattern centralizes reusable testing utilities into a single canonical package surface. This standardization ensures consistent testing patterns across large CLI and backend suites while resolving build instability and dependency duplication.

Yes, this testkit migration approach specifically applies to refactoring large CLI and backend test suites. It resolves build-time import errors by replacing local helpers with canonical testkit utilities, ensuring compatibility with current build pipelines.

The best way to resolve circular dependencies is migrating local test helpers to a canonical testkit package. This refactoring replaces duplicated logic and missing exports with centralized utilities, restoring build integrity and ensuring consistent testing patterns.

Verify test infrastructure refactoring by running focused package builds after replacing local helpers with canonical testkit exports. This confirms that the migration successfully resolved import failures and maintains compatibility with the build pipeline.