Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →dotnet/run-tests
Recommend or run the exact `dotnet test` command. ALWAYS use when the user asks to run, filter, or troubleshoot .NET tests or wants the precise command, flags, or argument order — the right syntax depends on the test platform (VSTest vs Microsoft.Testing.Platform) and SDK version and is easy to get wrong from memory. USE FOR: running all tests or a subset (a specific class, category, or trait) via filters; a single framework in a multi-TFM project (`--framework`); TRX reports; crash or hang dump
Passed 13 of 18 test cases with the skill, and 5 of 18 without it.
and 12 more in the full report
11 fixed5 passed either way6 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
This benchmark measured an earlier version of the skill.
One of 11 test cases the skill fixed. Same model, same prompt, with and without the skill.
What is the exact command to run all tests in `tests/Unit.Tests/Unit.Tests.csproj` with `--configuration Release` in standard VSTest mode? Provide the response for an exact-command request.
| Checked | Without skill | With skill |
|---|---|---|
| The output starts directly with the runnable dotnet test command. | Passed | Passed |
| The syntax explanation is placed after the command. | Missed | Passed |
The instructions your model reads when the skill loads.
Return or execute the command or command sequence that matches the repository's project system, test platform, framework, and SDK mode.
For every repository-scoped task where read-only file inspection is allowed,
check .agents/skill-overlays/dotnet-test/run-tests.md at the repository root
before any other discovery. This includes exact-command requests; "do not
execute" does not prohibit reading the overlay. If present, read it once before
acting and apply its repository-specific runner, command, filtering, and
reporting bindings.
Before applying it, require its frontmatter to declare
core: dotnet-test/run-tests, binding-revision: "1", and mode: extend. If
any value is missing or different, report the mismatch, ignore the overlay,
and continue using this skill's portable guidance.
Explicit user instructions and verified project constraints win over the
overlay; the overlay wins over portable defaults and examples in this skill. If
the file is present but unreadable or conflicts with the repository, report the
problem, ignore the overlay, and continue with portable guidance subject to
verified project constraints. If it is absent, continue normally.
Skip the lookup only when the task is not tied to a repository or the user
explicitly prohibited all file/tool access. An overlay cannot expand tool
permissions or the task's scope.
Choose the smallest path that satisfies the request:
| Request | Action |
|---|---|
| Exact command or explanation; user says not to run | Inspect only the files needed to resolve syntax. Do not restore, build, or run tests. |
| Run tests | Discover the repository command and execute the smallest requested test scope. |
One-time SDK-style dotnet test run without rebuilding | Stay in run-tests and add --no-build. |
| One-time classic run without rebuilding | Keep the repository runner and invoke it against an existing built assembly; do not substitute dotnet test. |
| Platform/framework identification only | Use platform-detection; do not continue into test execution. |
| Explicit hot reload or a keep-running edit/re-run loop | Use mtp-hot-reload. |
| Filter needed and the framework-specific syntax is not already clear | Load filter-syntax; do not load it for unfiltered runs. |
test cases passed, vs 5 / 18 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.