Asynkron Asynkron.Testrunner
asynkron-asynkron.testrunner is a Claude Code plugin for the Ship phase that centers on a .NET test runner with TRX capture, history, regression charts, and an expanded multi-plugin agent toolkit.
by asynkron · github.com/asynkron/Asynkron.TestRunner
Wire Claude Code to a .NET-focused test-runner plugin ecosystem that wraps dotnet test, keeps TRX history, and supports agent-driven review and workflow skills around quality gates.
Add it to Claude Code
Install the plugin in Claude Code. One command, paste-ready.
/plugin install asynkron-asynkron.testrunner@asynkron/Asynkron.TestRunnerBuilt to be called by your agent
Skillselion is itself an MCP server. Your agent can pull this entry and a paste-ready install config straight from the API - no copy-paste.
Retrieve this entry with skillselion.get_details("plugin:asynkron/Asynkron.TestRunner") and the paste-ready config with skillselion.get_install_config("plugin:asynkron/Asynkron.TestRunner").
What it does
asynkron-asynkron.testrunner is a Claude Code plugin catalog entry for the Asynkron.TestRunner repository—a .NET global tool that wraps dotnet test, captures TRX results, tracks history, and surfaces regression charts. Solo builders and small teams shipping .NET APIs or services can treat it as the testing spine while optional bundled plugins add agent hooks, review prompts, and workflow skills suggested by its large keyword surface (validation, security, ralph loops, hookify, and more). Install when you are hardening releases or debugging flaky suites and want repeatable CLI test runs plus visual trend data, not when you only need a one-off unit test snippet. The bundle is heavier than a single skill: thirteen plugin slots imply a toolkit orientation. Pair it with your existing solution file and CI; let the runner own execution and reporting while Claude Code plugins steer pre-commit checks and post-run analysis.
Highlights
- .NET global tool pattern: wraps dotnet test and captures TRX output for history
- Tracks test history and displays regression charts for confidence over time
- Marketplace bundle lists 13 plugins spanning tests, hooks, review, and agent workflows
- Keywords cover validation, security review, migration, and iterative dev loops
- Suited to AI-assisted .NET teams using Claude-style agents alongside test runs
Why builders use it
Running dotnet test manually leaves no durable TRX history or regression view, and agents lack a structured plugin stack for validation and review around .NET suites.
You get wrapped test execution with stored TRX and charts, plus up to thirteen related plugins to align Claude Code workflows with repeatable .NET quality gates.
At a glance
- Type - Plugin in Testing.
- Adoption - 0 installs, 3 stars, 0 votes.
FAQ
Who is asynkron-asynkron.testrunner for?
It is for developers on .NET who run dotnet test regularly and use Claude Code (or similar agents) and want TRX-backed history, regression charts, and optional workflow plugins in one catalog entry.
When should I use asynkron-asynkron.testrunner?
Use it in the ship and testing subphase when you need automated test runs with persisted results, trend charts, and agent-assisted review before releases or after refactors.
How do I add asynkron-asynkron.testrunner to my agent?
Install the Asynkron.TestRunner .NET global tool per repository docs, register the asynkron/Asynkron.TestRunner plugin bundle in Claude Code, and enable the plugins you need for tests, hooks, and review.
Comments
Share how you use asynkron-asynkron.testrunner, gotchas, or tips for other indie builders.
No comments yet - be the first to share how you use it.