standalone-test-repro-method

Resolves CoreCLR runtime test methods from fully qualified names for standalone reproduction.

18.2k|5.6k|Updated Sep 24, 2019
One-click install
npx skills add https://github.com/dotnet/runtime --skill standalone-test-repro-method
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: standalone-test-repro-method
Source: https://github.com/dotnet/runtime/tree/main/.github/skills/standalone-test-repro-method
Command: npx skills add https://github.com/dotnet/runtime --skill standalone-test-repro-method

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

CI failure logs for .NET runtime tests contain fully qualified method names with xUnit display arguments, assembly prefixes, and nested-type notation that are hard to map back to the exact source test, owning project, and invocation needed for local reproduction.

Core Features & Use Cases

  • Identifier Normalization: Strips quotes, CI log noise, assembly prefixes, and punctuation while preserving xUnit theory arguments and nested-type notation.
  • Source and Project Resolution: Searches C# sources under src/tests/ to locate the exact method declaration and finds the owning .csproj, including merged JIT regression assemblies with wildcard includes.
  • Invocation Analysis: Inspects Fact/Theory attributes, fixtures, constructors, async and generic signatures, conditional compilation, and theory data rows to determine faithful invocation semantics.
  • Use Case: Given a CI failure like Namespace.TypeName.MethodName with a jitstress1 scenario, resolve the exact test source and project, then hand off to the parent standalone-test-repro workflow for extraction.

Quick Start

Resolve the failing runtime test from this fully qualified method name and identify its owning project and invocation requirements.

Frequently Asked Questions about standalone-test-repro-method

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

FAQPage Schema
How do I find the source of a failing .NET runtime test from a CI log?

Extract the fully qualified method name from the CI failure, normalize it by removing quotes and log noise, then search C# sources under src/tests/ for the exact method declaration and confirm its containing type and namespace.

How do I reproduce an xUnit theory failure with specific arguments?

Preserve the xUnit display-name arguments from the failure log to identify the exact theory row. Reproduce only that row when arguments are present; otherwise generate invocations for all locally resolvable rows and label them.

Can this handle tests in merged or multi-test assemblies?

Yes, it locates the owning .csproj by explicit or evaluated Compile items, accounting for wildcard includes and merged projects such as JIT regression assemblies. Nested types and generic arity suffixes are also handled during parsing.

What happens when multiple source methods match the name?

When multiple candidates remain after resolution, the skill presents the concrete matches via the ask_user tool rather than guessing. Resolution completes only when the exact method, project, and invocation semantics are known.

Does the method name include the test scenario like jitstress1?

No, a separately supplied scenario such as jitstress1 is preserved apart from the method identifier. It is returned unchanged for canonicalization by the test-scenario-env skill in the parent workflow.