Dotnet Testing logo

Dotnet Testing

Organization
novotnyllc
dotnet-testing

Defines .NET test strategy and implementation patterns across xUnit v3 (Facts, Theories, fixtures, IAsyncLifetime), integration testing (WebApplicationFactory, Testcontainers), Aspire testing (DistributedApplicationTestingBuilder), snapshot testing (Verify, scrubbing), Playwright E2E browser automation, BenchmarkDotNet microbenchmarks, code coverage (Coverlet), mutation testing (Stryker.NET), UI testing (page objects, selectors), and AOT WASM test compilation. Spans 13 topic areas. Do not use for production API architecture or CI workflow authoring.

Overview

Publishernovotnyllc
Repositorydotnet-artisan
Skill namedotnet-testing
Stars
235
Forks
14
Bundled files
14
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 14 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by novotnyllc on GitHub. Read the source before you install it.

Installation

Install the Dotnet Testing AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/novotnyllc/dotnet-artisan/tree/main/plugins/dotnet-artisan/skills/dotnet-testing
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/novotnyllc/dotnet-artisan.git /tmp/dotnet-artisan
mkdir -p .claude/skills
cp -r /tmp/dotnet-artisan/plugins/dotnet-artisan/skills/dotnet-testing .claude/skills/dotnet-testing
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Dotnet Testing in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Dotnet Testing on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Dotnet Testing is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

dotnet-testing

Overview

Testing strategy, frameworks, and quality tooling for .NET applications. This consolidated skill spans 13 topic areas. Load the appropriate companion file from references/ based on the routing table below.

Baseline dependency: references/testing-strategy.md defines the unit vs integration vs E2E decision tree and test doubles selection that inform all testing decisions. Load it by default whenever a testing approach needs to be chosen.

Most-shared companion: references/xunit.md covers xUnit v3 framework features used by integration, snapshot, and UI testing companions.

Routing Table

TopicKeywordsDescriptionCompanion File
Strategyunit vs integration vs E2E, test doublesUnit vs integration vs E2E decision tree, test doubles selectionreferences/testing-strategy.md
xUnitFacts, Theories, fixtures, parallelismxUnit v3 Facts, Theories, fixtures, parallelism, IAsyncLifetimereferences/xunit.md
IntegrationWebApplicationFactory, Testcontainers, AspireWebApplicationFactory, Testcontainers, Aspire, database fixturesreferences/integration-testing.md
SnapshotVerify, scrubbing, API responsesVerify library, scrubbing, custom converters, HTTP response snapshotsreferences/snapshot-testing.md
PlaywrightE2E browser, CI caching, trace viewerPlaywright E2E browser automation, CI caching, trace viewer, codegenreferences/playwright.md
BenchmarkDotNetmicrobenchmarks, memory diagnosersBenchmarkDotNet microbenchmarks, memory diagnosers, baselinesreferences/benchmarkdotnet.md
CI benchmarkingthreshold alerts, baseline trackingCI benchmark regression detection, threshold alerts, baseline trackingreferences/ci-benchmarking.md
Test qualityCoverlet, Stryker.NET, flaky testsCoverlet code coverage, Stryker.NET mutation testing, flaky testsreferences/test-quality.md
Add testingscaffold xUnit project, coverlet, layoutScaffold xUnit project, coverlet setup, directory layoutreferences/add-testing.md
SlopwatchLLM reward hacking detectionSlopwatch CLI for LLM reward hacking detectionreferences/slopwatch.md
AOT WASMBlazor/Uno WASM AOT, size, lazy loadingBlazor/Uno WASM AOT compilation, size vs speed, lazy loading, Brotlireferences/aot-wasm.md
UI testing corepage objects, selectors, async waitsPage object model, test selectors, async waits, accessibility testingreferences/ui-testing-core.md
Aspire testingDistributedApplicationTestingBuilder, Aspire test hostAspire test host, service HTTP clients, resource healthreferences/aspire-testing.md

Scope

  • Test strategy and architecture (unit, integration, E2E)
  • xUnit v3 test authoring
  • Integration testing (WebApplicationFactory, Testcontainers)
  • E2E browser testing (Playwright)
  • Snapshot testing (Verify)
  • Benchmarking (BenchmarkDotNet, CI gating)
  • Quality (coverage, mutation testing)
  • Cross-framework UI testing patterns
  • Test scaffolding

Out of scope

  • UI framework-specific testing (bUnit, Appium) -> dotnet-ui
  • CI/CD pipeline configuration -> dotnet-devops
  • Performance profiling -> dotnet-tooling

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Dotnet Testing AI skill do?

Defines .NET test strategy and implementation patterns across xUnit v3 (Facts, Theories, fixtures, IAsyncLifetime), integration testing (WebApplicationFactory, Testcontainers), Aspire testing (DistributedApplicationTestingBuilder), snapshot testing (Verify, scrubbing), Playwright E2E browser automation, BenchmarkDotNet microbenchmarks, code coverage (Coverlet), mutation testing (Stryker.NET), UI testing (page objects, selectors), and AOT WASM test compilation. Spans 13 topic areas. Do not use for production API architecture or CI workflow authoring.

Why use Dotnet Testing on TypingMind?

Because you install it once and use it with any model. Dotnet Testing is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Dotnet Testing in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/novotnyllc/dotnet-artisan/tree/main/plugins/dotnet-artisan/skills/dotnet-testing. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Dotnet Testing?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Dotnet Testing?

As many as you like. As long as a model supports skills, you can use Dotnet Testing with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Dotnet Testing AI skill free?

Yes. It is published on GitHub by novotnyllc under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇