test-scaffold

Standardize .NET test suites with AAA pattern and naming conventions.

2|Updated Jan 31, 2026
One-click install
npx skills add https://github.com/michaelalber/ai-toolkit --skill test-scaffold
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test-scaffold
Source: https://github.com/michaelalber/ai-toolkit/tree/main/skills/test-scaffold
Command: npx skills add https://github.com/michaelalber/ai-toolkit --skill test-scaffold

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill establishes consistent conventions and patterns for writing .NET tests, ensuring clarity, maintainability, and adherence to best practices across your projects.

Core Features & Use Cases

  • AAA Pattern Enforcement: Guarantees tests follow Arrange-Act-Assert structure.
  • Descriptive Naming: Enforces MethodName_Scenario_ExpectedResult for clear test intent.
  • Project Structure Guidance: Provides a standard layout for test projects.
  • Use Case: When starting a new .NET project or refactoring an existing test suite, use this Skill to define and apply a uniform testing methodology, making tests easier to understand and debug.

Quick Start

Apply the test-scaffold skill to establish .NET testing conventions for your project.

Frequently Asked Questions about test-scaffold

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

FAQPage Schema
How do I standardize .NET test structure and naming conventions?

Standardize .NET test structure by enforcing the AAA pattern and descriptive MethodName_Scenario_ExpectedResult naming. This approach ensures your unit and integration tests remain maintainable and clearly communicate their intent across the project lifecycle.

What is the AAA pattern in xUnit and FluentAssertions testing?

The AAA pattern in xUnit testing structures tests into Arrange, Act, and Assert sections. FluentAssertions provides readable assertion syntax within the Assert phase, ensuring your .NET test suites are robust and easy to debug.

Can I use NSubstitute with xUnit for .NET integration testing?

Yes, you can use NSubstitute with xUnit for .NET integration testing. This combination allows you to create robust test suites by substituting dependencies, enabling isolated unit and integration tests that follow standard project structure guidelines.

What's the best way to organize a .NET test project layout?

The best way to organize a .NET test project is to apply a uniform testing methodology that defines a clear project structure. This standardization makes tests easier to understand and debug when starting new projects or refactoring existing suites.

Does this testing approach work for both unit and integration tests in C#?

Yes, this testing approach works for both unit and integration tests in C#. It standardizes .NET testing practices by enforcing consistent conventions, ensuring clarity and maintainability across your entire C# test suite.