dotnet-testing

dotnet-testing is a skill for Claude Code, Codex from iamBrzDev/enterprise-agent-skills. It costs 127 tokens per session (2,621 once invoked), scanned A, original, MIT.

A testing guide for .NET and C# applications using xUnit, Moq, FluentAssertions, and WebApplicationFactory. It covers unit tests, integration tests, API tests, and test databases.

In plain words
What is it for?
Use it to create test projects, test commands and validators, isolate databases, test ASP.NET Core APIs, configure shared fixtures, and check that tests leave no leftover state.
Why use it?
It helps choose what to test with real code and what to replace with a mock, while avoiding tests that pass only because they use an unrealistic in-memory database.

Skill for Claude CodeCodex

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add skills/iambrzdev/enterprise-agent-skills/dotnet-testing
Any agent
npx skills add iamBrzDev/enterprise-agent-skills --skill dotnet-testing
Clone the repo
git clone --depth 1 https://github.com/iamBrzDev/enterprise-agent-skills

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for dotnet-testing

README.md
[![agentmods](https://agentmods.dev/badge/skills/iambrzdev/enterprise-agent-skills/dotnet-testing.svg)](https://agentmods.dev/skills/iambrzdev/enterprise-agent-skills/dotnet-testing)
Your own site
<a href="https://agentmods.dev/skills/iambrzdev/enterprise-agent-skills/dotnet-testing"><img src="https://agentmods.dev/badge/skills/iambrzdev/enterprise-agent-skills/dotnet-testing.svg" alt="Measured on agentmods" height="20"></a>
Per session 127 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,621 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00127 $0.02621
Opus 5 $0.00063 $0.01311
Sonnet 5 $0.00025 $0.00524
Haiku 4.5 $0.00013 $0.00262

Measured 4d ago against content hash 0f164fab22ef, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

dotnet-testing scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 4d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/dotnet-testing/SKILL.md · 368 lines

How it starts

The opening of the file, as written. The whole thing — 368 lines — stays where its author put it; the contents beside it link to each section on GitHub.

When to activate

  • Writing a unit test or integration test in .NET / C#
  • "What should I mock?" in a .NET testing context
  • Setting up a test project for the first time in a solution
  • Configuring WebApplicationFactory for ASP.NET Core API tests
  • Implementing database isolation for integration tests
  • Testing a MediatR Command, Query, or Handler
  • Testing FluentValidation validators
  • Setting up shared test infrastructure (Docker containers, DB migrations)
  • Any question about xUnit fixtures, test collections, or parallel execution
  • "How do I test this without hitting the real database?"

Rules — Non-negotiable

  1. One Act per test. Strict AAA pattern: one action triggers one outcome. A test that does two things hides which one failed.

  2. Mock only external/unmanaged dependencies. Moq is for third-party APIs, email services, payment gateways — not for repositories or domain services. Test those with real implementations.

  3. Integration tests use real databases. In-memory providers (UseInMemoryDatabase) do not enforce foreign keys, SQL constraints, or stored procedures. Use a real SQL Server instance (Docker) for integration tests.

  4. Every test leaves zero side effects. Use transaction rollback or database reset between tests. Never rely on test execution order.

  5. Unit tests have zero infrastructure. No database, no file system, no HTTP calls, no environment variables in unit tests. If you need them, it's an integration test.

Test Project Structure

solution/
├── src/
│   ├── Domain/
│   ├── Application/
│   ├── Infrastructure/
│   └── API/
└── tests/
    ├── Domain.UnitTests/          # Pure domain logic — no mocks needed usually
    ├── Application.UnitTests/     # Handlers, validators — mock output ports
    ├── Infrastructure.IntegrationTests/  # Repositories against real DB
    └── API.IntegrationTests/      # Full HTTP stack via WebApplicationFactory

Each test project mirrors the production project it covers. Test class names: {ClassUnderTest}Tests.cs Test method names: {MethodName}_{Scenario}_{ExpectedResult}

Read the full file on GitHub · 368 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 4d ago First seen · 368 lines · 127 tokens per session scan A 0f164fab22ef

Subscribe to this mod's changes

dotnet-testing is a skill published in the GitHub repository iamBrzDev/enterprise-agent-skills (5 stars, last pushed 5mo ago), licensed MIT. It adds 127 tokens to every session and 2,621 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

author-test

Generate a test given sample. Parameters: C# SDK repository root; Package name: one of Azure.AI.Projects, Azure.AI.Projects.Agents or Azure.AI.Extensions.OpenAI; the sample to use as a starting point for the test.

Azure/azure-sdk-for-net · 68 tokens

migrate-mstest-v3-to-v4

Use this skill before answering, planning, or editing any MSTest 3.x-to-4.x upgrade or post-upgrade failure. Triggers include "MSTest v4 breaking changes"; CS0507/CS0103/CS1061/CS1615; ExecuteAsync, CallerInfo, DisplayName, or custom TestMethodAttribute; ClassCleanupBehavior; ContainsKey; ThrowsExactly or…

dotnet/skills · 179 tokens

writing-mstest-tests

ALWAYS USE when asked to fix, rewrite, update, improve, modernize, show corrected code for, or explain existing MSTest tests or MSTest-specific configuration. Use for "review" when corrected code or edits are wanted, even for one pasted assertion or passing tests with bad failure output. Covers expected/actual labels…

dotnet/skills · 180 tokens

migrate-mstest-v1v2-to-v3

Use this skill before answering or editing whenever an MSTest v1/v2 project is being upgraded or repaired for v3. Triggers include QualityTools assembly references; MSTest.TestFramework/TestAdapter 1.x-2.x; "upgrade to MSTest v3"; comparing v1 and v2 migration paths; choosing MSTest or MSTest.Sdk; CS0411/CS1503 after…

dotnet/skills · 193 tokens

migrate-xunit-to-mstest

Convert .NET tests from xUnit.net v2/v3 to MSTest v4 while preserving VSTest or MTP. Use for replacing xunit packages, Fact/Theory/InlineData/MemberData, assertions, IClassFixture/ICollectionFixture, ITestOutputHelper, TestContext cancellation, traits/Owner, skips, timeouts, and xUnit parallelization. Also use when a…

dotnet/skills · 141 tokens

migrate-xunit-to-xunit-v3

Migrate .NET test projects from xUnit.net v2 to xunit.v3 and fix v3 breaks. Use for package/CPM conversion, OutputType=Exe, preserving the VSTest or MTP runner (including projects currently using YTest.MTP.XUnit2), incompatible TFMs, async void tests, string-to-Type attributes, custom Fact/Theory/BeforeAfterTest…

dotnet/skills · 149 tokens