acm-failure-classifier

Automate root cause analysis for Jenkins pipeline test failures by providing the path to 'core-data.json', which triggers a 5-phase investigation framework to classify failures into categories like PRODUCT_BUG, AUTOMATION_BUG, INFRASTRUCTURE, or NO_BUG.

Automated test failure classification works with MCP tools by analyzing failed test data and leveraging multiple MCP tools for data verification and correlation, applying a 12-layer diagnostic framework to isolate the root cause accurately.

Yes, you need a Python environment and the oc CLI for cluster access to classify test failures. These prerequisites enable the Skill to execute its diagnostic scripts and query the cluster for verification data.

Yes, you can investigate ACM cluster issues alongside automated test failure classification because the Skill integrates with acm-cluster-investigator, allowing you to perform detailed cluster investigations during the diagnostic process.

The 5-phase framework for test failure classification is limited to Jenkins pipeline test data and requires valid 'core-data.json' input; it cannot diagnose failures outside automated testing workflows or without proper cluster access via oc CLI.

The best way to categorize automated test failures into bug types is using an automated classifier that applies a 12-layer diagnostic framework, distinguishing between PRODUCT_BUG, AUTOMATION_BUG, INFRASTRUCTURE, or NO_BUG for quicker issue resolution.