rm-guide-testing

Community

Keep TUnit helpers and doubles consistent

Authormichaelvolz
Version1.0.0
Installs0

System Documentation

What problem does it solve?

This Skill removes the guesswork from TUnit test creation by enforcing consistent fluent assertions, helper file placement, and naming patterns so reviews focus on behavior rather than conventions.

Core Features & Use Cases

  • Fluent assertions: Reminds you to use TUnit's built-in Assert.That(...) style to keep validation expressive and reliable.
  • Naming conventions: Encourages naming test doubles as [Class]_[Type] and placing helpers in [TestClass].Helpers.cs partial files for discoverability.
  • Shared setup: Promotes using TestScope when setting up fixtures so integration helpers remain isolated yet reusable.
  • Use Case: When adding a new API integration test, rely on this Skill to guide naming the mock as ApiClient_Spy, placing helpers near the test class, and wrapping setup in a TestScope helper.

Quick Start

Apply rm-guide-testing when writing or reviewing TUnit tests to reinforce fluent assertion usage, test double naming, and helper placement.

Dependency Matrix

Required Modules

None required

Components

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: rm-guide-testing
Download link: https://github.com/michaelvolz/redmuffin.Blazor.StaticWeb/archive/main.zip#rm-guide-testing

Please download this .zip file, extract it, and install it in the .claude/skills/ directory.
View Source Repository

Agent Skills Search Helper

Install a tiny helper to your Agent, search and equip skill from 471,000+ vetted skills library on demand.