web-testing

Replay authenticated Playwright sessions headlessly and parse test results into a unified verdict.

5|Updated May 2, 2026
One-click install
npx skills add https://github.com/vanducng/skills --skill web-testing-vanducng
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: web-testing
Source: https://github.com/vanducng/skills/tree/main/skills/web-testing
Command: npx skills add https://github.com/vanducng/skills --skill web-testing-vanducng

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Headless Playwright replay for local web apps — scaffold a Playwright e2e suite whose logged-in identity comes from a vd:browser-profile storageState export, run it in CI, and parse Playwright/Vitest/JUnit results into one verdict. Use when the user says "set up playwright", "headless e2e", "run e2e in CI", "replay the logged-in session headless", "analyze test results", or wants the vd:web-e2e flows runnable without a headed browser.

Core Features & Use Cases

  • Replays authenticated sessions headlessly using a stored identity to enable unattended runs.
  • Parses Playwright, Vitest, and JUnit results into a single verdict suitable for CI outcomes.
  • Supports CI integration and local development workflows with storageState-driven testing.

Quick Start

Export your identity with a vd:browser-profile storageState and run the Playwright tests headlessly to generate the unified verdict.

Frequently Asked Questions about web-testing

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

FAQPage Schema
How do I run Playwright e2e tests headlessly with a logged-in session in CI?▼

Run headless Playwright e2e tests with a logged-in session by using a persisted storageState export from a browser-profile. This approach enables unattended CI runs by replaying the stored identity without launching a headed browser.

What is the best way to parse Playwright, Vitest, and JUnit test results into a single verdict?▼

Parsing Playwright, Vitest, and JUnit test results into a single verdict consolidates multiple framework outputs into one unified summary. This provides a clear pass or fail outcome suitable for CI integration and local development workflows.

Do I need Node 18 and chromium binaries installed to run headless Playwright replay?▼

Yes, running headless Playwright replay requires Node 18+, a project-local Playwright test installation, and chromium binaries. You also need an identity export via storageState from a browser-profile to authenticate the headless session.

How does storageState work for maintaining persistent identity in headless e2e testing?▼

StorageState maintains persistent identity in headless e2e testing by saving browser session data like cookies and localStorage from a profile. The headless replay reuses this exported state to bypass interactive authentication during unattended CI execution.

Can I use my local development Playwright suite for CI workflows with storageState?▼

Yes, you can use your local development Playwright suite for CI workflows with storageState. The same persisted browser identity enables both local development testing and unattended CI execution by running the tests headlessly.

Why does my headless e2e replay fail to authenticate in CI without a storageState export?▼

Headless e2e replay fails to authenticate in CI without a storageState export because there is no interactive browser to handle login flows. You must provide a persisted browser-profile storageState to inject the logged-in identity for unattended execution.