TUnit
Trigger On
- the repo uses TUnit
- you need to add, run, debug, or repair TUnit tests
- the repo uses Microsoft.Testing.Platform-based test execution
- the repo uses
ClassDataSource<...>(Shared = SharedType.PerTestSession), TUnit.Playwright, or --treenode-filter
Do Not Use For
- xUnit projects
- MSTest projects
- generic test strategy with no TUnit-specific mechanics
Inputs
- the nearest
AGENTS.md
- the test project file and package references
- the repo's current TUnit execution command
Workflow
- Confirm the project really uses TUnit and not a different MTP-based framework.
- Read the repo's real
test command from AGENTS.md. If the repo has no explicit command yet, start with dotnet test PROJECT_OR_SOLUTION.
- Keep the TUnit execution model intact:
- tests are source-generated at build time
- tests run in parallel by default
- on .NET 10, test modules also run in parallel by default up to
Environment.ProcessorCount
- built-in analyzers should remain enabled
- Choose the fixture level deliberately:
- plain TUnit tests for isolated logic
- shared AppHost/Aspire fixtures for HTTP, SignalR, SSE, or UI flows
WebApplicationFactory layered over shared Aspire infra when tests need Host DI services, IGrainFactory, or other runtime internals
- Reuse expensive fixtures with
ClassDataSource<Fixture>(Shared = SharedType.PerTestSession) instead of booting distributed infrastructure per test. Fixture reuse does not serialize consumers: keep the fixture concurrency-safe and give each test unique mutable state.
- Keep tests and test modules parallel. Do not add
--max-parallel-test-modules 1, TUNIT_MAX_PARALLEL_TESTS=1, [assembly: NotInParallel], a class-wide [NotInParallel], or an equivalent global restriction.
- Use keyed
[NotInParallel("collision-domain")] only on the smallest tests that perform destructive changes to the same shared state and can corrupt one another. A shared read-only fixture, expensive startup, module boundary, or vague CI-stability concern is not a reason to limit parallelism.
- Run the narrowest useful scope first with
dotnet test ... --treenode-filter "..." on .NET 10. Use the older -- separator only when the repository is pinned to an SDK that requires it.
- Follow
Test Output Budget: show bounded root-error evidence and link coverage, Playwright screenshots, and HTML artifacts; never dump host logs.
- Use
[Test], [Arguments], hooks, and dependencies only when they make the scenario clearer, not because the framework allows it.
Test Output Budget
- Keep native runner progress and ANSI enabled (
--progress on --ansi on for supported MTP/TUnit runners); use a PTY locally. Do not replay progress redraws into model context. Use the detected runner's flags, not MTP switches on VSTest.
- Show warnings and errors plus one final summary (counts, duration, exit code). Configure test-owned console logging at
Warning; keep Information/Debug/Trace, successful-test output, and expected negative-test noise out of context. Quiet build verbosity alone does not filter application logs.
- On failure, crash, startup error, or timeout, show the failing test/resource, root exception, and relevant stack frames. Deduplicate; cap each diagnostic tool response at 80 lines / 8 KiB, whichever comes first. Never automatically dump stdout/stderr, host logs, browser console history, DOM/HTML, TRX, or crash artifacts.
- Keep necessary diagnostics in size-bounded or rotating artifacts and link them. Search by exact failure/correlation; read bounded excerpts, never whole logs. Capture/filter noisy output before tool delivery, preserve the real exit code, and disclose truncation. Monitor actual activity; silence alone does not prove a hang.
Bootstrap When Missing
If TUnit is requested but not configured yet:
- Detect current state:
rg -n "TUnit|Microsoft\\.Testing\\.Platform" -g '*.csproj' -g 'Directory.Build.*' .
- Add the minimal package set to the test project:
dotnet add TEST_PROJECT.csproj package TUnit
- do not add
Microsoft.NET.Test.Sdk to a current TUnit project; it selects the VSTest path and conflicts with the normal Microsoft.Testing.Platform setup
- Keep the runner model explicit in
AGENTS.md and CI:
- record that the repo uses Microsoft.Testing.Platform-compatible execution for this test project
- record the exact
dotnet test TEST_PROJECT.csproj command the repo will use
- Add one small executable test using
[Test].
- Run
dotnet test TEST_PROJECT.csproj and return status: configured or status: improved.
- If the repo intentionally standardizes on xUnit or MSTest, return
status: not_applicable unless migration is explicitly requested.
Deliver
- TUnit tests that respect source generation and parallel execution
- commands that work in local and CI runs
- framework-specific verification guidance for the repo
- a fixture strategy that matches the actual test scope: logic-only, AppHost/API, Host DI/grains, or Playwright UI
Validate
- the command matches the repo's TUnit runner style
- focused runs use
--treenode-filter rather than VSTest-style --filter
- .NET 10 runs pass MTP options directly without a
-- separator
- no global or assembly-wide single-thread setting has been introduced
- any keyed non-parallel group is limited to tests with a named destructive shared-state collision
- shared distributed fixtures use
SharedType.PerTestSession or an equivalent reuse pattern
- fixture and shared infrastructure are safe for concurrent consumers; mutable data is isolated per test
- built-in TUnit analyzers remain active
- coverage tooling matches Microsoft.Testing.Platform if coverage is enabled
- UI failures link artifacts and server-side failures expose bounded root-error excerpts to avoid blind reruns
Test Harness
flowchart LR
A["TUnit task"] --> B{"What does the test need?"}
B -->|"Single component only"| C["Plain TUnit test"]
B -->|"HTTP / SignalR / resource graph"| D["Shared Aspire/AppHost fixture"]
B -->|"Host DI / grains / runtime services"| E["Shared Aspire/AppHost fixture + WebApplicationFactory"]
B -->|"Browser automation"| F["Shared Aspire/AppHost fixture + Playwright"]
C & D & E & F --> G["Run focused with --treenode-filter"]
G --> H["Show bounded errors and link artifacts"]
Load References
- references/patterns.md
- references/migration.md
- references/tunit.md
- references/integration-testing.md
Running Tests
TUnit uses Microsoft.Testing.Platform. Use --treenode-filter for filtering, not VSTest --filter. On .NET 10, pass MTP switches directly; older SDKs may require --.
# Run all tests
dotnet test --solution MySolution.sln
# Run one test project
dotnet test --project tests/MyProject.Tests/MyProject.Tests.csproj
# Filter by class
dotnet test --project tests/MyProject.Tests/MyProject.Tests.csproj --treenode-filter "/*/*/CalculatorTests/*"
# Filter by category
dotnet test --project tests/MyProject.Tests/MyProject.Tests.csproj --treenode-filter "/*/*/*/*[Category=Integration]"
# Coverage on Microsoft.Testing.Platform
dotnet test --solution MySolution.sln --coverage --coverage-output coverage.cobertura.xml --coverage-output-format cobertura
# Raw runner help when the repo needs direct TUnit app switches
dotnet run --project tests/MyProject.Tests/MyProject.Tests.csproj -- --help
Filter syntax: /<Assembly>/<Namespace>/<Class>/<Test> with * wildcards. See references/patterns.md for full examples.
Example Requests
- "Run this TUnit project correctly."
- "Fix our TUnit CI command."
- "Add a regression test in TUnit without breaking parallelism."
1---2name: tunit3description: "Write, run, or repair .NET tests that use TUnit. Use when a repo uses `TUnit`, `TUnit.Playwright`, `[Test]`, `[Arguments]`, `ClassDataSource`, `SharedType.PerTestSession`, or Microsoft.Testing.Platform-based execution. Preserve TUnit's parallel-by-default model and constrain only destructive shared-state collisions. DO NOT USE FOR: xUnit projects; MSTest projects."4metadata:5 source: https://skillmd.com/skills/managedcode/tunit6---78# TUnit910## Trigger On1112- the repo uses TUnit13- you need to add, run, debug, or repair TUnit tests14- the repo uses Microsoft.Testing.Platform-based test execution15- the repo uses `ClassDataSource<...>(Shared = SharedType.PerTestSession)`, `TUnit.Playwright`, or `--treenode-filter`1617## Do Not Use For1819- xUnit projects20- MSTest projects21- generic test strategy with no TUnit-specific mechanics2223## Inputs2425- the nearest `AGENTS.md`26- the test project file and package references27- the repo's current TUnit execution command2829## Workflow30311. Confirm the project really uses TUnit and not a different MTP-based framework.322. Read the repo's real `test` command from `AGENTS.md`. If the repo has no explicit command yet, start with `dotnet test PROJECT_OR_SOLUTION`.333. Keep the TUnit execution model intact:34 - tests are source-generated at build time35 - tests run in parallel by default36 - on .NET 10, test modules also run in parallel by default up to `Environment.ProcessorCount`37 - built-in analyzers should remain enabled384. Choose the fixture level deliberately:39 - plain TUnit tests for isolated logic40 - shared AppHost/Aspire fixtures for HTTP, SignalR, SSE, or UI flows41 - `WebApplicationFactory` layered over shared Aspire infra when tests need Host DI services, `IGrainFactory`, or other runtime internals425. Reuse expensive fixtures with `ClassDataSource<Fixture>(Shared = SharedType.PerTestSession)` instead of booting distributed infrastructure per test. Fixture reuse does not serialize consumers: keep the fixture concurrency-safe and give each test unique mutable state.436. Keep tests and test modules parallel. Do not add `--max-parallel-test-modules 1`, `TUNIT_MAX_PARALLEL_TESTS=1`, `[assembly: NotInParallel]`, a class-wide `[NotInParallel]`, or an equivalent global restriction.447. Use keyed `[NotInParallel("collision-domain")]` only on the smallest tests that perform destructive changes to the same shared state and can corrupt one another. A shared read-only fixture, expensive startup, module boundary, or vague CI-stability concern is not a reason to limit parallelism.458. Run the narrowest useful scope first with `dotnet test ... --treenode-filter "..."` on .NET 10. Use the older `--` separator only when the repository is pinned to an SDK that requires it.469. Follow `Test Output Budget`: show bounded root-error evidence and link coverage, Playwright screenshots, and HTML artifacts; never dump host logs.4710. Use `[Test]`, `[Arguments]`, hooks, and dependencies only when they make the scenario clearer, not because the framework allows it.4849## Test Output Budget5051- Keep native runner progress and ANSI enabled (`--progress on --ansi on` for supported MTP/TUnit runners); use a PTY locally. Do not replay progress redraws into model context. Use the detected runner's flags, not MTP switches on VSTest.52- Show warnings and errors plus one final summary (counts, duration, exit code). Configure test-owned console logging at `Warning`; keep Information/Debug/Trace, successful-test output, and expected negative-test noise out of context. Quiet build verbosity alone does not filter application logs.53- On failure, crash, startup error, or timeout, show the failing test/resource, root exception, and relevant stack frames. Deduplicate; cap each diagnostic tool response at 80 lines / 8 KiB, whichever comes first. Never automatically dump stdout/stderr, host logs, browser console history, DOM/HTML, TRX, or crash artifacts.54- Keep necessary diagnostics in size-bounded or rotating artifacts and link them. Search by exact failure/correlation; read bounded excerpts, never whole logs. Capture/filter noisy output before tool delivery, preserve the real exit code, and disclose truncation. Monitor actual activity; silence alone does not prove a hang.5556## Bootstrap When Missing5758If `TUnit` is requested but not configured yet:59601. Detect current state:61 - `rg -n "TUnit|Microsoft\\.Testing\\.Platform" -g '*.csproj' -g 'Directory.Build.*' .`622. Add the minimal package set to the test project:63 - `dotnet add TEST_PROJECT.csproj package TUnit`64 - do not add `Microsoft.NET.Test.Sdk` to a current TUnit project; it selects the VSTest path and conflicts with the normal Microsoft.Testing.Platform setup653. Keep the runner model explicit in `AGENTS.md` and CI:66 - record that the repo uses Microsoft.Testing.Platform-compatible execution for this test project67 - record the exact `dotnet test TEST_PROJECT.csproj` command the repo will use684. Add one small executable test using `[Test]`.695. Run `dotnet test TEST_PROJECT.csproj` and return `status: configured` or `status: improved`.706. If the repo intentionally standardizes on xUnit or MSTest, return `status: not_applicable` unless migration is explicitly requested.7172## Deliver7374- TUnit tests that respect source generation and parallel execution75- commands that work in local and CI runs76- framework-specific verification guidance for the repo77- a fixture strategy that matches the actual test scope: logic-only, AppHost/API, Host DI/grains, or Playwright UI7879## Validate8081- the command matches the repo's TUnit runner style82- focused runs use `--treenode-filter` rather than VSTest-style `--filter`83- .NET 10 runs pass MTP options directly without a `--` separator84- no global or assembly-wide single-thread setting has been introduced85- any keyed non-parallel group is limited to tests with a named destructive shared-state collision86- shared distributed fixtures use `SharedType.PerTestSession` or an equivalent reuse pattern87- fixture and shared infrastructure are safe for concurrent consumers; mutable data is isolated per test88- built-in TUnit analyzers remain active89- coverage tooling matches Microsoft.Testing.Platform if coverage is enabled90- UI failures link artifacts and server-side failures expose bounded root-error excerpts to avoid blind reruns9192## Test Harness9394```mermaid95flowchart LR96 A["TUnit task"] --> B{"What does the test need?"}97 B -->|"Single component only"| C["Plain TUnit test"]98 B -->|"HTTP / SignalR / resource graph"| D["Shared Aspire/AppHost fixture"]99 B -->|"Host DI / grains / runtime services"| E["Shared Aspire/AppHost fixture + WebApplicationFactory"]100 B -->|"Browser automation"| F["Shared Aspire/AppHost fixture + Playwright"]101 C & D & E & F --> G["Run focused with --treenode-filter"]102 G --> H["Show bounded errors and link artifacts"]103```104105## Load References106107- [references/patterns.md](references/patterns.md)108- [references/migration.md](references/migration.md)109- [references/tunit.md](references/tunit.md)110- [references/integration-testing.md](references/integration-testing.md)111112## Running Tests113114TUnit uses Microsoft.Testing.Platform. Use `--treenode-filter` for filtering, not VSTest `--filter`. On .NET 10, pass MTP switches directly; older SDKs may require `--`.115116```bash117# Run all tests118dotnet test --solution MySolution.sln119120# Run one test project121dotnet test --project tests/MyProject.Tests/MyProject.Tests.csproj122123# Filter by class124dotnet test --project tests/MyProject.Tests/MyProject.Tests.csproj --treenode-filter "/*/*/CalculatorTests/*"125126# Filter by category127dotnet test --project tests/MyProject.Tests/MyProject.Tests.csproj --treenode-filter "/*/*/*/*[Category=Integration]"128129# Coverage on Microsoft.Testing.Platform130dotnet test --solution MySolution.sln --coverage --coverage-output coverage.cobertura.xml --coverage-output-format cobertura131132# Raw runner help when the repo needs direct TUnit app switches133dotnet run --project tests/MyProject.Tests/MyProject.Tests.csproj -- --help134```135136Filter syntax: `/<Assembly>/<Namespace>/<Class>/<Test>` with `*` wildcards. See [references/patterns.md](references/patterns.md) for full examples.137138## Example Requests139140- "Run this TUnit project correctly."141- "Fix our TUnit CI command."142- "Add a regression test in TUnit without breaking parallelism."