skills.rest
behl1anmol
behl1anmolCOMMUNITY
Explore all skills by this author →
Website𝕏@behl1anmolGitHub

mediatorlite-tests

Write xUnit tests for MediatorLite following project conventions.

4|1|Updated Jan 11, 2026
Search Tags:#xunit#fluentassertions#dotnet testing#mediatorlite#source generator tests#pipeline behavior tests#notification tests
One-click install
npx skills add https://github.com/behl1anmol/MediatorLite --skill mediatorlite-tests
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: mediatorlite-tests
Source: https://github.com/behl1anmol/MediatorLite/tree/main/.cursor/skills/mediatorlite-tests
Command: npx skills add https://github.com/behl1anmol/MediatorLite --skill mediatorlite-tests

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the friction of writing non-compliant or broken tests for the MediatorLite .NET mediator library, removing guesswork around source generator registration, test type patterns, and pipeline validation rules.

Core Features & Use Cases

  • Test Convention Reference: Covers xUnit + FluentAssertions patterns, required DI bootstrap sequences, and static state reset rules for the MediatorLite.Tests project.
  • Source Generator Sanity Checks: Includes patterns for using MediatorLiteRegistration.*Count properties to catch source generator regressions instantly without full DI spin-up.
  • Use Case: When adding a new request handler, pipeline behavior, or validator to MediatorLite, use this Skill to write end-to-end tests that verify source-generated dispatch works correctly without manual wiring.

Quick Start

Use this skill to author a new xUnit test for a custom MediatorLite request handler, following the project's static tracking state and required DI registration conventions.

Frequently Asked Questions about mediatorlite-tests

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

FAQPage Schema
How do I write xUnit tests for MediatorLite source-generated dispatch without manual DI wiring?▼

Writing MediatorLite xUnit tests requires following project-specific conventions for DI bootstrap sequences and static handler tracking to verify source-generated dispatch without manual wiring, ensuring test reliability and generator regression detection.

What is the best way to test MediatorLite pipeline behaviors and notification strategies?▼

The best way to test MediatorLite pipeline behaviors and notification strategies is by authoring xUnit tests with FluentAssertions that validate logic against static tracking state and required DI registration conventions.

How do I catch MediatorLite source generator regressions instantly without spinning up full DI?▼

You can catch MediatorLite source generator regressions instantly by using MediatorLiteRegistration Count properties for sanity check assertions, verifying source generator registration without the overhead of full DI spin-up.

Do I need to reset static tracking state between MediatorLite tests?▼

Yes, resetting static tracking state between MediatorLite tests is a required project convention to prevent test pollution and ensure reliable validation of source-generated dispatch and pipeline behaviors.

Why should I avoid obsolete attributes when writing MediatorLite tests?▼

Avoiding obsolete attributes in MediatorLite tests satisfies project-specific compliance rules, ensuring test suites remain reliable and do not trigger warnings that interfere with source generator regression detection.

Related Skills

Explore More Software Engineering Skills→
manxmanx

unit-test-specialist

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

Community
Basic
behl1anmolbehl1anmol
4

mediatorlite-source-generation

Reference MediatorLite.SourceGeneration Roslyn generator discovery pipelines and emitted dispatch code.

Community
Advanced
FortiumPartnersFortiumPartners
11

xUnit Test Framework

Generate and execute xUnit tests for C#/.NET projects with JSON results.

Official
Intermediate
nist0nist0

mediatr

Implement MediatR commands, queries, handlers, and pipeline behaviors in .NET applications.

Community
Advanced