Is it compatible with the Page Object Model (POM)?

Absolutely. One of its primary use cases is extracting inline selectors and logic into structured Page Objects to reduce code duplication.

Does it support TypeScript?

Yes, it is designed to work with TypeScript Playwright setups and can help implement proper types and interfaces during refactoring.

Can it help with test flakiness?

Yes, it identifies race conditions and hardcoded waits, replacing them with proper web-first assertions and network idle states to improve reliability.

How does it handle locator updates?

It can perform bulk updates of data-testid values or CSS selectors across your entire test suite, ensuring consistency after UI changes.

Can this skill create new Playwright tests from scratch?

No, this skill is specifically optimized for maintaining and refactoring existing tests. For creating new tests, you should use the test-generator skill.

Playwright Test Maintainer

Name: Playwright Test Maintainer
Author: joel611

byjoel611

•

Seguridad y Pruebas

Refactors and optimizes existing Playwright E2E test suites to improve stability, maintainability, and code quality.

Acerca de

This skill is designed to streamline the maintenance of Playwright end-to-end testing codebases. It automates the tedious tasks of updating locators across multiple files, refactoring duplicate code into reusable utilities or Page Objects, and fixing flaky tests by implementing robust waiting strategies. By enforcing industry best practices like the AAA pattern and proper TypeScript typing, it helps developers keep their test suites clean, efficient, and resilient to frequent UI changes.

Características Principales

Enforcement of testing best practices and AAA patterns
1 GitHub stars
Refactoring of duplicate code into Page Objects and utilities
Consolidation of redundant tests using data-driven patterns
Automated locator updates across entire test suites
Flaky test remediation via improved waiting strategies

Casos de Uso

Migrating a legacy test suite with inline selectors to the Page Object Model
Updating test selectors after a major frontend UI redesign or data-testid change
Eliminating test flakiness caused by race conditions or improper network handling

Acerca de

Características Principales

Enforcement of testing best practices and AAA patterns
1 GitHub stars
Refactoring of duplicate code into Page Objects and utilities
Consolidation of redundant tests using data-driven patterns
Automated locator updates across entire test suites
Flaky test remediation via improved waiting strategies

Casos de Uso

Migrating a legacy test suite with inline selectors to the Page Object Model
Updating test selectors after a major frontend UI redesign or data-testid change
Eliminating test flakiness caused by race conditions or improper network handling