agentleFS
joaoguimaraesprojoaoguimaraespro/personal-finance/.cursor/rules/csharp-testing.mdc

personal-finance / rules

Cursor rule1 starsChanged todayMITView on GitHub

.NET testing: xUnit, assertion and mocking libraries, Testcontainers, WebApplicationFactory, architecture tests

The file

We split this csharp-testing.mdc into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    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. Very specific:

    Test names describe behaviour: Create_ReturnsConflict_WhenNameExists.

    line 23

≈ “Common” is an estimate: at least 1 in 5 of the 6,809 Cursor rule 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
csharp-testing.mdc
---
description: ".NET testing: xUnit, assertion and mocking libraries, Testcontainers, WebApplicationFactory, architecture tests"
globs: **/*.cs,**/*Tests.csproj
alwaysApply: false
---
<!-- Generated by armature from stack-dotnet/rules/csharp/testing.md. Edit the source rule, not this file. -->
# C# testing

Extends [common/testing.md](common-testing.mdc).

## Tools
- xUnit (v3 or the repo's version) for unit and integration tests; the repo's runner (`dotnet test`, Microsoft
  Testing Platform where configured).
- Assertions: the library the repo already uses (AwesomeAssertions, the maintained fork of FluentAssertions, or
  Shouldly). Do not add FluentAssertions 8+ (commercial licence).
- Mocks: NSubstitute or Moq, only at boundaries; prefer real domain objects and in-memory fakes of interfaces.
- Testcontainers (PostgreSQL etc.) for integration tests that need real infrastructure; never the EF in-memory
  provider for behaviour that depends on the database.

## Layout
- One test project per module or layer (`<Module>.Tests`), mirroring `src/`; integration tests in their own project
  so the fast gate can skip them when they need Docker.
- Test names describe behaviour: `Create_ReturnsConflict_WhenNameExists`. Arrange, Act, Assert.

## What to cover
- Domain: factories and state transitions, including every `Error` path.
- Handlers: success and each failure `Result`.
- API: `WebApplicationFactory<TEntryPoint>` through HTTP, so auth, validation, serialization and Problem Details
  are exercised; include a request without a token and one for the wrong tenant.
- Architecture tests for module boundaries and layering where the repo has them.

<!-- Adapted from affaan-m/ECC rules/csharp/testing.md (MIT) at d2ef268 (upstream AwesomeAssertions won over the Ordo frozen copy's FluentAssertions); merged with ordo-api AGENTS.md (test-first per module *.Tests) and personal-finance-sdd (Integration.Tests need Docker, architecture tests). -->

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.