CtrlK
BlogDocsLog inGet started
Tessl Logo

testland/dotnet-unit-tests

.NET unit testing (C# / F# / VB.NET) with xUnit.net as the primary framework - `[Fact]` single tests, `[Theory]` + `[InlineData]`/`[ClassData]`/`[MemberData]` parametrization, class and collection fixtures (`IClassFixture` / `ICollectionFixture`), parallel-execution config, `ITestOutputHelper` output, skip/traits filtering, and `dotnet test` CI with trx + coverage. Includes framework choice (xUnit for new projects; match an existing NUnit/MSTest convention detected from csproj PackageReferences; legacy .NET Framework 4.x → NUnit or MSTest) and test-authoring conventions (AAA mapping, argument-order traps, no fabricated methods, no smoke asserts). References cover NUnit (`[TestCase]`, constraint-model `Assert.That`), MSTest (`[TestClass]` / `[DataRow]` / TestContext), and the FluentAssertions `.Should()` catalog including the v8 commercial-license change. Use for any .NET unit-test task: choosing or configuring a framework, writing or parameterizing tests, fixtures, or wiring CI.

75

Quality

94%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Overview
Quality
Evals
Security
Files

Quality

Content

92%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

Well-structured, executable, and appropriately split across one-level-deep reference files, with validation checkpoints and an anti-pattern recovery table. Minor tightening possible in the Overview and lifecycle prose.

DimensionReasoningScore

Conciseness

Mostly lean and assumes Claude's knowledge, but the Overview and a few explanatory clauses (e.g. 'constructor as setup' lifecycle prose) could be trimmed slightly without losing clarity.

4 / 5

Actionability

Fully executable, copy-paste-ready code across install, first test, parametrization, fixtures, output, and CI YAML; common cases are covered with real commands and config.

5 / 5

Workflow Clarity

A clear Step 1-7 sequence with an explicit verification checkpoint and debug loop in Step 2 ('verify the run reports Passed!... if it discovers 0 tests, confirm...') plus an anti-pattern recovery table.

5 / 5

Progressive Disclosure

Clear overview with well-signaled, one-level-deep references to real files (references/nunit.md, mstest.md, fluentassertions.md); cross-skill pointers (test-code-conventions, synthetic-data-toolkit) are appropriately routed out of the main body.

5 / 5

Total

19

/

20

Passed

Description

92%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A highly specific, third-person description with an explicit 'Use for...' trigger and broad concrete coverage of frameworks and attributes. Slightly padded by the long attribute enumeration and could add common file-extension synonyms.

DimensionReasoningScore

Specificity

Lists multiple concrete actions and a comprehensive attribute catalog ('[Fact] single tests', '[Theory] + [InlineData]/[ClassData]/[MemberData] parametrization', 'IClassFixture / ICollectionFixture', 'ITestOutputHelper output', 'dotnet test CI with trx + coverage').

5 / 5

Completeness

Explicitly answers both 'what' (the enumerated capabilities) and 'when' via the closing 'Use for any .NET unit-test task: ...' trigger clause with concrete trigger phrases.

5 / 5

Trigger Term Quality

Good natural triggers ('choosing or configuring a framework', 'writing or parameterizing tests, fixtures, or wiring CI') plus framework names, but misses common synonyms/extensions like .csproj or .dll that a user might mention.

4 / 5

Distinctiveness Conflict Risk

A clear .NET unit-testing niche with framework-specific triggers; the scope (xUnit/NUnit/MSTest/FluentAssertions) is distinct and unlikely to fire for unrelated skills.

5 / 5

Total

19

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Reviewed

Table of Contents