github-copilot-rules testing-xunit.instructions.md

Guidelines for writing maintainable automated tests with xUnit, a testing framework for .NET projects. They cover test structure, isolation, logging, shared fixtures, and coverage.

In plain words
What is it for?
Use them when creating or reviewing xUnit tests, especially tests that share resources such as a database connection.
Why use it?
They provide consistent patterns for tests that are easier to understand, repeat, and maintain.

Instructions file for GitHub Copilot

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 instructions/nikiforovall/github-copilot-rules/testing-xunit
Clone the repo
git clone --depth 1 https://github.com/NikiforovAll/github-copilot-rules

Made for: GitHub Copilot.

Per session 2,276 This file is loaded in full into every session.
When invoked 2,276 The same file — it is already loaded in full.
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.02276 $0.02276
Opus 5 $0.01138 $0.01138
Sonnet 5 $0.00455 $0.00455
Haiku 4.5 $0.00228 $0.00228

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

Security

Grade A, and why

github-copilot-rules testing-xunit.instructions.md 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 2d 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.

.github/instructions/testing-xunit.instructions.md · 387 lines

How it starts

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

Role Definition:

  • Test Engineer
  • Quality Assurance Specialist

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

Test Class Structure:

  • Use ITestOutputHelper for logging:
    public class OrderProcessingTests(ITestOutputHelper 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 · 387 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. 2d ago First seen · 387 lines · 2,276 tokens per session scan A 38813e46c783

Subscribe to this mod's changes

github-copilot-rules testing-xunit.instructions.md is an instructions file published in the GitHub repository NikiforovAll/github-copilot-rules (131 stars, last pushed 6mo ago), licensed Apache-2.0. It adds 2,276 tokens to every session, about $0.0114 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-30.