playwright

Automate browser-level verification with traces, screenshots, and replay logs.

7|Updated Feb 14, 2026

Search Tags:#playwright #deterministic #e2e-testing #browser-testing #test-plans #replay-artifacts

Ready to run

npx skills add https://github.com/KentoShimizu/sw-agent-skills --skill playwright-kentoshimizu

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: playwright
Source: https://github.com/KentoShimizu/sw-agent-skills/tree/main/skills/playwright
Command: npx skills add https://github.com/KentoShimizu/sw-agent-skills --skill playwright-kentoshimizu

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) and references (resource) components.

What problem does it solve?

Automates browser-level verification with reproducible artifacts (traces, screenshots, replay logs) that engineers can review and replay to confirm behavior changes before merge or release.

Core Features & Use Cases

Use this skill to validate browser-level behavior with reproducible artifacts that engineers can replay exactly.
Shared references and templates support deterministic replay rules, test plans, and artifact checklists for reliable evidence.
Use Case: Before merging a UI change, generate a trace and screenshots to verify critical user journeys across browsers.

Quick Start

Run a local Playwright test suite to generate deterministic traces and screenshots for the defined scenarios.

Frequently Asked Questions about playwright

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

FAQPage Schema

How do I generate reproducible browser testing artifacts for merge confidence?▼

To generate reproducible browser testing artifacts, automate end-to-end user journeys to produce traces, screenshots, and replay logs as evidence for merge confidence. Standardized artifact templates enforce deterministic replay prerequisites for reliable verification.

What is deterministic e2e-testing replay and when do I need it?▼

Deterministic e2e-testing replay is the process of reproducing exact browser behavior through recorded traces and logs. You need it to verify critical user journeys and confirm behavior changes before merging UI updates.

How do I run Playwright test plans across multiple browsers in a CI environment?▼

You can run Playwright test plans across supported browsers in CI environments by applying standardized command profiles and test plan templates. This automation validates critical user journeys while generating consistent replay logs as evidence.

Does this browser-testing approach work for both local and CI environments?▼

Yes, this browser-testing approach supports validating end-to-end user journeys across both local and CI environments. It enforces deterministic replay prerequisites to ensure reproducible traces and screenshots regardless of where tests execute.

What are the limitations of deterministic replay for browser-level verification?▼

Deterministic replay for browser-level verification requires strict adherence to standardized artifact templates and deterministic replay prerequisites. Limitations arise if test plans or command profiles deviate from these enforced templates, compromising reproducible evidence.

What's the best way to verify UI changes before a release using e2e-testing?▼

The best way to verify UI changes before release using e2e-testing is automating browser-level verification to generate reproducible traces and screenshots. Reviewing these replay logs confirms critical user journeys across supported browsers before merging.