Agent skill

Dotnet Test Frameworks

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.

MITAuto-check passedTesting & QA

Install Dotnet Test Frameworks

skills CLI

$ npx skills add runceel/ReactiveProperty --skill dotnet-test-frameworks -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install runceel/ReactiveProperty dotnet-test-frameworks --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/runceel/ReactiveProperty.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/dotnet-test-frameworks .claude/skills/dotnet-test-frameworks && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "dotnet-test-frameworks" agent skill from https://github.com/runceel/ReactiveProperty/tree/main/.agents/skills/dotnet-test-frameworks into .claude/skills/dotnet-test-frameworks/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dotnet-test-frameworks", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/runceel/ReactiveProperty/tree/main/.agents/skills/dotnet-test-frameworks

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add runceel/ReactiveProperty --skill dotnet-test-frameworks -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install runceel/ReactiveProperty dotnet-test-frameworks --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/runceel/ReactiveProperty.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/dotnet-test-frameworks .agents/skills/dotnet-test-frameworks && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "dotnet-test-frameworks" agent skill from https://github.com/runceel/ReactiveProperty/tree/main/.agents/skills/dotnet-test-frameworks into .agents/skills/dotnet-test-frameworks/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dotnet-test-frameworks", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add runceel/ReactiveProperty --skill dotnet-test-frameworks -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install runceel/ReactiveProperty dotnet-test-frameworks --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/runceel/ReactiveProperty.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/dotnet-test-frameworks .cursor/skills/dotnet-test-frameworks && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "dotnet-test-frameworks" agent skill from https://github.com/runceel/ReactiveProperty/tree/main/.agents/skills/dotnet-test-frameworks into .cursor/skills/dotnet-test-frameworks/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dotnet-test-frameworks", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/runceel/ReactiveProperty.git --path .agents/skills/dotnet-test-frameworks

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add runceel/ReactiveProperty --skill dotnet-test-frameworks -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install runceel/ReactiveProperty dotnet-test-frameworks --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/runceel/ReactiveProperty.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/dotnet-test-frameworks .gemini/skills/dotnet-test-frameworks && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "dotnet-test-frameworks" agent skill from https://github.com/runceel/ReactiveProperty/tree/main/.agents/skills/dotnet-test-frameworks into .gemini/skills/dotnet-test-frameworks/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dotnet-test-frameworks", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install runceel/ReactiveProperty dotnet-test-frameworks

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add runceel/ReactiveProperty --skill dotnet-test-frameworks -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/runceel/ReactiveProperty.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/dotnet-test-frameworks .github/skills/dotnet-test-frameworks && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "dotnet-test-frameworks" agent skill from https://github.com/runceel/ReactiveProperty/tree/main/.agents/skills/dotnet-test-frameworks into .github/skills/dotnet-test-frameworks/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dotnet-test-frameworks", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add runceel/ReactiveProperty --skill dotnet-test-frameworks -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install runceel/ReactiveProperty dotnet-test-frameworks --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/runceel/ReactiveProperty.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/dotnet-test-frameworks .opencode/skills/dotnet-test-frameworks && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "dotnet-test-frameworks" agent skill from https://github.com/runceel/ReactiveProperty/tree/main/.agents/skills/dotnet-test-frameworks into .opencode/skills/dotnet-test-frameworks/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dotnet-test-frameworks", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: dotnet-test-frameworks
GitHub stars: 944
Token cost: ~1.4k tokens
SKILL.md length: 293 words
Files: 1
Skills in repo: 12
Repo updated: Aug 31, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

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.

Tasks that involve Unit testing
SKILL.md covers Test File Identification, Assertion APIs by Framework, Sleep/Delay Patterns and Skip/Ignore Annotations, plus 4 more sections
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Dotnet Test Frameworks is an agent skill from runceel/ReactiveProperty. 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.

Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Testing & QA, covering Unit testing. It works with .NET. The repository describes itself as: ReactiveProperty provides MVVM and asynchronous support features under Reactive Extensions. Target frameworks are .NET 6+, .NET Framework 4.7.2 and .NET Standard 2.0. The licence is MIT.

When your agent uses it

Tasks that involve Unit testing

Example prompts

“/dotnet-test-frameworks”

What it can do on your machine

Read from SKILL.md and the folder at commit e7e6474. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are csharp).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Dotnet Test Frameworks loads about 1.4k tokens when it runs. Until then it costs about 107 tokens; SKILL.md has 293 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~107
When it runs · the whole SKILL.md, loaded when a task matches: ~1.4k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from runceel/ReactiveProperty at commit e7e6474, republished under its MIT licence (© runceel). 293 words, ~1,380 tokens.

Download SKILL.mdSave it as .claude/skills/dotnet-test-frameworks/SKILL.md (or your agent's skills folder).

name: dotnet-test-frameworks
description: 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.
metadata.github-path: plugins/dotnet-test/skills/dotnet-test-frameworks
metadata.github-pinned: v1.0.0
metadata.github-ref: refs/tags/v1.0.0
metadata.github-repo: https://github.com/dotnet/skills
metadata.github-tree-sha: e63b5feebdab4ff15d5e7c961b082222bfb74afa
user-invocable: false

.NET Test Framework Reference

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

Test File Identification

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

Assertion APIs by Framework

Category	MSTest	xUnit	NUnit
Equality	`Assert.AreEqual`	`Assert.Equal`	`Assert.That(x, Is.EqualTo(y))`
Boolean	`Assert.IsTrue` / `Assert.IsFalse`	`Assert.True` / `Assert.False`	`Assert.That(x, Is.True)`
Null	`Assert.IsNull` / `Assert.IsNotNull`	`Assert.Null` / `Assert.NotNull`	`Assert.That(x, Is.Null)`
Exception	`Assert.Throws<T>()` / `Assert.ThrowsExactly<T>()`	`Assert.Throws<T>()`	`Assert.That(() => ..., Throws.TypeOf<T>())`
Collection	`CollectionAssert.Contains`	`Assert.Contains`	`Assert.That(col, Has.Member(x))`
String	`StringAssert.Contains`	`Assert.Contains(str, sub)`	`Assert.That(str, Does.Contain(sub))`
Type	`Assert.IsInstanceOfType`	`Assert.IsAssignableFrom`	`Assert.That(x, Is.InstanceOf<T>())`
Inconclusive	`Assert.Inconclusive()`	skip via `[Fact(Skip)]`	`Assert.Inconclusive()`
Fail	`Assert.Fail()`	`Assert.Fail()` (.NET 10+)	`Assert.Fail()`

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

Sleep/Delay Patterns

Pattern	Example
Thread sleep	`Thread.Sleep(2000)`
Task delay	`await Task.Delay(1000)`
SpinWait	`SpinWait.SpinUntil(() => condition, timeout)`

Skip/Ignore Annotations

Framework	Annotation	With 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:

csharp

// 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:

csharp

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

NUnit:

csharp

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 indicator	What to look for
File system	`File.ReadAllText`, `File.Exists`, `File.WriteAllBytes`, `Directory.GetFiles`, `Path.Combine` with hard-coded paths
Database	`SqlConnection`, `DbContext` (without in-memory provider), `SqlCommand`
Network	`HttpClient` without `HttpMessageHandler` override, `WebRequest`, `TcpClient`
Environment	`Environment.GetEnvironmentVariable`, `Environment.CurrentDirectory`
Acceptable	`MemoryStream`, `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

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

Files

Just SKILL.md in .agents/skills/dotnet-test-frameworks of runceel/ReactiveProperty.

Open the folder on GitHubat commit e7e6474

Compare with similar skills

Dotnet Test Frameworks next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Dotnet Test Frameworks compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Dotnet Test Frameworks this skillrunceel/ReactiveProperty	944	—	~1.4k	Automated safety check: Pass	MIT	1 mo ago
New Event Sourceaws/aws-lambda-dotnet	1.7k	—	~3k	Automated safety check: Pass	Apache-2.0	today
ScottPlot Test RunnerScottPlot/ScottPlot	6.8k	—	~308	Automated safety check: Pass	MIT	1 mo ago
Aspire Integration TestingDevBetterCom/DevBetterWeb	157	2 repos	~2.3k	Automated safety check: Pass	None	5 days ago
Vstest Build Testmicrosoft/vstest	969	—	~1.9k	Automated safety check: Pass	MIT	today
Unit TestingOpenCoreMMO/OpenCoreMMO	481	—	~1.6k	Automated safety check: Pass	GPL-3.0	15 days ago

Similar skills

New Event Source
aws/aws-lambda-dotnet
Official
Add a new AWS event source attribute (e.g., Kinesis, Kafka, MQ) to the Lambda .NET Annotations framework, including the attribute class, source generator integration, CloudFormation writer, unit…
1.7k GitHub stars~3k tokensUpdated today
Testing & QAAuto-check passed
ScottPlot Test Runner
ScottPlot/ScottPlot
Run or add ScottPlot 5 tests. Use for unit-test and cookbook-test work; unless explicitly asked otherwise, restrict manual test execution to the Unit Tests…
6.8k GitHub stars~308 tokensUpdated 1 mo ago
Testing & QAAuto-check passed
Aspire Integration Testing
DevBetterCom/DevBetterWeb
Write integration tests using .NET Aspire's testing facilities with xUnit.
157 GitHub starsUsed in 2 repos~2.3k tokens
Testing & QAAuto-check passed
Vstest Build Test
microsoft/vstest
Official
Build, test, and validate changes in the vstest repository. An agent skill from microsoft/vstest.
969 GitHub stars~1.9k tokensUpdated today
Testing & QAAuto-check passed
Unit Testing
OpenCoreMMO/OpenCoreMMO
Write, fix, or review NeoServer unit tests using xUnit and FluentAssertions.
481 GitHub stars~1.6k tokensUpdated 15 days ago
Testing & QAAuto-check passed
Akka.NET Testing Patterns
Aaronontheweb/dotnet-skills
Shows how to test Akka.NET actors with Akka.Hosting.TestKit: swapping services for fakes, using TestProbes, and checking persistence, plus when the older TestKit still fits.
1.2k GitHub starsUsed in 1 repo~2.4k tokens
Testing & QAAuto-check passed

Questions about Dotnet Test Frameworks

What does Dotnet Test Frameworks do?

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. Dotnet Test Frameworks is an agent skill from runceel/ReactiveProperty.NET test framework detection patterns, assertion APIs, skip annotations, setup/teardown methods, and common test smell indicators across MSTest, xUnit, NUnit, and TUnit.

When should I use Dotnet Test Frameworks?

Dotnet Test Frameworks fits situations like: tasks that involve Unit testing.

How do I install Dotnet Test Frameworks in Claude Code?

Run `npx skills add runceel/ReactiveProperty --skill dotnet-test-frameworks -a claude-code`. Or copy the skill folder (.agents/skills/dotnet-test-frameworks in runceel/ReactiveProperty) into .claude/skills/dotnet-test-frameworks in your project. Claude Code loads it when a task matches its description.

How do I install Dotnet Test Frameworks in Codex?

Run `npx skills add runceel/ReactiveProperty --skill dotnet-test-frameworks -a codex`. Or copy the skill folder (.agents/skills/dotnet-test-frameworks in runceel/ReactiveProperty) into .agents/skills/dotnet-test-frameworks in your project. Codex loads it when a task matches its description.

Can I use Dotnet Test Frameworks in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add runceel/ReactiveProperty --skill dotnet-test-frameworks -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/dotnet-test-frameworks, .gemini/skills/dotnet-test-frameworks, .github/skills/dotnet-test-frameworks and .opencode/skills/dotnet-test-frameworks in your project.

What does Dotnet Test Frameworks need to run?

SKILL.md names no scripts, command-line tools or credentials: Dotnet Test Frameworks is instructions for the agent only.

Does Dotnet Test Frameworks access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Dotnet Test Frameworks safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Dotnet Test Frameworks use?

Dotnet Test Frameworks is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Dotnet Test Frameworks use?

About 1.4k tokens (SKILL.md is roughly 5.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Dotnet Test Frameworks?

Skills that share tags, products or a category with Dotnet Test Frameworks: New Event Source (aws/aws-lambda-dotnet, 1.7k stars), ScottPlot Test Runner (ScottPlot/ScottPlot, 6.8k stars), Aspire Integration Testing (DevBetterCom/DevBetterWeb, 157 stars) and Vstest Build Test (microsoft/vstest, 969 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Dotnet Test Frameworks?

runceel (a GitHub user) maintains it in runceel/ReactiveProperty, which has 944 GitHub stars. The repository holds 12 skills in this directory. The repository was last updated on August 31, 2026.

Source: runceel/ReactiveProperty on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Dotnet Test Frameworks

Facts

At a glance

What it does

When your agent uses it

Example prompts

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

.NET Test Framework Reference

Test File Identification

Assertion APIs by Framework

Sleep/Delay Patterns

Skip/Ignore Annotations

Exception Handling — Idiomatic Alternatives

Mystery Guest — Common .NET Patterns

Integration Test Markers

Setup/Teardown Methods

Files

Compare with similar skills

Similar skills

More from runceel/ReactiveProperty

Related

Questions about Dotnet Test Frameworks