auto-test-runner

Automate relevant test execution after code changes using dotnet test.

Updated Dec 31, 2025

Search Tags:#automation #CI/CD #dotnet #test #unit-tests #integration-tests #test-discovery

Ready to run

npx skills add https://github.com/ademceper/merge --skill auto-test-runner

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: auto-test-runner
Source: https://github.com/ademceper/merge/tree/main/server/.claude/skills/auto-test-runner
Command: npx skills add https://github.com/ademceper/merge --skill auto-test-runner

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates identifying and running the most relevant tests automatically after code changes, delivering fast feedback and reducing debugging time.

Core Features & Use Cases

Direct Test File Mapping: map source files to their corresponding test files to identify impacted tests quickly.
Test Discovery & Filtering: use find, grep, and pattern-based strategies to locate relevant tests.
Execution Strategy: run unit tests first; run integration/API tests if necessary.
Pre-commit & CI Workflows: supports pre-commit style checks and CI pipelines to enforce test coverage.
Change Impact Analysis: determine tests affected by changes in domain entities, handlers, repositories, or controllers.

Quick Start

Run unit tests for the changed files; if unit tests pass, run integration tests.

Frequently Asked Questions about auto-test-runner

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I automatically run only the relevant dotnet tests after code changes?▼

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.

What is the best way to execute impacted integration tests for changed API controllers?▼

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.

Can I use this to filter unit tests by category in a CI/CD pipeline?▼

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.

Does the test discovery support finding tests for changed domain entities and repositories?▼

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.

When should I run a full test suite instead of impacted tests during pre-commit?▼

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.

Why does my test runner execute unit tests before integration tests?▼

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.