csharp-tunit
Get best practices for TUnit unit testing, including data-driven tests
Profile →npx skills add github/awesome-copilot --skill csharp-tunit --agent copilot
Same command for any agent — swap --agent for claude-code, codex, cursor.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# TUnit Best Practices Your goal is to help me write effective unit tests with TUnit, covering both standard and data-driven testing approaches. ## Project Setup - Use a separate test project with naming convention `[ProjectName].Tests` - Reference TUnit package and TUnit.Assertions for fluent assertions - Create test classes that match the classes being tested (e.g., `CalculatorTests` for `Calculator`) - Use .NET SDK test commands: `dotnet test` for running tests - TUnit requires .NET 8.0 or higher ## Test Structure - No test class attributes required (like xUnit/NUnit) - Use `[Test]` attribute for test methods (not `[Fact]` like xUnit) - Follow the Arrange-Act-Assert (AAA) pattern - Name tests using the pattern `MethodName_Scenario_ExpectedBehavior` - Use lifecycle hooks: `[Before(Test)]` for setup and `[After(Test)]` for teardown - Use `[Before(Class)]` and `[After(Class)]` for shared context between tests in a class - Use `[Before(Assembly)]` and `[After(Assembly)]` for shared context across test classes - TUnit supports advanced lifecycle hooks like `[Before(TestSession)]` and `[After(TestSession)]` ## Standard Tests - Keep tests focused on a single behavior - Avoid testing mu
- Project Setup
- Test Structure
- Standard Tests
- Data-Driven Tests
- Assertions
- Advanced Features
- Test Organization
- Performance and Parallel Execution
- Migration from xUnit
What does the csharp-tunit skill do?
Get best practices for TUnit unit testing, including data-driven tests
How do I install it?
Run `npx skills add github/awesome-copilot --skill csharp-tunit --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From github/awesome-copilot, a repository with 37,432 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.