integration-test-analysis

Analyze Visual Studio integration test failures from Azure DevOps builds into structured JSON summaries.

20.6k|4.3k|Updated Jan 11, 2015
One-click install
npx skills add https://github.com/dotnet/roslyn --skill integration-test-analysis
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: integration-test-analysis
Source: https://github.com/dotnet/roslyn/tree/main/.github/skills/integration-test-analysis
Command: npx skills add https://github.com/dotnet/roslyn --skill integration-test-analysis

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill analyzes Visual Studio integration test failures from Azure DevOps builds to identify root causes and timeouts, accelerating diagnosis for roslyn-integration-CI runs.

Core Features & Use Cases

  • Timeline and log analysis: Fetches build timelines and test runner logs to surface failure points, durations, and hung test assemblies.
  • Artifact inspection: Downloads and parses published artifacts (exception XMLs, screenshots, MEF errors, VSIX logs) to derive actionable root causes.
  • Structured summaries: Produces a detailed [INTEGRATION_TEST_SUMMARY] JSON with per-job diagnostics, artifact findings, and recommended remediation steps.
  • Use Case: When integration tests time out or fail in roslyn-integration-CI, the skill provides a structured diagnosis and guidance for remediation.

Quick Start

Run the PS script with a BuildId to analyze an Azure DevOps roslyn integration test run and optionally download artifacts for deeper inspection.

Frequently Asked Questions about integration-test-analysis

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

FAQPage Schema
How do I diagnose Visual Studio integration test timeouts in Azure DevOps?

Diagnose integration test failures by applying this skill to roslyn-integration-CI runs, which coordinates data collection from Azure DevOps, parses exception Activity XMLs, MEF errors, and VSIX logs to identify root causes.

How do I find the root cause of MEF errors and VSIX failures from CI artifacts?

Find root causes of integration test failures by downloading and inspecting published artifacts like exception XMLs, MEF errors, and VSIX logs, then generating a structured summary with actionable root-cause patterns and remediation guidance.

Does this integration test analysis work with roslyn-integration-CI builds?

Yes, this skill is designed for roslyn-integration-CI builds, analyzing build timeline data, per-step logs, and published artifacts to diagnose Visual Studio integration test failures and identify root causes.

How do I generate a structured summary of integration test failures?

Generate a structured summary by running the included PowerShell script with an Azure DevOps BuildId, which coordinates data collection, parses artifacts, and outputs an [INTEGRATION_TEST_SUMMARY] JSON with per-job diagnostics and root-cause patterns.

What do I need to analyze an Azure DevOps integration test run?

You need a valid Azure DevOps BuildId to run the PowerShell script, which fetches build timelines, test runner logs, and published artifacts to diagnose integration test failures.

What types of files are parsed when debugging VS integration test artifacts?

When debugging artifacts, the skill parses exception Activity XMLs, MEF errors, VSIX logs, and screenshots to derive actionable root causes and produce a structured [INTEGRATION_TEST_SUMMARY] JSON with per-job diagnostics.