improve-ut

To boost unit-test coverage after code changes, analyze the changed files to identify coverage gaps using project-specific unit-test specs, then add or update tests following existing conventions to ensure correctness.

Automated test scope determination works by inspecting changed files and mapping them to project-specific unit-test specs, which dictates whether unit, integration, or regression tests are required based on established project conventions.

The best way to ensure code quality and validation when updating tests is to run lint, typecheck, and test suites after adding or modifying tests, verifying both coverage and correctness against the project's specific specs.

Yes, improving test coverage requires existing project-specific unit-test specs to determine the appropriate test scope and to ensure newly added or updated tests follow the project's established patterns and conventions.

You can use this method to automatically generate tests for changed files by analyzing them against project-specific unit-test specs, mapping the changes, and updating tests while referencing relevant specs to determine scope.