agentleFS
michaelalbermichaelalber/ai-toolkit/skills/test-scaffold/SKILL.md

test-scaffold

Skill3 starsChanged 4 months agoMITView on GitHub

Test generation conventions, naming patterns, mock strategies, and project structure for .NET test suites. Use when generating tests for C#/.NET projects with xUnit, FluentAssertions, and NSubstitute.

4 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    NO INTERDEPENDENCE — tests never depend on order.

    line 25
  2. Very specific:

    Exit criteria: every identified scenario has an AAA-structured, correctly named, isolated test.

    line 47

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Test Scaffold

"The ratio of time spent reading versus writing code is well over 10 to 1. Tests should be the most readable code in the project." -- Robert C. Martin

Core Philosophy

This skill provides the conventions, patterns, and structural guidance for generating .NET test suites with xUnit, FluentAssertions, and NSubstitute: test naming, file organization, mock strategy, the AAA (Arrange-Act-Assert) structure, and test project setup. Apply these conventions consistently across every generated test. Tests are documentation of behavior — they must be the most readable code in the project, isolated, deterministic, and independent of execution order.

Non-Negotiable Constraints:

  1. AAA ALWAYS — every test follows Arrange-Act-Assert with explicit comment markers; never mix Act and Assert in one expression.
  2. DESCRIPTIVE NAMING — every test name is MethodName_Scenario_ExpectedResult, a complete sentence describing what is tested.
  3. ONE CONCEPT PER TEST — each test verifies one logical concept (multiple asserts allowed only when they verify aspects of that same concept).
  4. NO INTERDEPENDENCE — tests never depend on order; each sets up its own state, runs in isolation, and cleans up.
  5. MOCK ONLY WHAT YOU OWN — mock interfaces you control; for third-party libraries use their test helpers or wrap them in your own interface first.

Workflow

IDENTIFY   The unit under test (handler, validator, service, endpoint, pipeline behavior) and the
           scenarios to cover: happy path, not-found, validation, exception, guard clause, edge,
           state change, side effect.

CHOOSE     The test type per scenario (decision table in references/test-patterns.md):
           unit + mocks · validator TestValidate() · WebApplicationFactory integration ·
           InMemory DbContext · mocked RequestHandlerDelegate for behaviors.

SCAFFOLD   Place the test file mirroring src/ structure (naming-conventions.md). Write each test
           AAA-structured, named MethodName_Scenario_ExpectedResult. Build data with builders;
           mock only external boundaries (mock-patterns.md); use InMemory DbContext, not a mocked one.

VERIFY     dotnet test passes; each test isolated and order-independent; no testing of private
           methods or framework code; DbContext disposed; no hardcoded GUIDs/dates.

Exit criteria: every identified scenario has an AAA-structured, correctly named, isolated test; the right test type per scenario; mocks limited to external boundaries; dotnet test green.

State Block

<test-scaffold-state>
phase: IDENTIFY | CHOOSE | SCAFFOLD | VERIFY | COMPLETE
unit_under_test: [class/member]
scenarios: [count identified]
tests_written: [count]
test_types: [unit | validator | integration | behavior | db]
build_status: pass | fail | not-run
last_action: [description]
next_action: [description]
</test-scaffold-state>

Output Template

  • Project structure, .csproj, GlobalUsings, AAA example, data builders, InMemory factory, FluentValidation, WebApplicationFactory, when-to-use table, pitfalls — references/test-patterns.md.
  • Mock/stub/fake patterns (repositories, mediator, HttpClient, DbContext) — references/mock-patterns.md.
  • Test naming patterns, file organization, project structure conventions — references/naming-conventions.md.

Integration with Other Skills

SkillRelationship
tdd-loopThe RED phase writes a failing test first; this skill supplies the conventions, naming, and structure those tests follow.
tdd-agentAutonomous operating mode of the TDD loop that generates tests — it applies these scaffolding conventions.
dotnet-vertical-sliceScaffolds the feature handlers/validators/endpoints this skill writes tests for; the test tree mirrors the slice structure.
evaluate-testsAudits generated tests for TDD discipline and quality — run it after scaffolding to verify the suite.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.