ylc-e2e-playwright

Name: ylc-e2e-playwright
Availability: InStock
Author: daichan132

Manage Playwright E2E testing workflows for the YouTube Live Chat Fullscreen extension.

34|Updated Oct 30, 2023

Search Tags:#playwright #e2e-testing #ci #web-automation #chrome-extension #test-flakiness

Ready to run

npx skills add https://github.com/daichan132/Youtube-Live-Chat-Fullscreen --skill ylc-e2e-playwright

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ylc-e2e-playwright
Source: https://github.com/daichan132/Youtube-Live-Chat-Fullscreen/tree/main/.agents/skills/ylc-e2e-playwright
Command: npx skills add https://github.com/daichan132/Youtube-Live-Chat-Fullscreen --skill ylc-e2e-playwright

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This guide provides a project-specific Playwright E2E testing workflow for the Youtube Live Chat Fullscreen extension, helping teams validate end-to-end behavior reliably without manual testing.

Core Features & Use Cases

Project-specific guidance: outlines infrastructure, fixtures, and guardrails for stable E2E tests.
Flaky-test debugging: describes strategies to diagnose and fix flaky tests, URL drift, and race conditions.
Use Case: when adding new tests or debugging, follow the documented conventions to maintain consistency across tests.

Quick Start

Run the Playwright e2e suite against the extension to verify fullscreen chat behavior.

Frequently Asked Questions about ylc-e2e-playwright

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

FAQPage Schema

How do I run Playwright E2E tests for a Chrome extension?▼

To run Playwright E2E tests for a Chrome extension, you execute the configured Playwright suite against the target browser extension environment to verify end-to-end behavior like fullscreen chat interactions reliably without manual testing.

What is the best way to debug flaky tests in Playwright CI workflows?▼

Debugging flaky tests in Playwright CI workflows involves using trace debugging and specific strategies to diagnose race conditions and URL drift, while enforcing reliability guardrails like single-worker execution to stabilize the end-to-end testing environment.

Can I use Playwright to automate web-extension testing in a CI pipeline?▼

Yes, you can use Playwright to automate web-extension testing in a CI pipeline by applying project-specific infrastructure, standardized POM references, and single-worker execution to enforce test reliability and prevent race conditions during automated runs.

Why does my Playwright test fail due to URL drift in E2E testing?▼

Playwright tests fail due to URL drift in E2E testing when application routing changes unexpectedly; resolving this requires following documented test maintenance conventions and using trace debugging to identify and update the affected navigation workflows.

Do I need single-worker execution for Playwright E2E testing of browser extensions?▼

Yes, single-worker execution is needed for Playwright E2E testing of browser extensions to enforce CI reliability, prevent race conditions, and ensure stable end-to-end behavior validation without concurrent test interference.