test-analysis-extensions

Provides language-specific test framework reference files for polyglot test analysis skills.

Updated Jul 12, 2026
One-click install
npx skills add https://github.com/Patrick-Rex/DotNetTechSamples --skill test-analysis-extensions-patrick-rex
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test-analysis-extensions
Source: https://github.com/Patrick-Rex/DotNetTechSamples/tree/main/.agents/plugins/dotnet-test/skills/test-analysis-extensions
Command: npx skills add https://github.com/Patrick-Rex/DotNetTechSamples --skill test-analysis-extensions-patrick-rex

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Test analysis skills need framework-specific lookup tables (assertion APIs, skip annotations, sleep patterns, tag syntax) that vary across languages, and this Skill centralizes those per-language reference files so analysis stays accurate across .NET, Python, TypeScript, Java, Go, Ruby, Rust, Swift, Kotlin, PowerShell, and C++. ## Core Features & Use Cases - Per-language extension files: Eleven reference files covering frameworks such as MSTest, xUnit, NUnit, TUnit, pytest, Jest, Vitest, JUnit, TestNG, RSpec, GoogleTest, and Pester. - Uniform capability categories: Each file documents test discovery, assertion detection, sleep/delay patterns, skip annotations, setup/teardown, mystery guest indicators, integration markers, and tag support. - Tag support gating: Declares auto-edit, report-only, or convention-based tagging capability per language so the test-tagging skill behaves safely. - Use Case: When auditing a mixed .NET and TypeScript repository, the test-quality-auditor agent reads dotnet.md and typescript.md to detect unawaited TUnit assertions and floating promises with framework-correct rules. ## Quick Start Ask the test-quality-auditor agent to analyze your test suite and it will load the extension file matching your language and test framework.

Frequently Asked Questions about test-analysis-extensions

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I analyze test quality across multiple programming languages?

Use the polyglot test analysis skills, which load a per-language extension file from this skill before auditing. Each extension documents framework-specific assertion APIs, skip annotations, and smell indicators so detection rules stay accurate for that language.

What test frameworks are supported for test smell detection?

Extensions cover MSTest, xUnit, NUnit, TUnit, pytest, unittest, Jest, Vitest, Mocha, JUnit 4/5, TestNG, Go testing with testify, RSpec, Minitest, Rust built-in tests, XCTest, Swift Testing, Kotest, Pester, GoogleTest, Catch2, and doctest.

Can test tagging be applied automatically in every language?

No. Each extension declares a tag support mode: auto-edit for languages with canonical attributes like .NET, Java, Python, and Swift Testing; report-only for Go, TypeScript, and Rust where no standard tag syntax exists; convention-based where tags rely on naming patterns.

Why are bare assert statements not flagged in pytest analysis?

Bare assert is the canonical pytest idiom and produces rich failure diffs through assertion rewriting. The python extension file explicitly calibrates the analysis skills so they do not flag it as a missing-framework-API smell.

What happens if my test framework has no extension file?

The skill instructs consumers to fall back to the closest matching extension, such as using pytest semantics for Pest, and to note the gap in the audit report rather than guessing framework rules.