analyze-failureslisted

Triage Katalon True Platform/TestOps test failures and file defects. Use when you need to investigate failed test results, classify each failure as product defect vs automation defect vs environment/data issue, cluster failures by common signature, find likely root cause from execution data, and optionally create ALM-linked defects for real product bugs. This is failure diagnosis and defect filing; for the overall ship/no-ship release call use release-analyze, and for repairing the tests themselves use test-maintenance.
katalon-labs/true-skills · ★ 3 · AI & Automation · score 67

Install: claude install-skill katalon-labs/true-skills

# Katalon Analyze Failures Use this skill for the **failure-analysis** part of the report/analysis stage: turn a set of failed results into a diagnosis and, when warranted, filed defects. The core value is **classification** — separating real product bugs from automation and environment noise. ## Availability Boundary - **Available via MCP:** read results (`read_test_result`, `read_execution_test_results`, `find_test_results`, `read_execution`), defect context (`fetch_defect_data`), ALM discovery + filing (`find_alm_integration_projects`, `create_defect`). - **Not directly available:** AI root-cause summarization and automation-error-pattern analytics are TestOps/Studio product features, not MCP calls — narrate their availability, do not claim to call them. `create_defect` requires a **known failed test result ID** and ALM integration details; there is no ID-less defect creation. ## Triage Workflow ```text +---------------------+ +----------------------+ +----------------------+ | Collect failures | --> | Classify each | --> | Cluster by signature | | read results | | product/auto/env | | | +---------------------+ +----------------------+ +----------------------+ | v +----------------------+