OpenParable
Skip to content
← Back to skills

Dotnet Test Frameworks

Testing & Quality
dotnet-test-frameworks

Dotnet Test Frameworks is an Agent Skill for testing & quality published in the runceel/ReactiveProperty repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Reference data for .NET test framework detection patterns, assertion APIs, skip annotations, setup/teardown methods, and common test smell indicators across MSTest, xUnit, NUnit, and TUnit. DO NOT USE directly — loaded by test analysis skills (test-anti-patterns, exp-test-smell-detection, exp-assertion-quality, exp-test-maintainability, exp-test-tagging) when they need framework-specific lookup tables.

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/runceel/ReactiveProperty/blob/HEAD/.agents/skills/dotnet-test-frameworks/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/dotnet-test-frameworks, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

.NET Test Framework Reference

Language-specific detection patterns for .NET test frameworks (MSTest, xUnit, NUnit, TUnit).

Test File Identification

FrameworkTest class markersTest method markers
MSTest[TestClass][TestMethod], [DataTestMethod]
xUnit(none — convention-based)[Fact], [Theory]
NUnit[TestFixture][Test], [TestCase], [TestCaseSource]
TUnit[ClassDataSource][Test]

Assertion APIs by Framework

CategoryMSTestxUnitNUnit
EqualityAssert.AreEqualAssert.EqualAssert.That(x, Is.EqualTo(y))
BooleanAssert.IsTrue / Assert.IsFalseAssert.True / Assert.FalseAssert.That(x, Is.True)
NullAssert.IsNull / Assert.IsNotNullAssert.Null / Assert.NotNullAssert.That(x, Is.Null)
ExceptionAssert.Throws<T>() / Assert.ThrowsExactly<T>()Assert.Throws<T>()Assert.That(() => ..., Throws.TypeOf<T>())
CollectionCollectionAssert.ContainsAssert.ContainsAssert.That(col, Has.Member(x))
StringStringAssert.ContainsAssert.Contains(str, sub)Assert.That(str, Does.Contain(sub))
TypeAssert.IsInstanceOfTypeAssert.IsAssignableFromAssert.That(x, Is.InstanceOf<T>())
InconclusiveAssert.Inconclusive()skip via [Fact(Skip)]Assert.Inconclusive()
FailAssert.Fail()Assert.Fail() (.NET 10+)Assert.Fail()

Third-party assertion libraries: Should* (Shouldly), .Should() (FluentAssertions / AwesomeAssertions), Verify() (Verify).

Sleep/Delay Patterns

PatternExample
Thread sleepThread.Sleep(2000)
Task delayawait Task.Delay(1000)
SpinWaitSpinWait.SpinUntil(() => condition, timeout)

Skip/Ignore Annotations

FrameworkAnnotationWith reason
MSTest[Ignore][Ignore("reason")]
xUnit[Fact(Skip = "reason")](reason is required)
NUnit[Ignore("reason")](reason is required)
TUnit[Skip("reason")](reason is required)
Conditional#if false / #if NEVER(no reason possible)

Exception Handling — Idiomatic Alternatives

When a test uses try/catch to verify exceptions, suggest the framework-native alternative:

MSTest:

// Instead of try/catch (matches exact type):
var ex = Assert.ThrowsExactly<InvalidOperationException>(
    () => processor.ProcessOrder(emptyOrder));
Assert.AreEqual("Order must contain at least one item", ex.Message);

// Or (also matches derived types):
var ex = Assert.Throws<InvalidOperationException>(
    () => processor.ProcessOrder(emptyOrder));
Assert.AreEqual("Order must contain at least one item", ex.Message);

xUnit:

var ex = Assert.Throws<InvalidOperationException>(
    () => processor.ProcessOrder(emptyOrder));
Assert.Equal("Order must contain at least one item", ex.Message);

NUnit:

var ex = Assert.Throws<InvalidOperationException>(
    () => processor.ProcessOrder(emptyOrder));
Assert.That(ex.Message, Is.EqualTo("Order must contain at least one item"));

Mystery Guest — Common .NET Patterns

Smell indicatorWhat to look for
File systemFile.ReadAllText, File.Exists, File.WriteAllBytes, Directory.GetFiles, Path.Combine with hard-coded paths
DatabaseSqlConnection, DbContext (without in-memory provider), SqlCommand
NetworkHttpClient without HttpMessageHandler override, WebRequest, TcpClient
EnvironmentEnvironment.GetEnvironmentVariable, Environment.CurrentDirectory
AcceptableMemoryStream, StringReader, InMemory database providers, custom DelegatingHandler

Integration Test Markers

Recognize these as integration tests (adjust smell severity accordingly):

  • Class name contains Integration, E2E, EndToEnd, or Acceptance
  • [TestCategory("Integration")] (MSTest)
  • [Trait("Category", "Integration")] (xUnit)
  • [Category("Integration")] (NUnit)
  • Project name ending in .IntegrationTests or .E2ETests

Setup/Teardown Methods

FrameworkSetupTeardown
MSTest[TestInitialize] or constructor[TestCleanup] or IDisposable.Dispose / IAsyncDisposable.DisposeAsync
xUnitconstructorIDisposable.Dispose / IAsyncDisposable.DisposeAsync
NUnit[SetUp][TearDown]
MSTest (class)[ClassInitialize][ClassCleanup]
NUnit (class)[OneTimeSetUp][OneTimeTearDown]
xUnit (class)IClassFixture<T>fixture's Dispose