Run any Skill in Manus with one click

code-testing-extensions

Provides file paths to language-specific extension files for the code-testing pipeline. Call this skill to discover available extension guidance files (e.g., dotnet.md for .NET, cpp.md for C++). Do not use directly — invoked by code-testing agents and skills that need language-specific references.

Run Skill in Manus

Overview

Install command

npx skills add https://github.com/dotnet/skills --skill code-testing-extensions

Copy and paste this command into Claude Code to install the skill

Source

dotnet/skills

Stars3,257

Forks242

UpdatedJune 2, 2026 at 13:42

File Explorer

17 files

SKILL.md

readonly

name	code-testing-extensions
description	Provides file paths to language-specific extension files for the code-testing pipeline. Call this skill to discover available extension guidance files (e.g., dotnet.md for .NET, cpp.md for C++). Do not use directly — invoked by code-testing agents and skills that need language-specific references.
user-invocable	false
license	MIT

Code Testing Extensions

This skill provides access to language-specific guidance files used by the code-testing pipeline. Call this skill to get the file paths, then read the relevant file for your target language.

Available Extension Files

File	Language	Contents
extensions/dotnet.md	.NET (C#/F#/VB)	Build commands, test commands, project reference validation, common CS error codes, MSTest template
extensions/python.md	Python	Framework-adaptive test commands (pytest, custom runners), project layout detection, mocking guidelines, common errors
extensions/typescript.md	TypeScript/JavaScript	Build/test commands (Jest/Vitest/Mocha), framework detection, mocking, TS-specific considerations
extensions/powershell.md	PowerShell	Test commands (Pester v5), module import patterns, discovery/run pitfalls, mocking, common errors
extensions/cpp.md	C++	Testing internals with friend declarations
extensions/go.md	Go	`go test` commands, table-driven tests, integration vs unit layout, mocking via interfaces, common errors
extensions/java.md	Java	Maven/Gradle commands, JUnit 4/5 and TestNG detection, Mockito, Spring Boot slices, common errors
extensions/rust.md	Rust	`cargo test` commands, unit vs integration vs doc tests, features, async test harnesses, common errors
extensions/ruby.md	Ruby	RSpec and Minitest commands, Bundler usage, Rails specifics, mocking patterns, common errors
extensions/swift.md	Swift	SPM and Xcode test commands, XCTest vs Swift Testing, `@testable import`, async/throws tests, common errors
extensions/kotlin.md	Kotlin	Gradle commands, JUnit/Kotest detection, MockK, coroutines test, KMP and Android specifics, common errors
extensions/dotnet-examples.md	.NET (C#/F#/VB)	Concrete pipeline examples: sample research output, plan, generated tests, fix cycles, final report
extensions/python-examples.md	Python	Concrete pipeline examples (pytest): research, plan, generated test file, fix cycles, final report
extensions/typescript-examples.md	TypeScript/JavaScript	Concrete pipeline examples (Vitest, applicable to Jest): research, plan, generated test file, fix cycles, final report
extensions/go-examples.md	Go	Concrete pipeline examples (standard `testing`): research, plan, table-driven test file, fix cycles, final report
extensions/java-examples.md	Java	Concrete pipeline examples (JUnit 5 + Mockito on Maven): research, plan, generated test file, fix cycles, final report

Usage

Read the appropriate extension file for the target language before writing test code. When an <language>-examples.md file exists for the target language, read it alongside the base extension to see a concrete end-to-end pipeline walkthrough (research output, plan, generated tests, fix cycles, final report).

More from this repository

same repository

code-testing-agent

dotnet/skills

Generates and writes new unit tests for any programming language using a Research-Plan-Implement pipeline. Use when asked to generate tests, write unit tests, add tests, improve test coverage, create test project, achieve high coverage, comprehensive tests, or asked to scaffold a new test project for an app, service, or library. Supports C#, TypeScript, JavaScript, Python, Go, Rust, Java, and more. Orchestrates the code-testing-generator sub-agent through research, planning, and implementation phases so tests compile, pass, and follow project conventions. DO NOT USE FOR: running existing tests or test filters (use run-tests); diagnosing coverage plateaus or project-wide coverage/CRAP analysis without writing tests (use coverage-analysis); targeted method/class CRAP scores (use crap-score); MSTest assertion guidance, MSTest test pattern modernization, or fixing existing MSTest test code (use writing-mstest-tests).

2026-06-023.3k

assertion-quality

dotnet/skills

Analyzes the variety and depth of assertions across test suites in any language. Use when the user asks to evaluate assertion quality, find shallow testing, identify assertion-free tests (no assertions or only trivial ones like Assert.IsNotNull / expect(x).toBeTruthy() / assert x is not None), flag self-referential or tautological assertions (output equals input on identity/round-trip operations), measure assertion coverage diversity, or audit whether tests verify different facets of correctness. Produces metrics and actionable recommendations. Polyglot: .NET (MSTest/xUnit/NUnit/TUnit), Python (pytest/unittest), TS/JS (Jest/Vitest/Mocha/Jasmine/node:test), Java (JUnit/TestNG), Go, Ruby (RSpec/Minitest), Rust, Swift (XCTest/Swift Testing), Kotlin (JUnit/Kotest), PowerShell (Pester), C++ (GoogleTest/Catch2/doctest). DO NOT USE FOR: writing new tests (use code-testing-agent, or writing-mstest-tests for MSTest), anti-patterns like flakiness or duplication (use test-anti-patterns), fixing assertions.

2026-06-013.3k

test-analysis-extensions

dotnet/skills

Provides file paths to language-specific reference files for the test ANALYSIS skills (assertion-quality, test-anti-patterns, test-gap-analysis, test-smell-detection, test-tagging). Call this skill to discover available extension files (e.g., dotnet.md for .NET/MSTest/xUnit/NUnit/TUnit, python.md for pytest/unittest, typescript.md for Jest/Vitest/Mocha, java.md for JUnit/TestNG, etc.). Do not use directly — invoked by the test-quality-auditor agent and polyglot analysis skills that need framework-specific lookup tables (test markers, assertion APIs, skip annotations, sleep patterns, mystery guest indicators, integration markers, setup/teardown, tag-support capability).

2026-06-013.3k

test-anti-patterns

dotnet/skills

Audits existing test code in any language for anti-patterns and quality issues — produces a severity-ranked report (Critical / Warning / Info) with concrete code-level fixes. Polyglot: .NET (MSTest/xUnit/NUnit/ TUnit), Python (pytest/unittest), TS/JS (Jest/Vitest/Mocha/node:test), Java (JUnit/TestNG), Go, Ruby (RSpec/Minitest), Rust, Swift, Kotlin (JUnit/Kotest), PowerShell (Pester), C++ (GoogleTest/Catch2). INVOKE when asked to audit, review, rank, or find problems in existing tests — "audit my tests", "test smell audit", "rank by severity", tests that pass but verify nothing, no/missing assertions, swallowed exceptions, always-true / self-comparing / tautological assertions, broad exception types, flakiness (sleep/Date.now/time.sleep), ordering dependency, shared global state, duplicated tests, magic values, missing await on async assertions. DO NOT USE FOR: writing new tests (use code-testing-agent, or writing-mstest-tests for MSTest); running tests (use run-tests); framework migration.

2026-06-013.3k

test-gap-analysis

dotnet/skills

Performs pseudo-mutation analysis on production code in any language to find gaps in existing test suites. Use when the user asks to find weak tests, discover untested edge cases, check if tests would catch a bug, or evaluate test effectiveness through mutation-style reasoning. Analyzes production code for mutation points (boundaries, boolean flips, null/None/nil returns, exception/error removal, arithmetic changes) and checks whether tests would detect each mutation. Polyglot: .NET (MSTest/xUnit/NUnit/TUnit), Python (pytest/unittest), TS/JS (Jest/Vitest/Mocha/node:test), Java (JUnit/TestNG), Go, Ruby (RSpec/Minitest), Rust, Swift, Kotlin (JUnit/Kotest), PowerShell (Pester), C++ (GoogleTest/Catch2). DO NOT USE FOR: writing new tests (use code-testing-agent, or writing-mstest-tests for MSTest), detecting anti-patterns (use test-anti-patterns), measuring assertion diversity (use assertion-quality), or running actual mutation testing tools (Stryker, mutmut, PIT, cargo-mutants).

2026-06-013.3k

test-smell-detection

dotnet/skills

Deep-dive audit using the full testsmells.org 19-smell academic catalog for tests in any language. Every finding maps to a named, citable smell from the research literature (Assertion Roulette, Duplicate Assert, Mystery Guest, Eager Test, Sensitive Equality, Conditional Test Logic, Sleepy Test, Magic Number Test, etc.) with research-backed severity. Polyglot: .NET (MSTest/xUnit/NUnit/TUnit), Python (pytest/unittest), TS/JS (Jest/Vitest/Mocha/node:test), Java (JUnit/TestNG), Go, Ruby (RSpec/Minitest), Rust, Swift, Kotlin (JUnit/Kotest), PowerShell (Pester), C++ (GoogleTest/Catch2). INVOKE ONLY when explicitly asked for the testsmells.org 19-smell academic catalog or citable smell names from the literature. DO NOT USE FOR: general or pragmatic audits — use test-anti-patterns; writing new tests (use code-testing-agent, or writing-mstest-tests for MSTest); running tests (use run-tests); framework migration.

2026-06-013.3k

Source

dotnet

dotnet/skills

View GitHub Repository View Creator Repositories

Install command

Download

Run Skill in Manus

Useful forSOC

Software Quality Assurance Analysts and TestersComputer and Mathematical Occupations15-1253L4

name	code-testing-extensions
description	Provides file paths to language-specific extension files for the code-testing pipeline. Call this skill to discover available extension guidance files (e.g., dotnet.md for .NET, cpp.md for C++). Do not use directly — invoked by code-testing agents and skills that need language-specific references.
user-invocable	false
license	MIT

Code Testing Extensions

This skill provides access to language-specific guidance files used by the code-testing pipeline. Call this skill to get the file paths, then read the relevant file for your target language.

Available Extension Files

File	Language	Contents
extensions/dotnet.md	.NET (C#/F#/VB)	Build commands, test commands, project reference validation, common CS error codes, MSTest template
extensions/python.md	Python	Framework-adaptive test commands (pytest, custom runners), project layout detection, mocking guidelines, common errors
extensions/typescript.md	TypeScript/JavaScript	Build/test commands (Jest/Vitest/Mocha), framework detection, mocking, TS-specific considerations
extensions/powershell.md	PowerShell	Test commands (Pester v5), module import patterns, discovery/run pitfalls, mocking, common errors
extensions/cpp.md	C++	Testing internals with friend declarations
extensions/go.md	Go	`go test` commands, table-driven tests, integration vs unit layout, mocking via interfaces, common errors
extensions/java.md	Java	Maven/Gradle commands, JUnit 4/5 and TestNG detection, Mockito, Spring Boot slices, common errors
extensions/rust.md	Rust	`cargo test` commands, unit vs integration vs doc tests, features, async test harnesses, common errors
extensions/ruby.md	Ruby	RSpec and Minitest commands, Bundler usage, Rails specifics, mocking patterns, common errors
extensions/swift.md	Swift	SPM and Xcode test commands, XCTest vs Swift Testing, `@testable import`, async/throws tests, common errors
extensions/kotlin.md	Kotlin	Gradle commands, JUnit/Kotest detection, MockK, coroutines test, KMP and Android specifics, common errors
extensions/dotnet-examples.md	.NET (C#/F#/VB)	Concrete pipeline examples: sample research output, plan, generated tests, fix cycles, final report
extensions/python-examples.md	Python	Concrete pipeline examples (pytest): research, plan, generated test file, fix cycles, final report
extensions/typescript-examples.md	TypeScript/JavaScript	Concrete pipeline examples (Vitest, applicable to Jest): research, plan, generated test file, fix cycles, final report
extensions/go-examples.md	Go	Concrete pipeline examples (standard `testing`): research, plan, table-driven test file, fix cycles, final report
extensions/java-examples.md	Java	Concrete pipeline examples (JUnit 5 + Mockito on Maven): research, plan, generated test file, fix cycles, final report