Senior QA
alirezarezvani/claude-skills
Generates unit tests, integration tests, and E2E tests for React/Next.js applications.
Defines .NET test strategy and implementation patterns across xUnit v3 (Facts, Theories, fixtures, IAsyncLifetime), integration testing (WebApplicationFactory, Testcontainers), Aspire testing…
Install Dotnet Testing
$ npx skills add novotnyllc/dotnet-artisan --skill dotnet-testing -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install novotnyllc/dotnet-artisan dotnet-testing --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/novotnyllc/dotnet-artisan.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/dotnet-artisan/skills/dotnet-testing .claude/skills/dotnet-testing && rm -rf skills-srcUse ~/.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/
Install the "dotnet-testing" agent skill from https://github.com/novotnyllc/dotnet-artisan/tree/main/plugins/dotnet-artisan/skills/dotnet-testing into .claude/skills/dotnet-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dotnet-testing", 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 install https://github.com/novotnyllc/dotnet-artisan/tree/main/plugins/dotnet-artisan/skills/dotnet-testingType 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.
$ npx skills add novotnyllc/dotnet-artisan --skill dotnet-testing -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install novotnyllc/dotnet-artisan dotnet-testing --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/novotnyllc/dotnet-artisan.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/dotnet-artisan/skills/dotnet-testing .agents/skills/dotnet-testing && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "dotnet-testing" agent skill from https://github.com/novotnyllc/dotnet-artisan/tree/main/plugins/dotnet-artisan/skills/dotnet-testing into .agents/skills/dotnet-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dotnet-testing", 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.
$ npx skills add novotnyllc/dotnet-artisan --skill dotnet-testing -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install novotnyllc/dotnet-artisan dotnet-testing --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/novotnyllc/dotnet-artisan.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/dotnet-artisan/skills/dotnet-testing .cursor/skills/dotnet-testing && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "dotnet-testing" agent skill from https://github.com/novotnyllc/dotnet-artisan/tree/main/plugins/dotnet-artisan/skills/dotnet-testing into .cursor/skills/dotnet-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dotnet-testing", 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 https://github.com/novotnyllc/dotnet-artisan.git --path plugins/dotnet-artisan/skills/dotnet-testing--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add novotnyllc/dotnet-artisan --skill dotnet-testing -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install novotnyllc/dotnet-artisan dotnet-testing --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/novotnyllc/dotnet-artisan.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/dotnet-artisan/skills/dotnet-testing .gemini/skills/dotnet-testing && rm -rf skills-srcUse ~/.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/
Install the "dotnet-testing" agent skill from https://github.com/novotnyllc/dotnet-artisan/tree/main/plugins/dotnet-artisan/skills/dotnet-testing into .gemini/skills/dotnet-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dotnet-testing", 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.
$ gh skill install novotnyllc/dotnet-artisan dotnet-testingInstalls 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).
$ npx skills add novotnyllc/dotnet-artisan --skill dotnet-testing -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/novotnyllc/dotnet-artisan.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/dotnet-artisan/skills/dotnet-testing .github/skills/dotnet-testing && rm -rf skills-srcUse ~/.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/
Install the "dotnet-testing" agent skill from https://github.com/novotnyllc/dotnet-artisan/tree/main/plugins/dotnet-artisan/skills/dotnet-testing into .github/skills/dotnet-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dotnet-testing", 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.
$ npx skills add novotnyllc/dotnet-artisan --skill dotnet-testing -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install novotnyllc/dotnet-artisan dotnet-testing --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/novotnyllc/dotnet-artisan.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/dotnet-artisan/skills/dotnet-testing .opencode/skills/dotnet-testing && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "dotnet-testing" agent skill from https://github.com/novotnyllc/dotnet-artisan/tree/main/plugins/dotnet-artisan/skills/dotnet-testing into .opencode/skills/dotnet-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dotnet-testing", 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-testing- GitHub stars
- 233
- Token cost
- ~972 tokens
- SKILL.md length
- 333 words
- Files
- 15 (incl. references)
- Skills in repo
- 9
- Repo updated
- First seen
- Licence
- MIT
At a glance
Defines .NET test strategy and implementation patterns across xUnit v3 (Facts, Theories, fixtures, IAsyncLifetime), integration testing (WebApplicationFactory, Testcontainers), Aspire testing…
- Production API architecture
- SKILL.md covers Overview, Routing Table, Scope and Out of scope
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- CI workflow authoring
What it does
Dotnet Testing is an agent skill from novotnyllc/dotnet-artisan. 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…
Its SKILL.md is about 970 tokens, which your agent loads only when the skill is triggered. The skill folder holds 16 other files, including reference files (for example `agents/openai.yaml`, `references/add-testing.md` and `references/aot-wasm.md`).
It sits in Testing & QA, covering Integration testing, Test coverage and Unit testing. It works with .NET, Playwright and WebAssembly. The repository describes itself as: Comprehensive .NET development skills for modern C and .NET. The licence is MIT.
When your agent uses it
- Production API architecture
- CI workflow authoring
Example prompts
- “Use the dotnet-testing skill to define .NET test strategy and implementation patterns across xUnit v3 (Facts, Theories, fixtures, IAsyncLifetime)…”
- “/dotnet-testing”
What it can do on your machine
Read from SKILL.md and the folder at commit 3db3ae6. 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.
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 Testing loads about 972 tokens when it runs, and up to ~44k if it reads all its reference files. Until then it costs about 143 tokens; SKILL.md has 333 words of instructions outside code blocks.
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 novotnyllc/dotnet-artisan at commit 3db3ae6, republished under its MIT licence (© novotnyllc). 333 words, ~972 tokens.
Download SKILL.mdSave it as
.claude/skills/dotnet-testing/SKILL.md (or your agent's skills folder). This skill also uses 14 other files; get the full folder from GitHub.- name
- dotnet-testing
- description
- 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.
- license
- MIT
- user-invocable
- false
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
| Topic | Keywords | Description | Companion File |
|---|---|---|---|
| Strategy | unit vs integration vs E2E, test doubles | Unit vs integration vs E2E decision tree, test doubles selection | references/testing-strategy.md |
| xUnit | Facts, Theories, fixtures, parallelism | xUnit v3 Facts, Theories, fixtures, parallelism, IAsyncLifetime | references/xunit.md |
| Integration | WebApplicationFactory, Testcontainers, Aspire | WebApplicationFactory, Testcontainers, Aspire, database fixtures | references/integration-testing.md |
| Snapshot | Verify, scrubbing, API responses | Verify library, scrubbing, custom converters, HTTP response snapshots | references/snapshot-testing.md |
| Playwright | E2E browser, CI caching, trace viewer | Playwright E2E browser automation, CI caching, trace viewer, codegen | references/playwright.md |
| BenchmarkDotNet | microbenchmarks, memory diagnosers | BenchmarkDotNet microbenchmarks, memory diagnosers, baselines | references/benchmarkdotnet.md |
| CI benchmarking | threshold alerts, baseline tracking | CI benchmark regression detection, threshold alerts, baseline tracking | references/ci-benchmarking.md |
| Test quality | Coverlet, Stryker.NET, flaky tests | Coverlet code coverage, Stryker.NET mutation testing, flaky tests | references/test-quality.md |
| Add testing | scaffold xUnit project, coverlet, layout | Scaffold xUnit project, coverlet setup, directory layout | references/add-testing.md |
| Slopwatch | LLM reward hacking detection | Slopwatch CLI for LLM reward hacking detection | references/slopwatch.md |
| AOT WASM | Blazor/Uno WASM AOT, size, lazy loading | Blazor/Uno WASM AOT compilation, size vs speed, lazy loading, Brotli | references/aot-wasm.md |
| UI testing core | page objects, selectors, async waits | Page object model, test selectors, async waits, accessibility testing | references/ui-testing-core.md |
| Aspire testing | DistributedApplicationTestingBuilder, Aspire test host | Aspire test host, service HTTP clients, resource health | references/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
© novotnyllc, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 14 other files (references) in plugins/dotnet-artisan/skills/dotnet-testing of novotnyllc/dotnet-artisan.
- SKILL.md
- agents/openai.yaml
- references/add-testing.md
- references/aot-wasm.md
- references/aspire-testing.md
- references/benchmarkdotnet.md
- references/ci-benchmarking.md
- references/integration-testing.md
- references/playwright.md
- references/slopwatch.md
- references/snapshot-testing.md
- references/test-quality.md
- references/testing-strategy.md
- references/ui-testing-core.md
- references/xunit.md
Open the folder on GitHubat commit 3db3ae6
Compare with similar skills
Dotnet Testing 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Dotnet Testing this skillnovotnyllc/dotnet-artisan | 233 | — | ~972 | Automated safety check: Pass | MIT | |
| Senior QAalirezarezvani/claude-skills | 28k | 1 repos | ~2.1k | Automated safety check: Pass | MIT | |
| Dotnet Testingmacalbert/envilder | 138 | — | ~1.6k | Automated safety check: Pass | MIT | |
| Testing Guidemobazha/mobazha-unified | 165 | — | ~1.7k | Automated safety check: Pass | MPL-2.0 | |
| Testing QAaiskillstore/marketplace | 430 | 3 repos | ~1.2k | Automated safety check: Pass | None | |
| Angular TestingKilo-Org/kilo-marketplace | 189 | — | ~2.9k | Automated safety check: Pass | MIT |
Similar skills
Dotnet Testing
macalbert/envilder
Mandatory testing conventions for .NET (xUnit, AwesomeAssertions).
Testing Guide
mobazha/mobazha-unified
Guide for writing unit tests (Vitest), integration tests, and E2E tests (Playwright) following Mobazha project conventions.
Testing QA
aiskillstore/marketplace
Comprehensive testing and QA workflow covering unit testing, integration testing, E2E testing, browser automation, and quality assurance.
Angular Testing
Kilo-Org/kilo-marketplace
Write unit and integration tests for Angular v20+ applications using Vitest or Jasmine with TestBed and modern testing patterns.
Test Automation
revfactory/harness-100
A full test automation pipeline. An agent skill from revfactory/harness-100.
More from novotnyllc/dotnet-artisan
All 9 skills in this repoDotnet Debugging
novotnyllc/dotnet-artisan
Debugs Windows and Linux/macOS applications (native, .NET/CLR, mixed-mode) with WinDbg MCP (crash dumps, !analyze, !syncblk, !dlk, !runaway, !dumpheap, !gcroot, BSOD), dotnet-dump, lldb with SOS…
Dotnet Tooling
novotnyllc/dotnet-artisan
Manages .NET SDK installation (dotnet-install, workloads), project setup (.slnx, Directory.Build.props, CPM), MSBuild authoring, build optimization, performance (Span, ArrayPool, stackalloc)…
Dotnet API
novotnyllc/dotnet-artisan
Builds ASP.NET Core APIs, EF Core data access, gRPC, SignalR, and backend services with middleware, security (OAuth, JWT, OWASP), resilience, messaging, OpenAPI, .NET Aspire, Semantic Kernel…
Dotnet Csharp
novotnyllc/dotnet-artisan
Baseline C skill loaded for every .NET code path. An agent skill from novotnyllc/dotnet-artisan.
Using Dotnet
novotnyllc/dotnet-artisan
Detects .NET intent for any C, ASP.NET Core, EF Core, Blazor, MAUI, Uno Platform, WPF, WinUI, SignalR, gRPC, xUnit, NuGet, or MSBuild request from prompt keywords and repository signals (.sln…
Dotnet Devops
novotnyllc/dotnet-artisan
Configures .NET CI/CD pipelines (GitHub Actions with setup-dotnet, NuGet cache, reusable workflows; Azure DevOps with DotNetCoreCLI, templates, multi-stage), containerization (multi-stage…
Related
Works with
Categories
Questions about Dotnet Testing
What does Dotnet Testing do?
Defines .NET test strategy and implementation patterns across xUnit v3 (Facts, Theories, fixtures, IAsyncLifetime), integration testing (WebApplicationFactory, Testcontainers), Aspire testing…. Dotnet Testing is an agent skill from novotnyllc/dotnet-artisan.NET), UI testing (page objects, selectors), and AOT WASM test compilation.
When should I use Dotnet Testing?
Dotnet Testing fits situations like: production API architecture; CI workflow authoring.
How do I install Dotnet Testing in Claude Code?
Run `npx skills add novotnyllc/dotnet-artisan --skill dotnet-testing -a claude-code`. Or copy the skill folder (plugins/dotnet-artisan/skills/dotnet-testing in novotnyllc/dotnet-artisan) into .claude/skills/dotnet-testing in your project. Claude Code loads it when a task matches its description.
How do I install Dotnet Testing in Codex?
Run `npx skills add novotnyllc/dotnet-artisan --skill dotnet-testing -a codex`. Or copy the skill folder (plugins/dotnet-artisan/skills/dotnet-testing in novotnyllc/dotnet-artisan) into .agents/skills/dotnet-testing in your project. Codex loads it when a task matches its description.
Can I use Dotnet Testing 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 novotnyllc/dotnet-artisan --skill dotnet-testing -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-testing, .gemini/skills/dotnet-testing, .github/skills/dotnet-testing and .opencode/skills/dotnet-testing in your project.
What does Dotnet Testing need to run?
SKILL.md names no scripts, command-line tools or credentials: Dotnet Testing is instructions for the agent only.
Does Dotnet Testing 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 Testing 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 Testing use?
Dotnet Testing is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Dotnet Testing use?
About 972 tokens (SKILL.md is roughly 3.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 43k tokens, read only when the agent opens those files.
What are the alternatives to Dotnet Testing?
Skills that share tags, products or a category with Dotnet Testing: Senior QA (alirezarezvani/claude-skills, 28k stars), Dotnet Testing (macalbert/envilder, 138 stars), Testing Guide (mobazha/mobazha-unified, 165 stars) and Testing QA (aiskillstore/marketplace, 430 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Dotnet Testing?
novotnyllc (a GitHub organization) maintains it in novotnyllc/dotnet-artisan, which has 233 GitHub stars. The repository holds 9 skills in this directory. The repository was last updated on August 18, 2026.
Source: novotnyllc/dotnet-artisan on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.