e2e-parse-ci-failure

You can parse CI job URLs or Jira tickets to extract test names, error messages, and relevant test parameters from build logs and Playwright reports. This failure analysis fetches artifacts and logs from GCS to identify precise failure reasons.

Yes, Jira MCP integration is required to function fully. The skill also depends on WebFetch and Playwright MCP, plus access to CI logs and GCS artifacts, to parse Jira comments and extract detailed failure context.

Yes, you can analyze Prow job failures and fetch GCS artifacts. The skill parses Prow reports to retrieve failure context and accesses GCS to analyze build logs, screenshots, and traces for end-to-end testing debugging.

The best way to debug Playwright test failures in a CI pipeline is to automatically gather all associated failure data, including screenshots and traces. Parsing build logs and reports from the CI job URL isolates error messages and relevant test parameters.

Without GCS access, parsing limitations include an inability to fetch build logs, screenshots, and traces for failure analysis. The skill requires access to CI logs and GCS artifacts to function fully and identify precise failure reasons.