testrunner

Detect flaky, hanging, and crashing .NET tests with per-test timeouts.

32|3|Updated Feb 12, 2026
One-click install
npx skills add https://github.com/asynkron/asynkron-skills --skill testrunner
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: testrunner
Source: https://github.com/asynkron/asynkron-skills/tree/main/skills/testrunner
Command: npx skills add https://github.com/asynkron/asynkron-skills --skill testrunner

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Stabilizes .NET test suites by automatically detecting flaky, hanging, and crashing tests, reducing wasted time and improving reliability.

Core Features & Use Cases

  • Hang detection with per-test timeouts to identify stalled tests.
  • Automatic isolation to locate the root cause by splitting test trees and running branches independently.
  • History tracking and regression analysis to surface flaky patterns over time.
  • Diagnostics-friendly reports and easy integration with existing CI workflows for large and unstable test suites.

Quick Start

Integrate Asynkron.TestRunner into your dotnet test workflow and let it automatically detect, isolate, and report flaky tests.

Frequently Asked Questions about testrunner

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

FAQPage Schema
How do I stabilize flaky .NET tests in a large test suite?

Flaky .NET tests are stabilized by automatically detecting hanging, crashing, or memory-intensive tests and isolating them. This Skill splits test trees and runs branches independently to locate root causes while tracking history for regressions.

How does test isolation work for identifying the root cause of flaky dotnet tests?

Test isolation works by splitting the test tree and running branches independently to pinpoint the root cause of failures. This automated process ensures reliable, traceable test outcomes across large dotnet test runs.

Can I integrate automated hang detection into my existing CI workflows for dotnet test suites?

Yes, automated hang detection integrates easily with existing CI workflows. It uses per-test timeouts to identify stalled tests and generates diagnostics-friendly reports for unstable dotnet test runs without disrupting pipelines.

What is the best way to track flaky test regressions over time in .NET projects?

The best way to track flaky test regressions is by maintaining history tracking and regression analysis over time. This surfaces flaky patterns across projects, ensuring reliable and traceable test outcomes for large-scale runs.

Do I need per-test timeouts to detect stalled tests in .NET?

Yes, per-test timeouts are required to detect stalled tests. By configuring these timeouts, the test runner can automatically identify hanging tests and manage them safely to prevent stalled test executions.