xunit
Write, run, or repair .NET tests that use xUnit with the right package, CLI, and runner guidance. USE FOR: xUnit v2 or xUnit v3 projects; adding, running, debugging, or repairing xUnit tests; choosing between VSTest and Microsoft.Testing.Platform. DO NOT USE FOR: TUnit projects; MSTest projects. INVOKES: inspect the repository context, edit targeted files, and run relevant build, test, lint, or validation commands when changes are made.
How do I install this agent skill?
npx skills add https://github.com/managedcode/dotnet-skills --skill xunitIs this agent skill safe to install?
- Gen Agent Trust Hubpass
The xunit skill is a set of instructions for managing .NET testing workflows. It provides guidance on detecting xUnit versions, selecting appropriate test runners, and executing standard .NET CLI commands. No security risks or malicious patterns were detected.
- Socketpass
No alerts
- Snykpass
Risk: LOW · No issues
What does this agent skill do?
xUnit.net
Diagnostic Output Budget
Keep native test progress and ANSI visible; use the detected runner's supported flags (--progress on --ansi on for MTP/TUnit), not MTP switches on VSTest. Keep console logs at Warning or higher and one concise final summary. Do not replay progress redraws, successful-test output, or Information/Debug/Trace logs into model context. On failure/crash, show only the failing test/resource, root error, and relevant stack frames; deduplicate and cap each diagnostic response at 80 lines / 8 KiB. Never dump entire console/host/browser logs, HTML, TRX, or crash artifacts. Keep necessary artifacts size-bounded outside context, link them, and inspect exact bounded excerpts. Preserve the runner exit code through capture/filtering; disclose truncation. Silence alone does not establish a hang.
Trigger On
- the repo uses xUnit v2 or xUnit v3
- you need to add, run, debug, or repair xUnit tests
- the team is unsure whether a project is using VSTest or Microsoft.Testing.Platform
Value
- produce a concrete project delta: code, docs, config, tests, CI, or review artifact
- reduce ambiguity through explicit planning, verification, and final validation skills
- leave reusable project context so future tasks are faster and safer
Do Not Use For
- TUnit projects
- MSTest projects
- generic test strategy with no xUnit-specific mechanics
Inputs
- the nearest
AGENTS.md - the test project file and package references
- the active runner model for the test project
Quick Start
- Read the nearest
AGENTS.mdand confirm scope and constraints. - Run this skill's
Workflowthrough theRalph Loopuntil outcomes are acceptable. - Return the
Required Result Formatwith concrete artifacts and verification evidence.
Workflow
- Detect the active xUnit model before changing commands:
xunitusually means v2xunit.v3means v3xunit.runner.visualstudioplusMicrosoft.NET.Test.Sdkusually means VSTest compatibility is enabledTestingPlatformDotnetTestSupportorUseMicrosoftTestingPlatformRunnermeans Microsoft.Testing.Platform is in play
- Read the repo's real
testcommand fromAGENTS.md. If the repo has no explicit command yet, start withdotnet test PROJECT_OR_SOLUTION. - Keep the runner model consistent:
- xUnit v2 usually runs through VSTest
- xUnit v3 can run as a standalone executable with
dotnet run - xUnit v3 can also integrate with Microsoft.Testing.Platform
- do not mix VSTest-only switches into Microsoft.Testing.Platform runs
- Run the narrowest useful scope first:
- one project
- one class
- one trait
- one method
- Prefer
[Theory]for stable data-driven coverage and[Fact]for single-path invariant checks. - Keep
xunit.analyzersenabled when present. Fix analyzer findings instead of muting them casually.
Bootstrap When Missing
If xUnit is requested but not configured:
- Detect current framework first:
rg -n "xunit(\\.v3)?|xunit\\.runner\\.visualstudio|TestingPlatformDotnetTestSupport|UseMicrosoftTestingPlatformRunner|TUnit|MSTest" -g '*.csproj' .
- If the repo currently uses
TUnitorMSTest, do not auto-migrate. Returnstatus: not_applicableunless migration is explicitly requested. - For explicit xUnit adoption, add packages to the target test project:
dotnet add TEST_PROJECT.csproj package xunit.v3- optional VSTest bridge:
dotnet add TEST_PROJECT.csproj package xunit.runner.visualstudio
- Add repo test commands and runner notes to
AGENTS.md. - Run
dotnet test TEST_PROJECT.csprojor repo-defined xUnit command and returnstatus: configuredorstatus: improved.
Deliver
- xUnit tests that match the repo's active xUnit version and runner
- commands that work in local and CI runs
- focused verification before broader suite execution
Validate
- the chosen CLI matches the active runner model
- test filters or focused runs are valid for that runner
- tests use deterministic inputs and assertions
- xUnit-specific analyzers remain active unless the repo documents an exception
Ralph Loop
Use the Ralph Loop for every task, including docs, architecture, testing, and tooling work.
- Plan first (mandatory):
- analyze current state
- define target outcome, constraints, and risks
- write a detailed execution plan
- list final validation skills to run at the end, with order and reason
- Execute one planned step and produce a concrete delta.
- Review the result and capture findings with actionable next fixes.
- Apply fixes in small batches and rerun the relevant checks or review steps.
- Update the plan after each iteration.
- Repeat until outcomes are acceptable or only explicit exceptions remain.
- If a dependency is missing, bootstrap it or return
status: not_applicablewith explicit reason and fallback path.
Required Result Format
status:complete|clean|improved|configured|not_applicable|blockedplan: concise plan and current iteration stepactions_taken: concrete changes madevalidation_skills: final skills run, or skipped with reasonsverification: commands, checks, or review evidence summaryremaining: top unresolved items ornone
For setup-only requests with no execution, return status: configured and exact next commands.
Load References
Example Requests
- "Run this xUnit suite correctly."
- "Fix our xUnit v3 test command."
- "Add an xUnit regression test and keep CI compatible."
How can the creator link this skill?
Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.
<a href="https://skillzs.dev/skills/managedcode/dotnet-skills/xunit">View xunit on skillZs</a>