Is this skill suitable for CI/CD integration?

Yes, it covers advanced topics like test sharding, parallel execution, and environment-specific configurations specifically designed for automated delivery pipelines.

Does this skill support both Playwright and Cypress?

Yes, it provides specific implementation patterns, configurations, and best practices for both Playwright and Cypress frameworks, including setup and advanced usage.

How does this help with flaky tests?

It emphasizes deterministic waiting strategies, network interception, and proper fixture management instead of using unreliable fixed timeouts that often cause flakiness.

Can I use this for visual regression testing?

Absolutely. It includes specific patterns for capturing and comparing screenshots to catch visual UI regressions automatically during the testing process.

E2E Testing Patterns

Name: E2E Testing Patterns
Author: Microck

byMicrock

•

Seguridad y Pruebas

Implements reliable end-to-end testing suites using Playwright and Cypress to ensure robust application workflows and catch regressions.

Acerca de

This skill empowers Claude to architect and implement comprehensive end-to-end (E2E) testing strategies using industry-leading tools like Playwright and Cypress. It provides standardized patterns for the Page Object Model (POM), intelligent waiting strategies to eliminate flakiness, and network mocking for isolated testing. Beyond basic automation, it covers advanced capabilities like visual regression testing, accessibility audits with Axe-core, and CI/CD optimization through test sharding. It is ideal for developers looking to stabilize their test suites, validate critical user journeys across multiple browsers, and enable confident, fast deployment cycles.

Características Principales

Advanced network mocking and request interception for isolated frontend testing.
Visual regression testing patterns to detect unintended UI changes.
Deterministic waiting strategies and auto-assertions to eliminate flaky test results.
81 GitHub stars
Page Object Model (POM) implementation for maintainable and scalable test code.
Automated accessibility (a11y) testing integration using Axe-core.

Casos de Uso

Debugging and stabilizing unreliable or slow legacy E2E test suites.
Setting up cross-browser and mobile emulation testing in CI/CD pipelines.
Automating critical user flows such as authentication, multi-step forms, and checkout processes.

Acerca de

Características Principales

Advanced network mocking and request interception for isolated frontend testing.
Visual regression testing patterns to detect unintended UI changes.
Deterministic waiting strategies and auto-assertions to eliminate flaky test results.
81 GitHub stars
Page Object Model (POM) implementation for maintainable and scalable test code.
Automated accessibility (a11y) testing integration using Axe-core.

Casos de Uso

Debugging and stabilizing unreliable or slow legacy E2E test suites.
Setting up cross-browser and mobile emulation testing in CI/CD pipelines.
Automating critical user flows such as authentication, multi-step forms, and checkout processes.