skills.rest
lciacci
lciacciCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

playwright-testing

Build Playwright end-to-end browser tests with reliable locators and isolated fixtures.

Updated Jun 19, 2026
Search Tags:#ci/cd#browser automation#playwright#e2e testing#page objects#cross-browser testing#dead link detection
One-click install
npx skills add https://github.com/lciacci/tessera --skill playwright-testing-lciacci
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: playwright-testing
Source: https://github.com/lciacci/tessera/tree/main/skills/playwright-testing
Command: npx skills add https://github.com/lciacci/tessera --skill playwright-testing-lciacci

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams build reliable end-to-end tests without brittle selectors, hardcoded waits, shared state, or incomplete browser coverage.

Core Features & Use Cases

  • Cross-Browser Testing: Configure Chromium, Firefox, WebKit, and mobile browser projects with CI-friendly settings.
  • Reliable Test Design: Use accessible locators, Page Object Models, fixtures, web-first assertions, isolated test data, and network mocking.
  • Use Case: Create an authenticated checkout test that covers product selection, payment, success verification, visual checks, and dead-link detection across supported browsers.

Quick Start

Use the Playwright testing skill to create a robust cross-browser E2E test suite for the application's login and checkout flows.

Frequently Asked Questions about playwright-testing

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

FAQPage Schema
How do I build reliable cross-browser E2E tests with Playwright without flaky selectors?▼

You can reduce flaky selectors in E2E tests by using user-facing locators, Page Object Models, and web-first assertions. Playwright's auto-waiting mechanism handles dynamic content without requiring hardcoded waits.

What is the best way to configure Playwright for CI execution across desktop and mobile browsers?▼

The best way to configure Playwright for CI is to define browser projects for Chromium, Firefox, and WebKit with CI-friendly settings. You can execute automated test suites across both desktop and mobile browsers within your integration pipeline.

Can I mock APIs and handle authenticated checkout workflows in Playwright?▼

Yes, you can mock APIs and handle authenticated checkout workflows in Playwright. You can create tests that cover product selection, payment processing, and success verification using network mocking and isolated test data fixtures.

Does Playwright support visual regression and dead link detection for web applications?▼

Playwright supports visual regression and dead link detection for web applications. You can configure tests to perform visual checks across supported browsers and automatically detect dead links during your E2E test runs.

Why do my Playwright tests fail due to shared test state and how do I fix it?▼

Playwright tests fail due to shared test state when data overlaps between runs. You can fix this by using isolated fixtures and isolated test data, ensuring each test executes independently without relying on shared state.

Related Skills

Explore More Software Engineering Skills→
vincehvinceh
1

playwright-testing

Create Playwright end-to-end tests with TypeScript and GitHub Actions.

Community
Advanced
EstomEstom

playwright-expert

Create Playwright end-to-end browser tests with Page Object Model patterns.

Community
Advanced
vecearvecear

mocking-assistant

Automate MSW-based API and service mocks with fixtures and test overrides.

Community
Advanced
makeupmakeup
47

test-coverage

Evaluate unit test coverage for makeup-js modules and generate prioritized gap reports.

Official
Intermediate