skills.rest
kirillshilin
kirillshilinCOMMUNITY
Explore all skills by this author →
GitHub

unit-testing

Create xUnit tests for .NET classes using AAA pattern and Should_ naming.

Updated Aug 27, 2026
Search Tags:#dotnet#unit-testing#naming-conventions#xunit#test-organization#testing-patterns#aaa-pattern
One-click install
npx skills add https://github.com/kirillshilin/instructions --skill unit-testing-kirillshilin
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: unit-testing
Source: https://github.com/kirillshilin/instructions/tree/main/obsolete/claude/skills/unit-testing
Command: npx skills add https://github.com/kirillshilin/instructions --skill unit-testing-kirillshilin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Writing reliable unit tests for .NET applications can be time-consuming without a structured approach; this skill provides a framework to create xUnit tests following the Should_ naming convention, with proper AAA structure and region organisation.

Core Features & Use Cases

  • Plan and scaffold tests using AAA pattern and Should_ naming conventions.
  • Mirror source structure by placing tests under tests/ directories that reflect src/ paths.
  • Enforce consistency with region-based organization and FluentAssertions for clear assertions.

Quick Start

Write a new unit test class for the class under test and run the tests to validate coverage.

Frequently Asked Questions about unit-testing

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write xUnit tests for .NET that follow the AAA pattern and clear naming conventions?▼

To write xUnit tests for .NET, structure each test using the Arrange-Act-Assert (AAA) pattern and apply the Should_ naming convention to clarify intent. This approach ensures tests are reliable, readable, and consistently organized.

What is the best way to organize .NET unit tests to mirror my source structure?▼

Organizing .NET unit tests involves mirroring your source structure by placing test files under tests/ directories that directly reflect your src/ paths. Using region-based organization within test classes further enforces consistency and maintainability across the project.

Can I use FluentAssertions with xUnit when scaffolding .NET unit tests?▼

Yes, you can use FluentAssertions with xUnit to create clear and expressive assertions in .NET unit tests. Pairing FluentAssertions with the AAA pattern and Should_ naming conventions enhances test readability and provides precise failure diagnostics.

How do I handle mocking dependencies when writing xUnit tests for refactored .NET classes?▼

Mocking dependencies in xUnit tests for refactored .NET classes requires isolating the class under test by substituting external interfaces with mock objects. This ensures tests remain focused and reliable without relying on actual external implementations.

Does this unit testing approach require a specific test framework for .NET projects?▼

This specific unit testing approach requires xUnit for .NET projects, as the structured test scaffolding relies on its framework. It specifically integrates xUnit features alongside FluentAssertions and the Should_ naming convention for optimal test reliability.

Related Skills

Explore More Software Engineering Skills→
rudironsonirudironsoni

dotnet-add-testing

Scaffold xUnit test projects with Coverlet coverage in .NET.

Community
Intermediate
vincent-kkvincent-kk
1

test-generator

Generate Vitest-based unit, integration, and end-to-end test templates from TypeScript/React source files.

Community
Advanced
manxmanx

unit-test-specialist

Automate unit testing for .NET 9 projects with xUnit and Moq.

Community
Basic
ojrojasojrojas

dotnet-test-frameworks

Identifies.NET test frameworks and compares their assertion APIs, skipping patterns, and setup/teardown methods.

Community
Intermediate