valynt-test-infra

Fix vitest module resolution errors by aligning vitest alias configurations and correcting setup.ts mocks to ensure dependencies resolve correctly during test execution, stabilizing failures caused by misconfigured environments.

Widespread test infrastructure failures stem from missing imports, hoisting errors, environment misconfigurations, and brittle setup code rather than application logic, requiring diagnostic workflows to triage and resolve across development and CI pipelines.

Triage provider mock setup errors by running a diagnostic workflow that categorizes failures into import resolution, setup errors, provider mocks, and environment variables, then applying prescribed configuration changes to stabilize tests.

Yes, the diagnostic workflow applies across local development and CI pipelines, providing repeatable triage steps and recommended code or config changes to sustain test stability in both environments.

The best way to diagnose missing import and hoisting errors is running a structured diagnostic workflow that maps error patterns to prescribed fixes, including vitest alias alignment and PNPM overrides guidance to restore stability.

Avoid using a test infrastructure diagnostic workflow when failures are caused by actual application logic bugs rather than module resolution, setup, provider mocks, or environment misconfigurations, as these require logic debugging instead.