auto-test-runner

This Skill automates running relevant dotnet tests after code changes by mapping source files to test files and using test discovery strategies. It executes unit tests first, then integration tests if necessary, to deliver fast feedback.

Running impacted integration tests for changed API controllers requires change impact analysis. This Skill identifies affected tests across domain entities and handlers, executing them via dotnet test with category filters during pre-commit checks.

Yes, you can filter unit tests by category in a CI/CD pipeline. It leverages dotnet test with category filters and orchestrates both unit and integration tests to support pre-commit workflows and enforce test coverage.

Yes, test discovery supports finding tests for changed domain entities and repositories. It uses find, grep, and pattern-based strategies to locate relevant tests, ensuring impacted tests are identified quickly after modifications.

You should run a full test suite during pre-commit when you need comprehensive validation before integration. This Skill supports full-suite options for pre-commit checks, although running impacted unit tests first delivers faster feedback.

Your test runner executes unit tests first to deliver fast feedback and reduce debugging time. If unit tests pass, it then proceeds to execute integration or API tests if necessary, optimizing the development workflow.