testing

Rules for writing and running automated tests in .NET projects with xUnit. Automated tests check code behavior repeatedly, while xUnit is a framework for organizing and executing tests.

In plain words
What is it for?
Use them to set up .NET test projects, organize xUnit tests, keep tests independent, collect coverage with Coverlet, and run tests as part of CI.
Why use it?
They encourage tests that are isolated, consistent, maintainable, and meaningful instead of fragile checks that depend on one another. They also define how testing and coverage should fit into CI, the automated build pipeline.

Cursor rule

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/aaronontheweb/dotnet-cursor-rules/testing
Clone the repo
git clone --depth 1 https://github.com/Aaronontheweb/dotnet-cursor-rules
Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 3,607 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.00000 $0.03607
Opus 5 $0.00000 $0.01803
Sonnet 5 $0.00000 $0.00721
Haiku 4.5 $0.00000 $0.00361

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

Security

Grade A, and why

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 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.

csharp/testing.mdc · 594 lines

How it starts

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

Role Definition:

  • Test Engineer
  • Quality Assurance Specialist
  • CI/CD Expert

General: Description: > Tests should be reliable, maintainable, and provide meaningful coverage. Use xUnit as the primary testing framework, with proper isolation and clear patterns for test organization and execution. Requirements: - Use xUnit as the testing framework - Ensure test isolation - Follow consistent patterns - Maintain high code coverage - Configure proper CI/CD test execution

Project Setup:

  • Configure test projects:
    <Project Sdk="Microsoft.NET.Sdk">
      <PropertyGroup>
        <TargetFramework>net8.0</TargetFramework>
        <IsPackable>false</IsPackable>
        <IsTestProject>true</IsTestProject>
        <CollectCoverage>true</CollectCoverage>
        <CoverletOutputFormat>cobertura</CoverletOutputFormat>
      </PropertyGroup>
      
      <ItemGroup>
        <PackageReference Include="Microsoft.NET.Test.Sdk" Version="17.8.0" />
        <PackageReference Include="xunit" Version="2.6.2" />
        <PackageReference Include="xunit.runner.visualstudio" Version="2.5.4" />
        <PackageReference Include="coverlet.collector" Version="6.0.0" />
        <PackageReference Include="coverlet.msbuild" Version="6.0.0" />
      </ItemGroup>
    </Project>
    

Test Class Structure:

  • Use ITestOutputHelper for logging:
    public class OrderProcessingTests
    {
        private readonly ITestOutputHelper _output;
        
        public OrderProcessingTests(ITestOutputHelper output)
        {
            _output = output;
        }
        
        [Fact]
        public async Task ProcessOrder_ValidOrder_Succeeds()
        {
            _output.WriteLine("Starting test with valid order");
            // Test implementation
        }
    }
    
  • Use fixtures for shared state:
    public class DatabaseFixture : IAsyncLifetime
    {
        public DbConnection Connection { get; private set; }
        
        public async Task InitializeAsync()
        {
            Connection = new SqlConnection("connection-string");
            await Connection.OpenAsync();
        }
        
        public async Task DisposeAsync()
        {
            await Connection.DisposeAsync();
        }
    }
    
    public class OrderTests : IClassFixture<DatabaseFixture>
    {
        private readonly DatabaseFixture _fixture;
        private readonly ITestOutputHelper _output;
        
        public OrderTests(DatabaseFixture fixture, ITestOutputHelper output)
        {
            _fixture = fixture;
            _output = output;
        }
    }
    

Test Methods:

  • Prefer Theory over multiple Facts:
    public class DiscountCalculatorTests
    {
        public static TheoryData<decimal, int, decimal> DiscountTestData => 
            new()
            {
                { 100m, 1, 0m },      // No discount for single item
                { 100m, 5, 5m },      // 5% for 5 items
                { 100m, 10, 10m },    // 10% for 10 items
            };
        
        [Theory]
        [MemberData(nameof(DiscountTestData))]
        public void CalculateDiscount_ReturnsCorrectAmount(
            decimal price,
            int quantity,
            decimal expectedDiscount)
        {
            // Arrange
            var calculator = new DiscountCalculator();
            
            // Act
            var discount = calculator.Calculate(price, quantity);
            
            // Assert
            Assert.Equal(expectedDiscount, discount);
        }
    }
    
  • Follow Arrange-Act-Assert pattern:
    [Fact]
    public async Task ProcessOrder_ValidOrder_UpdatesInventory()
    {
        // Arrange
        var order = new Order(
            OrderId.New(),
            new[] { new OrderLine("SKU123", 5) });
        var processor = new OrderProcessor(_mockRepository.Object);
        
        // Act
        var result = await processor.ProcessAsync(order);
        
        // Assert
        Assert.True(result.IsSuccess);
        _mockRepository.Verify(
            r => r.UpdateInventoryAsync(
                It.IsAny<string>(),
                It.IsAny<int>()),
            Times.Once);
    }
    

Read the full file on GitHub · 594 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 · 594 lines · 3,607 tokens per session scan A 36c233977911

Subscribe to this mod's changes

testing is a cursor rule published in the GitHub repository Aaronontheweb/dotnet-cursor-rules (134 stars, last pushed 1y ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 3,607 tokens. 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-30.