code-testing-extensions

Provides language-specific test generation guidance files for the code-testing pipeline.

Updated Jul 2, 2026
One-click install
npx skills add https://github.com/ecoDriverltd/FoundryAgentsExperiment --skill code-testing-extensions-ecodriverltd
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: code-testing-extensions
Source: https://github.com/ecoDriverltd/FoundryAgentsExperiment/tree/main/.agents/skills/code-testing-extensions
Command: npx skills add https://github.com/ecoDriverltd/FoundryAgentsExperiment --skill code-testing-extensions-ecodriverltd

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Test generation agents need accurate, language-specific knowledge about build commands, test frameworks, mocking patterns, and common errors. This Skill centralizes that guidance into per-language reference files so code-testing agents can load exactly the right instructions for the target language instead of guessing. ## Core Features & Use Cases - Language Extension Files: Provides dedicated guidance files for .NET, Python, TypeScript, PowerShell, C++, Go, Java, Rust, Ruby, Swift, and Kotlin covering build/test commands, framework detection, mocking, and common errors. - Pipeline Examples: Ships concrete end-to-end examples (research output, plan, generated tests, fix cycles, final report) for .NET, Python, TypeScript, Go, Java, and C++. - Use Case: A code-testing agent about to generate tests for a Go module calls this Skill, reads extensions/go.md for table-driven test patterns and go test command guidance, then reads extensions/go-examples.md to model its research, plan, and report output. ## Quick Start Call the code-testing-extensions skill to get the file path for your target language, then read that extension file before writing any test code.

Frequently Asked Questions about code-testing-extensions

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

FAQPage Schema
How do I get language-specific test generation guidance for my project?▼

Call this Skill to receive the available extension file paths, then read the file matching your target language, such as dotnet.md for .NET or go.md for Go. Each file contains build commands, test commands, framework detection rules, and common error fixes.

What languages does the code-testing pipeline support?▼

Extension files exist for .NET (C#/F#/VB), Python, TypeScript/JavaScript, PowerShell, C++, Go, Java, Rust, Ruby, Swift, and Kotlin. Several languages also have companion examples files showing full pipeline walkthroughs.

Which test frameworks are covered for each language?▼

The guidance covers the mainstream frameworks per language: MSTest, xUnit, and NUnit for .NET; pytest for Python; Jest, Vitest, and Mocha for TypeScript; GoogleTest and Catch2 for C++; JUnit 4/5 and TestNG for Java; and the standard testing package for Go.

Can I invoke this Skill directly as a user?▼

No. The Skill is marked user-invocable false with model invocation disabled, meaning it is called internally by code-testing agents and skills that need language-specific references rather than by end users directly.

Why do generated tests fail with common compiler errors like CS0246 or undefined references?▼

Each extension file documents frequent errors and fixes, such as adding a ProjectReference for CS0246 in .NET or linking the test target to the library under test in C++. Reading the relevant extension before writing tests prevents these failures.