debugging-e2e-tests

To analyze failed Opik E2E tests, this skill gathers evidence from CI checks, local runs, and TestOps launches, classifies the failure as a regression, flake, or environmental issue, and proposes a targeted fix.

The best way to investigate Opik test failures from a pull request is to trigger this skill, which automatically collects traces and history from your failing run to classify the root cause and suggest a potential fix.

Yes, you can classify E2E test failures from local runs and TestOps launches; the skill evaluates gathered evidence to determine whether the failure stems from a regression, a flake, or an environmental issue.

Yes, you need access to GitHub, TestOps, and the Opik test environment to fully gather evidence, investigate failing runs, and propose accurate fixes for your E2E test failures.

Your Opik E2E test check might be failing due to a regression, a flake, or an environmental issue; this skill collects traces and run history to pinpoint the exact cause and propose a resolution.

Investigating Opik end-to-end test failures requires access to GitHub, TestOps, and the Opik test environment; without these integrations, the skill cannot gather the necessary evidence or propose accurate fixes.