E2E
Classify e2e test failures and apply targeted fixes using proven taxonomy
What You Can Do
You can quickly categorize e2e test failures using a proven taxonomy (flaky, outdated, or bug), then apply the correct fix strategy for each category. The skill ensures you never conflate test infrastructure issues with implementation problems, maintains clean boundaries between test and source code, and validates fixes against specifications before modifying application logic.
Features
instantly categorize failures as flaky (timing/selector issues), outdated (test doesn't match current behavior), or bugs (code doesn't match spec)
replace arbitrary delays with auto-waiting locators, fix race conditions with web-first assertions, and correct selector brittleness using semantic queries
update assertions and selectors to match current correct behavior without touching source code
only classify as bugs when spec exists; fix source code with unit tests first, never modify e2e assertions to match buggy code
prevents accidental API contract changes and enforces test/implementation separation
flags failures without specification backing for stakeholder decision-making
quotes relevant specification sections before applying any implementation fixes
Example Output
Example 1: Flaky Failure
Input: Test intermittently fails with element not found on login form
Classification: Flaky — stale selector / race condition
Fix:
// Before: brittle selector + arbitrary delay
await page.waitForTimeout(500);
const button = await page.$('.login-btn');
// After: semantic locator + web-first assertion
const button = page.getByRole('button', { name: /sign in/i });
await expect(button).toBeVisible();
Example 2: Outdated Test
Input: Test fails asserting error message on empty email field
Classification: Outdated — spec changed, email is now optional
Fix: Update test assertion to match current (correct) behavior
// Before: expects error
await expect(page.getByText(/email required/i)).toBeVisible();
// After: reflects new spec (email optional)
await expect(page.getByText(/email required/i)).not.toBeVisible();
Example 3: Bug with Spec
Input: Test consistently fails; payment confirms before processing
Classification: Bug — implementation violates payment spec § 4.2
Fix: Correct source code to match spec, add unit tests first
// Per Spec § 4.2: "confirmation must occur AFTER processing"
// Fix in payment.js, then verify with unit test before e2e
test('payment confirmation waits for processor response', () => { ... });
What's Included
- SKILL.md: complete failure taxonomy and fix rules by category
- Flaky Fixes Checklist: selector strategies, timing patterns, and anti-patterns
- Bug vs. Outdated Decision Tree: flowchart for classification when ambiguous
- Spec Validation Template: format for quoting spec sections before bug fixes
- Source Code Boundary Guardrails: rules preventing test/implementation bleed
Who It's For
- QA Engineers — diagnose and fix e2e test failures systematically without guesswork
- Frontend Developers — apply test fixes that preserve code boundaries and specification integrity
- Test Automation Engineers — maintain flaky test prevention and classification consistency across suites
- Engineering Leads — enforce strict test/implementation separation and spec-driven bug fixes in code review
Best For
- Debugging intermittent e2e test failures and flaky assertions
- Updating tests after intentional feature changes without touching source code
- Validating that bug fixes match specification before implementation
- Preventing accidental API contract changes during e2e debugging
- Classifying ambiguous test failures for stakeholder action
You might also like
You can rapidly map warranty claims, field failures, and quality escapes to specific production processes, equipment conditions, or supplier issues across engine, transmission, and drivetrain systems. By correlating defect clusters with build dates, shift schedules, component batches, and process parameters, you'll isolate root causes and develop data-driven corrective actions that prevent recurrence rather than treating symptoms.
by alleneubankYou can architect test automation frameworks tailored to your tech stack and design maintainable test suites from requirements. This skill helps you identify test patterns, eliminate flakiness, integrate with CI/CD pipelines, and build test infrastructure that scales with your codebase.
You can rapidly diagnose production bottlenecks by analyzing multi-source data from your body shop—shift reports, quality logs, cycle times, downtime codes, and equipment metrics. Claude correlates variables across paint, welding, and assembly lines to identify root causes of throughput loss, surface hidden process dependencies, and quantify the impact each constraint has on overall output. You receive actionable, prioritized recommendations with expected improvement impact so you can focus resources on interventions that drive the greatest gains.
by alleneubank
You can simultaneously analyze regulatory requirements across 3+ automotive certification regions (EU, US EPA/NHTSA, China CAAM, India SIAM, etc.) to pinpoint conflicting standards, missing compliance pathways, and cost-effective remediation strategies. This skill helps you prioritize engineering changes by compliance impact, document regulatory equivalencies for submission justification, and create region-specific certification roadmaps with realistic timelines—all without re-engineering your entire platform for every market.
by alleneubank
You can conduct structured root cause analyses on supplier quality incidents using automotive industry standards (AIAG, IATF, VDA). The skill guides you through incident assessment, multi-level RCA using decision trees, and generates detailed corrective action plans (CAPs) with effectiveness verification. You'll transform raw incident data into compliance-ready documentation that addresses systemic issues, reduces repeat failures, and supports supplier performance benchmarking.
by alleneubank
You can systematically analyze warranty claim datasets to uncover systemic failure patterns rather than treating claims as isolated incidents. The skill calculates financial impact, identifies high-risk components or assemblies, and generates prioritized corrective action recommendations backed by statistical evidence. You'll move from reactive claim handling to proactive quality improvement with data-driven arguments for design changes, process modifications, or supplier interventions.
by alleneubank
You can transform raw warranty claim data into actionable root cause analyses that prevent recurrence and protect customer satisfaction. This skill helps you correlate technical data with customer complaints, identify failure patterns across vehicle populations, and develop targeted corrective actions—accelerating investigation timelines while maintaining analytical rigor for effective quality decisions.
by alleneubank
You can pinpoint exact bottlenecks in your paint line—whether from spray booth scheduling conflicts, cure time dependencies, or spray gun performance issues—using structured diagnostic methods. This skill guides you through analyzing utilization logs, defect reports, and cycle time data to surface root causes, then builds actionable improvement plans with specific targets for throughput, quality, and cost reduction.
by alleneubank