kova-test-performance

To fix slow Vitest execution without losing coverage, establish an evidence-first baseline using full-suite and scoped runs, diagnose import hotspots, refactor module loading, and verify with updated before/after performance reporting.

High CPU and RSS memory usage during Vitest integration tests is caused by import hotspots, eager plugin or channel loading, and gateway or server lifecycle overhead at integration-to-unit boundaries.

Diagnose import duration breakdowns in a slow Vitest test file by running scoped Vitest benchmarks, using import breakdown tooling to identify module loading hotspots, and targeting narrower helpers for refactoring.

You can optimize Kova test runtime for full-suite group runs by applying evidence-first benchmarking, reducing cold-start costs, and avoiding unnecessary module loading to decrease CPU and RSS while preserving coverage.

The best way to ensure test reliability after performance optimizations is to execute mandatory verification runs that maintain the coverage shape and update performance reports with before and after metrics.