skills.rest
dotnet
dotnetOFFICIAL
Explore all skills by this author →
Website𝕏@dotnetfdnGitHub

standalone-test-repro-cmd

Resolves CoreCLR runtime test wrapper paths to source tests and effective invocations.

18.2k|5.6k|Updated Sep 24, 2019
Search Tags:#ci-failure#helix#dotnet-runtime#test-reproduction#coreclr#corerun#wrapper-resolution
One-click install
npx skills add https://github.com/dotnet/runtime --skill standalone-test-repro-cmd
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: standalone-test-repro-cmd
Source: https://github.com/dotnet/runtime/tree/main/.github/skills/standalone-test-repro-cmd
Command: npx skills add https://github.com/dotnet/runtime --skill standalone-test-repro-cmd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

CI and Helix failures report .NET runtime tests as generated .cmd or .sh wrapper paths, which do not directly reveal the underlying source test, owning project, or exact invocation needed to reproduce the failure locally.

Core Features & Use Cases

  • Wrapper Path Normalization: Cleans quoted, formatted, or argument-laden wrapper paths from CI logs and maps them back to src/tests/ source locations.
  • Invocation Extraction: Reads generated wrappers to capture corerun arguments, environment variables, pre/post commands, working directories, and expected exit codes.
  • Project Resolution: Locates the owning .csproj, source files, and AssemblyName, and evaluates CLRTest batch and bash command items.
  • Use Case: A CI failure reports JIT\Directed\ConvertToInt\checked\ConvertToInt.cmd with scenario jitstress1; this Skill resolves the exact source method, project, and effective invocation so the parent standalone-test-repro workflow can reproduce it.

Quick Start

Resolve the failing test at JIT\Directed\ConvertToInt\checked\ConvertToInt.cmd from the CI log and tell me the source test, project, and exact invocation.

Frequently Asked Questions about standalone-test-repro-cmd

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

FAQPage Schema
How do I reproduce a CoreCLR test failure from a CI wrapper path?▼

Normalize the .cmd or .sh path from the CI log, read the generated wrapper to capture corerun arguments and environment variables, then map the path back to src/tests/ to find the owning project. This Skill performs that resolution and hands off to the standalone-test-repro workflow.

How do I map a Helix test path back to src/tests source code?▼

Strip prefixes through the runtime test output root, remove configuration-only artifact segments, then search the remaining relative directory for the wrapper stem, .csproj, source file, and matching AssemblyName under src/tests/.

Does a .cmd test wrapper just run corerun on the test assembly?▼

No. Wrappers may include host options, -p and -e corerun arguments, environment variables, batch or bash pre/post commands, working-directory assumptions, and copied dependencies. The generated wrapper is the ground truth for the effective invocation.

What if the wrapper file is not available locally?▼

Use the path and stem to search under src/tests/ for the matching project, then derive invocation settings from the project file, its imports, and evaluated Compile and CLRTest command items.

What happens when a test assembly contains multiple runnable tests?▼

Resolution stops and asks for a fully qualified method name. The Skill only completes when the exact source method, owning project, and effective invocation are uniquely known.

Related Skills

Explore More Software Engineering Skills→
dotnetdotnet
13

ci-crash-dump

Identify crashed Helix work items and retrieve crash artifacts from dotnet CI runs.

Official
Advanced
cyalcalacyalcala
1

debugging-and-error-recovery

Diagnose root causes in failing tests, builds, and runtime errors via structured triage.

Community
Advanced
eleva-labseleva-labs

setup-env

Configure environment variables and .env files for frontend environments.

Official
Basic
joshka0joshka0
3

Route Research for Testing

Extract edited route paths from tsc-cache logs into JSON test specifications.

Community
Intermediate