skills.rest
somachak
somachakCOMMUNITY
Explore all skills by this author →
GitHub

stabilizing-e2e-tests

Identify and fix flaky Playwright and Cypress end-to-end tests by aligning waits with user-visible outcomes.

Updated Apr 14, 2026
Search Tags:#playwright#cypress#e2e-testing#retry-patterns#test-flakiness#ci-stability#wait-for-state
One-click install
npx skills add https://github.com/somachak/claude-code-skills-db --skill stabilizing-e2e-tests
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: stabilizing-e2e-tests
Source: https://github.com/somachak/claude-code-skills-db/tree/main/skills/testing/stabilizing-e2e-tests
Command: npx skills add https://github.com/somachak/claude-code-skills-db --skill stabilizing-e2e-tests

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

End-to-end tests often fail or drift due to flakiness from timing, network conditions, and shared state. This skill helps you tighten waits, remove arbitrary sleeps, and ensure assertions reflect real user outcomes.

Core Features & Use Cases

  • Wait-for-state patterns instead of fixed delays to stabilize tests.
  • Data isolation per test to enable parallel runs and reduce interference.
  • Retry logic for transient failures with clear failure reports.
  • Debug-friendly guidance and reporting to speed triage and CI reliability.

Quick Start

Run the stabilizer on your Playwright or Cypress test suite to identify flaky steps and apply best-practice fixes.

Frequently Asked Questions about stabilizing-e2e-tests

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I fix flaky E2E tests in Playwright and Cypress?▼

Fix flaky E2E tests by aligning waits with user-visible outcomes and applying wait-for-state patterns instead of fixed delays. This skill identifies flaky steps and enforces data isolation to reduce interference from timing issues and network delays.

Why does my E2E test fail intermittently during CI pipeline runs?▼

E2E tests fail intermittently due to flakiness from timing issues, network conditions, and shared state. Stabilizing tests involves removing arbitrary sleeps, isolating test data per run, and implementing retry logic for transient failures.

Does this test stabilization approach work for both local development and CI pipelines?▼

Yes, this approach applies to both CI pipelines and local development across frontend and QA teams. It provides debug-friendly guidance and clear failure reports to speed up triage and ensure reliable CI stability.

What's the best way to handle transient network delays causing test flakiness?▼

Handle transient network delays by implementing retry logic for transient failures alongside wait-for-state patterns. This combination ensures tests only fail on genuine defects, providing clear failure reports to speed triage.

How do I isolate test data to enable parallel E2E test runs without interference?▼

Isolate test data per test to enable parallel runs and reduce state interference between test cases. This prevents shared state flakiness and ensures consistent test execution across different environments.

Related Skills

Explore More Software Engineering Skills→
ClubMediterraneeClubMediterranee
4

e2e-testing

Automate end-to-end testing workflows for web applications across multi-browser environments.

Official
Advanced
cskirocskiro
7

e2e-testing

Automate Playwright end-to-end test setup, generation, and regression detection.

Community
Advanced
programadorisgodprogramadorisgod
1

playwright-e2e-testing

Automate cross-browser end-to-end web tests with Playwright.

Community
Advanced
edneyreis999edneyreis999

e2e-playwright-diagnosis

Diagnose Playwright E2E test failures with browser reproduction and MCP orchestration.

Community
Advanced