csharp-testing-standards

A set of rules for C# unit and integration tests, covering NUnit 3, Moq, coverage collection, test structure, naming, assertions, mocking, and parameterized cases.

In plain words
What is it for?
Use it to write or review C# tests, organize test fixtures, configure the system under test, mock dependencies, and test multiple input cases.
Why use it?
It gives test projects a shared approach so tests are easier to discover, understand, run, and review.

Cursor rule for Cursor

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 rules/linuxchata/ai-playbook/csharp-testing-standards
Clone the repo
git clone --depth 1 https://github.com/linuxchata/ai-playbook

Made for: Cursor.

Per session 46 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,195 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.00046 $0.02195
Opus 5 $0.00023 $0.01097
Sonnet 5 $0.00009 $0.00439
Haiku 4.5 $0.00005 $0.00219

Measured yesterday against content hash 0387da228961, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

csharp-testing-standards 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 yesterday.

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.

.cursor/rules/csharp-testing-standards.mdc · 317 lines

How it starts

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

C# Testing Standards

Description

Defines the testing standards, patterns, and conventions for all C# unit and integration test projects. Rules cover test framework usage, naming, structure, mocking, assertions, and parameterization. Apply these rules uniformly across all test projects.


1. Framework & Tooling

  • Test framework: NUnit 3
  • Mocking: Moq
  • Coverage: coverlet.collector
  • Test runner: Microsoft.NET.Test.Sdk + NUnit3TestAdapter

Core NUnit attributes in use:

Attribute Purpose
[TestFixture] Marks the test class
[Test] Marks a single test method
[SetUp] Runs before each test
[TearDown] Runs after each test
[OneTimeSetUp] Runs once before all tests in the fixture
[TestCase] Parameterized test inline values

2. Test Class Structure

2.1 Visibility

Test classes are internal. They do not need to be public – NUnit discovers them via the test runner regardless.

[TestFixture]
internal class OrderServiceTests { }

2.2 System Under Test Field

Name the field under test _sut (system under test) and initialize it in [SetUp]:

private OrderService _sut = null!;

2.3 Mock Fields

Declare all mocks as class-level fields initialized in [SetUp]:

private Mock<IOrderRepository> _orderRepositoryMock = null!;
private Mock<ILogger<OrderService>> _loggerMock = null!;

2.4 SetUp Method

  • Initialize all mocks and the SUT in the [SetUp] method.
  • Configure happy-path default behaviors here so individual tests only override what they specifically need.
  • Keep [SetUp] focused – it should not contain assertions or complex logic.
[SetUp]
public void Setup()
{
    _orderRepositoryMock = new Mock<IOrderRepository>();
    _orderRepositoryMock
        .Setup(r => r.GetByIdAsync(It.IsAny<Guid>(), It.IsAny<CancellationToken>()))
        .ReturnsAsync((Order?)null);

    _sut = new OrderService(
        _orderRepositoryMock.Object,
        NullLogger<OrderService>.Instance);
}

Read the full file on GitHub · 317 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. yesterday First seen · 317 lines · 46 tokens per session scan A 0387da228961

Subscribe to this mod's changes

csharp-testing-standards is a cursor rule published in the GitHub repository linuxchata/ai-playbook (6 stars, last pushed 3mo ago), licensed MIT. It adds 46 tokens to every session and 2,195 once invoked, about $0.0002 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.