Analyze Test Run
Turn a failed Azure pipeline or local test run into actionable root-cause notes so you can fix CI before you ship again.
Overview
analyze-test-run is an agent skill for the Ship phase that interprets completed test and pipeline runs on Azure so you can act on failures faster.
Install
npx skills add https://github.com/microsoft/azure-skills --skill analyze-test-runWhat is this skill?
- Interprets test and pipeline run output in an Azure-centric workflow
- Surfaces failure patterns and next debugging steps from run artifacts
- Pairs with microsoft/azure-skills for deploy-and-verify loops
- Aimed at indie teams using Azure DevOps or Azure-hosted CI
- 794 community installs on skills.sh (catalog signal, not a quality score)
Adoption & trust: 794 installs on skills.sh; 1.2k GitHub stars.
What problem does it solve?
Your pipeline or test job failed and the log wall makes it hard to see what broke or what to fix first.
Who is it for?
Indie builders using Azure-hosted CI who want an agent to summarize and reason over a finished test run.
Skip if: Greenfield test authoring, load-test design, or non-Azure workflows where this skill’s commands and context do not apply.
When should I use this skill?
After a test or pipeline run finishes—especially on failure or ambiguous exit codes—in an Azure-oriented repo.
What do I get? / Deliverables
You get a clearer read on failure clusters, likely causes, and concrete next steps to get CI passing again.
- Structured failure summary and suspected root causes
- Recommended next verification or fix steps
- Notes you can paste into a PR or issue
Recommended Skills
Journey fit
Test-run analysis is a Ship-phase gate: you use it when builds are green or red and you need to interpret failures before release. Testing subphase is where solo builders reconcile flaky suites, regression signals, and CI logs—not during ideation or growth experiments.
How it compares
Use for post-run diagnosis, not as a substitute for writing or maintaining your test suite.
Common Questions / FAQ
Who is analyze-test-run for?
Solo and small-team builders on Azure who already run automated tests and need help reading failed or noisy runs.
When should I use analyze-test-run?
Use it in Ship/testing after a CI job completes, when regressions block merge, or when you are iterating on fixes and re-running the same pipeline.
Is analyze-test-run safe to install?
Review the Security Audits panel on this Prism page and treat any skill that touches CI logs or cloud APIs as something you scope to non-production secrets until you trust the repo.
SKILL.md
READMESKILL.md - Analyze Test Run
# analyze-test-run Installs: 794 Source: microsoft/azure-skills { "id": "microsoft/azure-skills/analyze-test-run", "url": "https://www.skills.sh/microsoft/azure-skills/analyze-test-run", "name": "analyze-test-run", "slug": "analyze-test-run", "source": "microsoft/azure-skills", "installs": 794, "installUrl": "https://github.com/microsoft/azure-skills", "sourceType": "github" }