integration-test-analysis

Diagnose Visual Studio integration test failures from Azure DevOps CI artifacts.

4|1|Updated May 1, 2026
One-click install
npx skills add https://github.com/CoolCoderSuper/vb-ls --skill integration-test-analysis-coolcodersuper
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: integration-test-analysis
Source: https://github.com/CoolCoderSuper/vb-ls/tree/main/roslyn/.github/skills/integration-test-analysis
Command: npx skills add https://github.com/CoolCoderSuper/vb-ls --skill integration-test-analysis-coolcodersuper

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Investigate and diagnose Visual Studio integration test failures from the roslyn-integration-CI Azure DevOps pipeline. It downloads and analyzes published test artifacts including exception logs, screenshots, MEF errors, and VSIX installer logs.

Core Features & Use Cases

  • Build timeline and job-status analysis to identify failed or canceled VS integration tests.
  • Artifact parsing: parse exception Activity XMLs, MEF errors, and VSIX logs; extract root causes and affected features.
  • Output: produce a structured [INTEGRATION_TEST_SUMMARY] JSON with detailed per-job and artifact analysis to guide root-cause diagnosis.

Quick Start

Run the Get-IntegrationTestStatus.ps1 PowerShell script with a BuildId to fetch timelines, download artifacts if desired, and generate a structured analysis.

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 failures from Azure DevOps?

Diagnose Visual Studio integration test failures by fetching build timelines, downloading published artifacts, and parsing Activity XMLs, MEF errors, and VSIX logs to produce a structured root-cause analysis summary.

How do I analyze MEF errors and VSIX logs from roslyn-integration-CI builds?

Analyze MEF errors and VSIX logs by downloading published test artifacts from the roslyn-integration-CI pipeline and parsing them to extract root causes and identify affected Visual Studio features.

What is the best way to find the root cause of an integration test timeout in Azure DevOps?

Find the root cause of integration test timeouts by fetching the Azure DevOps build timeline, analyzing job statuses, and parsing exception Activity XMLs to generate a structured diagnostic summary.

Can I use PowerShell to fetch build timelines and test artifacts for integration test analysis?

Use the Get-IntegrationTestStatus.ps1 PowerShell script with a BuildId to fetch Azure DevOps build timelines, download test artifacts, and generate structured integration test analysis output.

What does the integration test analysis output look like for failed CI runs?

The integration test analysis output is a structured INTEGRATION_TEST_SUMMARY JSON containing detailed per-job and artifact analysis designed to guide root-cause diagnosis for failed CI runs.

Does integration test diagnosis work for crashes and canceled jobs in Visual Studio runs?

Integration test diagnosis works for timeouts, crashes, and failures in Visual Studio runs by parsing published artifacts including exception logs, screenshots, and MEF errors to identify root causes.