skills.rest
CENKSSS
CENKSSSCOMMUNITY
Explore all skills by this author →
GitHub

test-failure-investigator

Diagnose test failures by classifying causes and generating investigation reports.

Updated Jun 15, 2026
Search Tags:#test automation#root cause analysis#flaky tests#test failure#software QA
One-click install
npx skills add https://github.com/CENKSSS/valocase-backend --skill test-failure-investigator-cenksss
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: test-failure-investigator
Source: https://github.com/CENKSSS/valocase-backend/tree/main/.claude/skills/test-failure-investigator
Command: npx skills add https://github.com/CENKSSS/valocase-backend --skill test-failure-investigator-cenksss

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill helps users diagnose and resolve test failures by guiding through a systematic investigation process.

Core Features & Use Cases

  • Classification of Failures: Determines whether a failure is a regression, environment issue, flaky test, or transient.
  • Investigation Flow: Provides step-by-step instructions to narrow down the cause of the failure.
  • Root Cause Analysis: Offers a guide to common failure symptoms and their likely causes.
  • Flaky Test Investigation: Includes methods to confirm flakiness and identify common causes.
  • Reporting: Generates a report summarizing the findings, classification, and recommended actions.

Quick Start

To investigate a failing test, run /test-failure-investigator [test-name-or-file].

Frequently Asked Questions about test-failure-investigator

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

FAQPage Schema
How do I find the root cause of a test failure in my automation framework?▼

To find the root cause of a test failure, you systematically investigate symptoms, narrow down the scope, and analyze potential causes. This process classifies the failure as a regression, environment issue, or transient problem to guide resolution.

What is the best way to investigate flaky tests in software QA?▼

Investigating flaky tests involves confirming the flakiness and identifying common causes through a guided root cause analysis. This approach helps software QA professionals isolate intermittent failures from actual regressions.

How do I classify test failures as regressions or environment issues?▼

Test failures are classified by analyzing failure symptoms and narrowing down the scope of the issue. This systematic investigation determines whether the failure stems from a code regression, an environment issue, or a flaky test.

Can I use a systematic investigation flow for any failing test?▼

Yes, a systematic investigation flow provides step-by-step instructions to narrow down the cause of any failing test. It guides software engineers through symptom analysis to classify the failure and recommend actions.

Do I need a test automation framework to perform root cause analysis on failing tests?▼

Yes, this root cause analysis is intended for software engineers and QA professionals working with test automation frameworks. The investigation process relies on analyzing symptoms generated by automated test executions.

Related Skills

Explore More Software Engineering Skills→
chrislawcodeschrislawcodes

test-runner-json

Executes project test suites and generates a detailed JSON report of failures.

Community
Intermediate
v1-iov1-io
6

fix-tests

Diagnose failing test outputs and apply minimal fixes across the codebase.

Official
Advanced
stolostronstolostron
3

acm-z-stream-analyzer

Classify Jenkins pipeline test failures and diagnose root causes.

Official
Advanced
kynoptickynoptic
1

Debugging Runtime Errors

Analyze stack traces and error logs to identify root causes and propose fixes.

Community
Advanced