Use the open-source free `coverlet` toolchain for .NET code coverage.
Scaffold or Repair a .NET Test Project
MUST USE when an existing .NET test project was excluded from a .slnf/CI solution filter, disappeared from .sln/.slnx discovery, or lost its production ProjectReference; also for requests to set up, create, reuse, add, register, include, or repair a test project. Handles "tests pass directly but CI discovers zero", exact solution wiring, xUnit/NUnit/MSTest, and central packages. DO NOT USE to only author tests in an already-wired project (code-testing), run tests, migrate, or correct MSTest syntax/configuration without changing project or CI files (writing-mstest-tests).
Workflow
1. Establish the repository contract
Start from the task's current working directory. The skill context's Base directory is where these instructions live, not the user's repository. Never search parent temporary directories or treat the skill installation as the workspace. If the expected files are not visible, confirm the current directory before concluding that a project is absent.
Anchor every edit and validation command to the repository path named by the user or established from the current directory. If similarly named fixtures, solutions, or copied trees exist, do not edit or validate one as a substitute for the requested tree. Before changing a solution artifact, record its exact path; after changing it, list that same artifact immediately and require the test project to appear before proceeding.
Read only enough to determine:
- the production project and requested test scope;
- the command and
.sln,.slnx,.slnf, or project graph used by CI; - whether a suitable test project exists, what it references, and where it is
registered;
- the neighboring test framework, runner, target framework, nullable and
implicit-usings conventions; and
- whether package or SDK versions come from
Directory.Packages.props,
Directory.Build.props, global.json, or an MSBuild SDK declaration.
If the user reports that a test project passes directly but solution-level discovery finds nothing, treat that as registration evidence. Inspect the entry point before considering project creation.
2. Create only when the project is absent
Choose one test project for the narrowest requested production project. Follow, in order, the user's explicit framework choice, neighboring test projects, repository-wide package/SDK conventions, then a standard SDK template.
Use a dotnet new template only when its generated framework generation and package style match the repository contract. Inspect template availability before creation. In particular, generic dotnet new xunit commonly emits xUnit 2 packages; for a centrally managed xunit.v3 repository, use a repository or installed xUnit v3 template, or create the minimal SDK project directly. Never generate versioned xUnit 2 references and then rewrite them into xUnit v3.
Then:
- align target framework, nullable, implicit usings, runner, and package style;
- use
dotnet add <test-project> reference <production-project>for only the
production projects exercised by the requested tests;
- delete template sample files such as
UnitTest1.cs, then create a
behavior-named test file rather than repurposing the template filename; and
- omit package versions when central package management supplies them.
For xUnit v3 projects using MTP, preserve or add the executable output and runner selection (or the equivalent supplied by the resolved package):
<OutputType>Exe</OutputType>
<UseMicrosoftTestingPlatformRunner>true</UseMicrosoftTestingPlatformRunner>
Add TestingPlatformDotnetTestSupport=true only for the VSTest-command-mode bridge to MTP. It is not required for SDK 10+ native MTP mode selected by global.json test.runner: Microsoft.Testing.Platform. Use platform-detection to distinguish command mode from the executed runner; neither SDK version nor OutputType=Exe alone proves harness discovery.
3. Repair only the missing edge when the project exists
- Missing production reference: use `dotnet add <test-project> reference
<production-project>, inspect the resulting project, and leave every other project element plus all test source files unchanged. Compare the project before and after so the added ProjectReference` is the only semantic change.
- Missing
.slnor.slnxregistration: run `dotnet sln <entry-point> add
<test-project>, then immediately run dotnet sln <entry-point> list` against that exact path. If the project is absent, the repair has not happened; do not validate a sibling solution or report success.
- Missing
.slnfregistration: add the existing project to its underlying
solution if necessary, then include that same project path in the filter. If the underlying solution already contains it, edit only the filter.
- Multiple solution artifacts: modify only the one named by the user or invoked
by CI. Do not substitute an easier format.
- No solution artifact: preserve the existing project-oriented workflow. Do not
create a solution for aesthetics.
4. Add only the requested smoke behavior
For a newly created project, replace template examples with the smallest smoke suite the user requested. Each test must invoke a real production symbol and assert a concrete deterministic result without network, wall-clock, process, or real-filesystem dependencies.
For an existing-project wiring repair, do not add, rewrite, rename, or expand tests unless the user explicitly asks for test behavior changes. Registration and test authoring are separate operations.
5. Verify the repaired path
Run the narrowest commands that prove the chosen route:
Choose command forms from the actual repository mode: native MTP uses dotnet test --project <test-project> and dotnet test --solution <entry-point>; VSTest command mode uses positional project/solution paths, including when it bridges to MTP. Apply this distinction to every direct-project and entry-point test below. Preserve the exact CI command and its supported .slnf invocation; do not substitute a solution or invent unsupported switches. For classic non-SDK projects, use the repository's documented MSBuild and native test-runner commands instead of any dotnet test example below. If that toolchain is unavailable, report the blocker without migrating the project or claiming successful discovery.
| Route | Required evidence | |---|---| | Newly created project | Mode-aware direct-project test, the exact entry-point command CI uses, and registration listing. If the entry point is a .slnf/.slnx containing tests, run the repository's test command on that artifact rather than proving only that it builds. | | Missing reference | Targeted project test plus the exact solution/root test command requested | | Missing .sln/.slnx registration | Listing and dotnet test for that exact artifact; never use another solution as a fallback | | Missing .slnf entry | Inspect the filter entry and run the exact CI filter build command; do not prepend a deliberately failing alternate command | | Already correct/no-op | Structural inspection of the existing reference and registration. Unless execution was requested, do not run tests merely to prove a no-op because that creates bin/obj and weakens byte-for-byte cleanliness evidence. |
Inspect the repository's command before adding switches. Do not prepend a speculative --no-restore attempt or hide alternatives in command-a || command-b; run the configured entry-point command whose clean exit is the evidence.
For every wiring repair, invoke the exact validation command directly and preserve its exit status. Reading generated files, a grader script, or a later build is not a substitute for observing that command complete successfully.
Before reporting completion, inspect the final changed-file set. Remove only bin/obj or equivalent build artifacts created by this task when they were absent beforehand and are not intentionally tracked; never remove pre-existing artifacts. Preserve the passing command's complete result so the handoff can state the exact entry point and discovered test count.
For a no-op, inspect rather than rewrite and report the existing paths. A green dotnet build is not test-discovery evidence. If validation is blocked, report the exact failing command and first actionable error; never describe an unrun or failed command as successful.
Related skills
Write, run, or repair .NET tests that use MSTest.
Write, run, or repair .NET tests that use NUnit.
These are the skills our senior team ships with. Want us to build your system? Book a 15-min call.