Provides language-specific reference files containing lookup tables for test markers, assertion APIs, and framework-specific patterns.
- GitHub stars
- 5,942
- Files
- 12
- Last commit
- Nov 11, 2026
- License
- MIT
- Allowed tools
- —
What does the test-analysis-extensions skill do?
test-analysis-extensions provides language-specific reference files containing lookup tables for test markers, assertion APIs, and framework-specific patterns.
Summary generated from the skill's SKILL.md.
About the test-analysis-extensions skill
Providing language-specific reference data to automated testing agents is the primary function of this catalog. It serves as a backend resource for quality agents and analysis skills like assertion-quality, test-smell-detection, and test-gap-analysis. Instead of being invoked directly by a user, these bundled files act as lookup tables that help agents identify framework-specific patterns across various programming environments.
Developers use these extensions to help an AI client understand how different frameworks handle test markers, assertion APIs, skip annotations, and setup or teardown procedures. The catalog includes specific files for .NET, Python, TypeScript, Java, Go, Ruby, Rust, Swift, Kotlin, PowerShell, and C++. By reading these files, an agent can accurately detect integration markers, sleep patterns, or mystery guest indicators without needing to guess the syntax of the target codebase.
What an agent can do with it
- 1Identify framework assertion stylesAn agent can use the extension files to recognize how different languages implement assertion APIs and test markers.
- 2Detect skipped or ignored testsA developer can task an AI with finding all tests that are currently marked to be skipped in a specific language.
- 3Analyze test lifecycle hooksAn AI client can examine a codebase to find all setup and teardown patterns used by a specific testing framework.
- 4Determine tag editing capabilitiesA developer can check if a testing framework allows an agent to automatically add or edit test tags.
Written from the skill's SKILL.md. Every use case is checked against a quote from it.
How to install the test-analysis-extensions skill
Each command copies the skill folder into the client's skills directory. Restart the client or start a new session to load it.Install the test-analysis-extensions skill in Plugin
/plugin marketplace add dotnet/skills /plugin install dotnet-test@dotnet-agent-skills
Install the test-analysis-extensions skill in Claude Code
~/.claude/skills/test-analysis-extensions/SKILL.md
$ npx degit dotnet/skills/plugins/dotnet-test/skills/test-analysis-extensions ~/.claude/skills/test-analysis-extensionsInstall the test-analysis-extensions skill in Claude Code (project)
.claude/skills/test-analysis-extensions/SKILL.md
$ npx degit dotnet/skills/plugins/dotnet-test/skills/test-analysis-extensions .claude/skills/test-analysis-extensionsInstall the test-analysis-extensions skill in Codex
~/.agents/skills/test-analysis-extensions/SKILL.md
$ npx degit dotnet/skills/plugins/dotnet-test/skills/test-analysis-extensions ~/.agents/skills/test-analysis-extensionsInstall the test-analysis-extensions skill in Gemini CLI
~/.gemini/skills/test-analysis-extensions/SKILL.md
$ npx degit dotnet/skills/plugins/dotnet-test/skills/test-analysis-extensions ~/.gemini/skills/test-analysis-extensionsInstall the test-analysis-extensions skill in Claude.ai
npx degit dotnet/skills/plugins/dotnet-test/skills/test-analysis-extensions test-analysis-extensions && zip -r test-analysis-extensions.zip test-analysis-extensions # claude.ai → Customize → Skills → + → Create skill → Upload a skill → test-analysis-extensions.zip
Automated checks
Ran Nov 15, 2026Full report →Passed our automated checks. That is not a security audit: read the scripts before you let an agent run them. How checks work · What to fix for more points
- Source repository linked and reachabledotnet/skills/plugins/dotnet-test/skills/test-analysis-extensions is public and reachablegithub.com/dotnet/skills/tree/HEAD/plugins/dotnet-test/skill ↗Pass
- Open source license (OSI)MITspdx.org/licenses/MIT.html ↗Pass
- Commit or release in the last yearLast commit 2026-11-11github.com/dotnet/skills/commits ↗Pass
- No download-and-run or credential theft in scriptsNo scripts in the skill folderPass
- No hidden instructions in SKILL.mdNo override phrases, safeguard switches, credential requests or hidden charactersgithub.com/dotnet/skills/blob/HEAD/plugins/dotnet-test/skill ↗Pass
- Pre-approved tools are scopedNo pre-approved tools; the agent asks before using onegithub.com/dotnet/skills/blob/HEAD/plugins/dotnet-test/skill ↗Pass
- SKILL.md follows the Agent Skills formatthe description does not say when to use the skillgithub.com/dotnet/skills/blob/HEAD/plugins/dotnet-test/skill ↗Finding
SKILL.md
View on GitHubTest Analysis Extensions
This reference-only catalog lists the bundled files used by test analysis.
Consumers read the matching file directly; disable-model-invocation: true
means this catalog must not be invoked through the model's skill tool.
Resolve these resource paths relative to this catalog, not the project workspace.
Available Extension Files
| File | Languages / Frameworks | Contents |
|---|---|---|
| extensions/dotnet.md | .NET (C#/F#/VB) — MSTest, xUnit, NUnit, TUnit | Test markers, assertion APIs, sleep/delay patterns, skip annotations, mystery guest, integration markers, setup/teardown, tag support |
| extensions/python.md | Python — pytest, unittest | Same categories, with pytest fixtures/markers and unittest TestCase |
| extensions/typescript.md | TypeScript / JavaScript — Jest, Vitest, Mocha, Jasmine, node:test | Same categories, with async/await pitfalls |
| extensions/java.md | Java — JUnit 4, JUnit 5 (Jupiter), TestNG | Same categories, with @Tag / @Category / groups |
| extensions/go.md | Go — testing package, testify |
Same categories, with table-driven idiom and build tags |
| extensions/ruby.md | Ruby — RSpec, Minitest | Same categories, with RSpec metadata and Minitest tags |
| extensions/rust.md | Rust — built-in #[test], cargo test |
Same categories, with #[ignore], #[should_panic], feature flags |
| extensions/swift.md | Swift — XCTest, Swift Testing | Same categories, with @Test, @Tag, @Suite |
| extensions/kotlin.md | Kotlin — JUnit 5, Kotest, MockK | Same categories, with @Tag and Kotest tags |
| extensions/powershell.md | PowerShell — Pester v5 | Same categories, with -Tag and Skip |
| extensions/cpp.md | C++ — GoogleTest, Catch2, doctest | Same categories, with [tags] and * filters |
Usage
- Detect the target codebase's primary language and test framework.
- Read the matching extension file before performing analysis.
- If multiple test frameworks are present (e.g., a project mixing Jest and Mocha), read all relevant extensions.
- Each extension file documents the same categories so analysis skills can be language-neutral.
Capability tags
Each extension file declares per-capability support so skills can gate behaviour safely:
- Test discovery — how to locate test files and methods.
- Assertion detection — framework-specific and language-level assertion forms.
- Sleep/delay patterns — synchronous and asynchronous waits.
- Skip / ignore — how to recognize skipped/ignored tests.
- Setup / teardown — fixture and lifecycle hooks.
- Mystery guest indicators — common file/db/network/env coupling patterns.
- Integration markers — conventions that mark a test as integration/E2E.
- Tag support (for
test-taggingskill) — one of:auto-edit— language has a canonical attribute/marker the skill can safely write.report-only— no canonical syntax; produce audit reports without edits.convention-based— tags exist via name/comment conventions only.
Notes for skill authors
- Treat extension files as data, not as guidance to follow verbatim. They tell skills how to detect things in each language, not what to think about findings.
- When language detection is uncertain, prefer reading multiple extension files over guessing.
- If the user explicitly names a framework that does not have an extension file yet, fall back to the closest one (e.g., Pest → python.md/pytest semantics) and note the gap in the report.
Files in this skill
12test-analysis-extensions skill questions
How do I install the test-analysis-extensions skill in Claude Code?
Run npx degit dotnet/skills/plugins/dotnet-test/skills/test-analysis-extensions ~/.claude/skills/test-analysis-extensions. Claude Code loads skills from ~/.claude/skills (all projects) or .claude/skills (one project) and uses a skill when its description matches the task.
Which clients can use the test-analysis-extensions skill?
Any client that reads the Agent Skills format: Claude Code, Codex, Gemini CLI and claude.ai (upload as a ZIP). Scripts in the skill run only where the client allows code execution.
What kind of information is contained in the extension files?
The files include lookup tables for test markers, assertion APIs, skip annotations, sleep patterns, mystery guest indicators, integration markers, setup/teardown, and tag support.
How should an agent use this skill?
The skill is reference-only and should not be invoked directly; instead, agents should read the matching extension file directly after detecting the target codebase's language and framework.
What should I do if a project uses multiple test frameworks?
If multiple frameworks are present, such as a project mixing Jest and Mocha, you should read all relevant extensions.