skills.rest
FoxSilou
FoxSilouCOMMUNITY
Explore all skills by this author →
GitHub

unit-testing

Standardizes .NET backend unit tests with French AAA conventions and FluentAssertions syntax.

Updated Apr 1, 2026
Search Tags:#dotnet#unit-testing#naming#fakes#fluentassertions#stubs#aaa
One-click install
npx skills add https://github.com/FoxSilou/ConfigurationClaude --skill unit-testing-foxsilou
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: unit-testing
Source: https://github.com/FoxSilou/ConfigurationClaude/tree/main/backend/.claude/skills/unit-testing
Command: npx skills add https://github.com/FoxSilou/ConfigurationClaude --skill unit-testing-foxsilou

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a unified set of conventions for writing backend unit tests in .NET, enforcing French naming, AAA structure, and the exclusive use of Fakes and Stubs instead of mocks.

Core Features & Use Cases

  • Enforces the Arrange‑Act‑Assert (AAA) pattern with clear separation.
  • Defines French‑language naming for test classes and methods.
  • Restricts test doubles to Fakes and Stubs, banning mocking frameworks.
  • Mandates FluentAssertions for all assertions.
  • Specifies a flat test file layout with an optional Fakes/ folder.
  • Suitable for developers reviewing, creating, or discussing unit tests for command handlers.

Quick Start

Ask the unit-testing skill to generate a test file for the CreerPartie command following the defined conventions.

Frequently Asked Questions about unit-testing

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

FAQPage Schema
How do I structure .NET unit tests using the AAA pattern with Fakes and Stubs?▼

Structure .NET unit tests by separating Arrange, Act, and Assert sections clearly, using Fakes and Stubs instead of mocking frameworks, and asserting outcomes with FluentAssertions syntax.

What are the French naming conventions for unit testing backend command handlers?▼

French naming conventions for unit testing require French-language names for test classes and methods, ensuring test file organization remains flat with an optional Fakes directory for backend command handlers.

Can I use a mocking framework with FluentAssertions for backend unit tests?▼

No, you cannot use a mocking framework; backend unit tests must restrict test doubles to Fakes and Stubs exclusively, while mandating FluentAssertions for all assertions.

What is the best way to organize unit test files for .NET command handlers?▼

The best way to organize unit test files for .NET command handlers is a flat test file layout, keeping test doubles in an optional Fakes directory rather than nesting complex folder hierarchies.

Does this unit testing approach work for .NET projects without mocking frameworks?▼

Yes, this unit testing approach works for .NET backend projects by replacing mocks entirely with Fakes and Stubs, enforcing the AAA pattern and French naming conventions without mocking dependencies.

Related Skills

Explore More Software Engineering Skills→
himanshu231204himanshu231204
2

csharp-testing

Standardize C# and .NET test suites with xUnit, FluentAssertions, and mocking frameworks.

Community
Intermediate
alexmondalexmond
4

test

Run yj-schema-validator tests with Maven Wrapper for full or targeted coverage.

Community
Intermediate
talbenmoshetalbenmoshe
4

manage-fake

Generate and update Fake test doubles for TypeScript interfaces.

Community
Intermediate
JaiminVadadoriyaJaiminVadadoriya
1

mcp-csharp-test

Automate unit and integration tests for C# MCP servers.

Community
Intermediate