dotnet-testing-test-naming-conventions
CommunityEnforce consistent test naming for .NET projects.
Authorkevintsengtw
Version1.0.0
Installs0
System Documentation
What problem does it solve?
Inconsistent test naming across a .NET codebase makes tests hard to read, maintain, and reason about. This skill standardizes naming to improve clarity, consistency, and documentation of test intent.
Core Features & Use Cases
- Standardized method naming using the three-part format: <Method><Scenario><Expected>.
- Consistent test class naming by suffixing with "Tests" (e.g., Calculator -> CalculatorTests).
- Clear guidance for parameterized tests naming to improve readability and traceability.
Quick Start
Apply the three-part naming format to test methods. Rename test classes to end with "Tests". For parameterized tests, follow consistent naming like Method_Scenario_Input_Expected for each data case.
Dependency Matrix
Required Modules
None requiredComponents
Standard package💻 Claude Code Installation
Recommended: Let Claude install automatically. Simply copy and paste the text below to Claude Code.
Please help me install this Skill: Name: dotnet-testing-test-naming-conventions Download link: https://github.com/kevintsengtw/dotnet-testing-agent-skills/archive/main.zip#dotnet-testing-test-naming-conventions Please download this .zip file, extract it, and install it in the .claude/skills/ directory.
Agent Skills Search Helper
Install a tiny helper to your Agent, search and equip skill from 223,000+ vetted skills library on demand.