← LeaderboardThe Skill Leaderboard

code-testing-extensions

Provides file paths to language-specific extension files for the code-testing pipeline. Read this reference-only catalog for extension guidance files (e.g., dotnet.md for .NET, cpp.md for C++). Agents and skills read its bundled files directly; do not invoke this catalog through the model's skill tool.

Published by dotnet ↗dotnet/skills

Try your first task

Start a fresh conversation. Replace the highlighted placeholders.

Use code-testing-extensions to provide a reference-only extension-selection note within an already active code-testing pipeline for [language and test-framework inventory]. Identify the matching bundled base-extension path relative to this catalog; require that complete extension before writing tests. Load a language-examples file only if representative repository tests are absent and the base guidance does not resolve the pattern. Do not invoke this catalog through a skill tool or present it as an independent testing workflow. Return the selected path and missing inputs only; wait for my explicit confirmation before reading project files, running commands or changing anything.

Required inputs

[language and test-framework inventory]

User-approved starter prompt based on a pinned source version; check current skill requirements before running. Task evidence ↗

SKILL.md

name: code-testing-extensionsdescription: >-  Provides file paths to language-specific extension files for the code-testing  pipeline. Read this reference-only catalog for extension guidance files  (e.g., dotnet.md for .NET, cpp.md for C++). Agents and skills read its bundled  files directly; do not invoke this catalog through the model's skill tool.user-invocable: falsedisable-model-invocation: truelicense: MIT

Code Testing Extensions

This reference-only catalog lists bundled guidance for the code-testing pipeline. Read the matching file directly; do not invoke this catalog as a skill. Resource paths are relative to this catalog, not the project workspace.

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 base extension before writing test code. Load an <language>-examples.md file only when the repository has no representative tests and the base extension does not resolve the needed pattern. Do not load end-to-end examples for a focused request with established local conventions.