Test Analysis Extensions
.NET (Microsoft)OfficialPublished by .NET (Microsoft)
- Skill
- Meta (authoring, orchestration, planning, memory)
- Agent tooling
- MIT
- No issues found
AutoGineer summary
Written by AutoGineer from the skill’s own files, not by the author
Test Analysis Extensions is a non-invocable data repository designed for internal use by other test-related agent skills. It provides structured reference files for various programming languages and their respective testing frameworks. These files contain essential metadata for identifying test markers, assertion APIs, lifecycle hooks, and anti-pattern indicators, enabling analysis agents to perform language-neutral evaluations across diverse codebases.
What it does
- Provides standardized lookup tables for test framework syntax and conventions.
- Maps language-specific features like setup/teardown hooks and skip annotations.
- Defines capability support levels for automated tagging and reporting.
- Enables consistent detection of mystery guest indicators and integration markers.
- Supports cross-language analysis by normalizing test-related concepts.
When to use it
- When building or maintaining test analysis agents that require framework-specific knowledge.
- When an agent needs to identify test lifecycle methods or assertion patterns in a specific language.
- When determining if a test suite supports automated tagging or requires report-only auditing.
Advantages
- Decouples analysis logic from framework-specific implementation details.
- Ensures consistent detection patterns across multiple programming languages.
- Provides clear capability definitions for automated test manipulation.
- Facilitates easier extension of analysis agents to new languages or frameworks.
Usage examples
- “N/A - This is a reference-only skill for internal agent use.”
- The agent automatically reads the relevant language file (e.g., python.md) to identify pytest fixtures and markers during analysis.
Install
Download the skill as a ZIP:
https://mp-staging.autogineer.com/agent-skills/dotnet/test-analysis-extensions/downloadUnzip it into the cross-client skills folder of your project:
mkdir -p .agents/skills && unzip test-analysis-extensions.zip -d .agents/skills
Documentation by .NET (Microsoft)
Test 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
- ATTRIBUTION.mdAdded by AutoGineer859 B
- LICENSELicence file added by AutoGineer1.1 KiB
- SKILL.md4.6 KiB
- extensions/cpp.md8.4 KiB
- extensions/dotnet.md6.7 KiB
- extensions/go.md7.4 KiB
- extensions/java.md7.5 KiB
- extensions/kotlin.md7.2 KiB
- extensions/powershell.md6.3 KiB
- extensions/python.md6.8 KiB
- extensions/ruby.md6.6 KiB
- extensions/rust.md7.2 KiB
- extensions/swift.md6.8 KiB
- extensions/typescript.md7.4 KiB
extensions/swift.md
Swift Test Frameworks Reference (XCTest, Swift Testing)
Reference data for analyzing Swift test code. Used by the polyglot test analysis skills.
Capability tags
| Capability | Support |
|---|---|
| Test discovery | Strong — XCTestCase subclasses, @Test functions |
| Assertion detection | Strong — XCTAssert*, #expect, #require |
| Sleep/delay detection | Strong — Thread.sleep, Task.sleep, XCTWaiter |
| Skip/ignore detection | Strong — XCTSkip, .disabled(...) |
| Setup/teardown detection | Strong — setUp/tearDown, init/deinit for Swift Testing |
| Tag support | auto-edit (Swift Testing) — @Test(.tags(...)) / @Suite(.tags(...)); XCTest: report-only |
Test File Identification
| Framework | File convention | Test method markers |
|---|---|---|
| XCTest | *Tests.swift (Swift Package Manager: Tests/<Module>Tests/) | class FooTests: XCTestCase with methods starting test |
| Swift Testing | same conventions | @Test func foo() async throws { ... }, optionally inside @Suite types |
Both frameworks can coexist in one target.
Assertion APIs
| Category | XCTest | Swift Testing |
|---|---|---|
| Equality | XCTAssertEqual(actual, expected) | #expect(actual == expected) |
| Inequality | XCTAssertNotEqual | #expect(actual != expected) |
| Boolean | XCTAssertTrue / XCTAssertFalse | #expect(condition) |
| Nil | XCTAssertNil / XCTAssertNotNil | #expect(value == nil) / #expect(value != nil) |
| Throws | XCTAssertThrowsError(try fn()) { error in ... } | #expect(throws: SomeError.self) { try fn() } / try #require(throws: ...) |
| No throw | XCTAssertNoThrow(try fn()) | implicit (just call try fn()) |
| Identical (reference) | XCTAssertIdentical | #expect(a === b) |
| Approximate | XCTAssertEqual(x, y, accuracy: 0.01) | #expect(abs(x - y) < 0.01) |
| Type | XCTAssertTrue(x is T) | #expect(x is T) |
| Membership | XCTAssertTrue(arr.contains(item)) | #expect(arr.contains(item)) |
| Fail | XCTFail("reason") | Issue.record("reason") |
| Soft fail (continue) | continues on XCTAssert* by default | #expect (records issues, continues) |
| Hard fail (stop) | XCTSkipIf is skip; no hard-fail at test level | try #require(...) aborts the test |
Sleep/Delay Patterns
| Pattern | Example |
|---|---|
| Thread sleep | Thread.sleep(forTimeInterval: 1.0) |
| Async sleep | try await Task.sleep(nanoseconds: 1_000_000_000) (Swift 5.5+) |
| Async sleep (newer) | try await Task.sleep(for: .seconds(1)) (Swift 5.7+) |
| XCTest waiter | wait(for: [exp], timeout: 5) (acceptable for expectation-based tests) |
| Async waiter | await fulfillment(of: [exp], timeout: 5) (Xcode 14+) |
XCTestExpectation + wait(for:timeout:) is the idiomatic async-coordination pattern in XCTest — not a sleep smell.
Skip/Ignore Annotations
| Framework | Annotation |
|---|---|
| XCTest | throw XCTSkip("reason"), XCTSkipIf(cond, "reason"), XCTSkipUnless(cond, "reason") |
| Swift Testing | @Test(.disabled("reason")), @Test(.disabled(if: cond, "reason")), @Test(.enabled(if: cond)) |
Exception Handling — Idiomatic Alternatives
// XCTest:
XCTAssertThrowsError(try service.placeOrder(emptyOrder)) { error in
guard case OrderError.empty = error else {
XCTFail("Expected .empty, got \(error)")
return
}
}
// Swift Testing:
#expect(throws: OrderError.self) {
try service.placeOrder(emptyOrder)
}
// Specific case (Swift Testing):
let err = try #require(throws: OrderError.self) { try service.placeOrder(emptyOrder) }
#expect(err == .empty)Flag manual do { try fn(); XCTFail("expected throw") } catch { ... } patterns and recommend the framework-native form.
Mystery Guest — Common Swift Patterns
| Indicator | What to look for |
|---|---|
| File system | FileManager.default.contents(atPath:), hard-coded Bundle.main paths |
| Database | direct SQLite.swift against real file, raw CoreData saves outside in-memory store |
| Network | URLSession.shared.dataTask without URLProtocol stub, Alamofire to real URL |
| Environment | ProcessInfo.processInfo.environment["X"] |
| Acceptable | URLProtocol stubs, OHHTTPStubs, Mocker, NSPersistentContainer with in-memory store type, Bundle.module resource paths |
Integration Test Markers
Folder convention:
IntegrationTests/,UITests/,E2ETests/Class name suffix:
*IntegrationTests,*UITestsXCUITest(XCUIApplication,XCUIElement) → UI/E2E testSwift Testing
@Tagnamed.integrationor.ui
Setup/Teardown
| Framework | Per-test | Per-class/suite |
|---|---|---|
| XCTest | setUp() / setUpWithError() | override class func setUp() |
| XCTest | tearDown() / tearDownWithError() | override class func tearDown() |
| Swift Testing | init(...) async throws per instance | static via @Suite type |
| Swift Testing | deinit for cleanup | static via @Suite type |
Swift Testing creates a fresh instance per test by default — fields initialized in init are reset between tests.
Tag/Trait Attributes (for test-tagging)
| Framework | Tag mechanism | Example |
|---|---|---|
| Swift Testing | @Test(.tags(.positive, .boundary)) (predefined or custom tag) | requires extension Tag { @Tag static var positive: Self } |
| Swift Testing (suite) | @Suite(.tags(...)) | inherits tags to contained tests |
| XCTest | none built-in — use class organization, naming, or test plans (.xctestplan) | (report-only) |
For Swift Testing, define tags in a single module-level location:
extension Tag {
@Tag static var positive: Self
@Tag static var negative: Self
@Tag static var boundary: Self
@Tag static var integration: Self
}Language-specific calibration notes
Swift Testing
#expectcontinues on failure;try #requireaborts. Tests that mix preconditions and assertions should usetry #requirefor preconditions.XCTAssert*continues on failure — tests with multiple cascading assertions may log many failures from one root cause.Async tests must
await— missingawaitcauses warnings and silent skips on async APIs.Combine tests with
expectation(description:)are XCTest's idiomatic async pattern; not a sleep smell.Snapshot testing (
SnapshotTestinglibrary) — treat snapshot comparisons as legitimate assertions; flag stale records.Parametrized tests (
@Test(arguments: [...])) are NOT duplicates.Test plans (
.xctestplan) can filter by tags / configurations; mention as a structural alternative to per-test tagging.continueAfterFailure— whenfalse, XCTest stops on first failure (useful for fast-fail integration tests).
Requirements and compatibility
Written for: Claude Code
Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta
“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.
Needs: Claude Code frontmatter, Needs Python, Needs Node.js
Security
No issues found by our static scan· No issues found
A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.
Attribution and licence
- Published by
- .NET (Microsoft)
- Publisher
- .NET (Microsoft) (Official)
- Source
- dotnet/skills · plugins/dotnet-test/skills/test-analysis-extensions · commit 96c3d68
- Licence
- MIT License (redistribution allowed)
- LICENSE (added by AutoGineer from LICENSE)
- ATTRIBUTION.md (written by AutoGineer)
- Synced
AutoGineer is not affiliated with or endorsed by .NET (Microsoft).
Download ZIP
The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download test-analysis-extensions.zip