microshift-ci:test-scenario

To analyze MicroShift CI test failures, this Skill retrieves and parses scenario artifacts like junit.xml to extract pass/fail/skip breakdowns and failed test cases. It constructs artifact URLs and outputs a comprehensive Markdown report for fast root-cause investigation.

Triageing a failed e2e scenario requires interpreting the scenario name to provide RHEL version, release type, and test category metadata. This Skill summarizes diagnostic context and generates ready-to-click links to boot_and_run.log and rf-debug.log artifacts.

Yes, you can get direct links to phase logs by running the analysis with a given Prow job URL and scenario identifier. The Skill constructs operational artifact navigation URLs for junit.xml, boot_and_run.log, rf-debug.log, and phase logs.

Scenario name parsing works by interpreting the scenario-name structure to identify RHEL version, release type, test category, and whether it is an upgrade scenario. This metadata is then included in the comprehensive Markdown report alongside the test results.

Yes, you need a Prow job URL and scenario name to investigate MicroShift periodic job runs. The Skill uses these inputs to construct the correct artifact URLs, fetch the relevant junit.xml reports, and extract the specific scenario metadata.

Skipped test cases in MicroShift CI results are extracted and summarized by parsing the junit.xml file for failed, error, and skipped test cases. The Skill compiles these details into a Markdown report with relevant diagnostic context and direct artifact links.