hs:web-testing

Automates web testing with Playwright, Vitest, and k6 across unit, E2E, load, security, and accessibility layers.

Updated Jul 19, 2026
One-click install
npx skills add https://github.com/Dozyboy/VSF --skill hs-web-testing-dozyboy
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: hs:web-testing
Source: https://github.com/Dozyboy/VSF/tree/main/Day2_VSF/Demo1/harness/plugins/hs/disabled-skills/web-testing
Command: npx skills add https://github.com/Dozyboy/VSF --skill hs-web-testing-dozyboy

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve? Web applications need testing across many dimensions—unit logic, end-to-end flows, load capacity, security, accessibility, and visual consistency—but coordinating the right tools, configurations, and CI gates for each layer is complex and error-prone. ## Core Features & Use Cases - Multi-layer test execution: Run unit tests with Vitest, E2E tests with Playwright, load tests with k6, accessibility audits with axe-core, and performance checks with Lighthouse. - Project scaffolding and result analysis: Initialize a best-practice Playwright setup (config, fixtures, example tests) and parse Playwright/Vitest/JUnit results into a unified summary with pass-rate thresholds. - Strategy guidance: Choose between testing pyramid, trophy, or honeycomb models, with 20+ reference guides covering contract testing, database testing with Testcontainers, flakiness mitigation, mobile gestures, and OWASP security checks. - Use Case: Before a release, run unit tests as a fast-fail gate, shard E2E tests across CI workers, audit accessibility with axe-core, and verify Core Web Vitals budgets with Lighthouse CI. ## Quick Start Ask the agent to set up Playwright E2E testing for your web app and run the full test suite with accessibility and performance checks.

Frequently Asked Questions about hs:web-testing

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

FAQPage Schema
How do I set up Playwright E2E testing for a web project?▼

Run the init-playwright script to generate a best-practice setup including playwright.config.ts, authentication fixtures, example tests, and multi-browser projects for Chromium, Firefox, WebKit, and mobile devices. Then install @playwright/test and run npx playwright install.

How to run accessibility tests with axe-core and Playwright?▼

Use AxeBuilder from @axe-core/playwright inside a Playwright test to analyze a page and assert zero violations, optionally filtering by WCAG tags like wcag2aa. You can also run npx @axe-core/cli against any URL for a quick audit.

Vitest vs Playwright component testing, which should I use?▼

Use Vitest when speed matters and jsdom is sufficient for logic and DOM tests. Use Playwright component testing when you need a real browser, cross-browser verification, or CSS and layout validation, accepting slower execution.

How do I reduce flaky Playwright tests in CI?▼

Replace hard waits with explicit condition waits or Playwright's auto-waiting locators, isolate tests so none depend on shared state, disable CSS animations, and mock unstable network calls. Detect flakiness by running tests with --repeat-each=5.

Can I combine Playwright, Vitest, and JUnit test results into one report?▼

Yes, the analyze-test-results script parses Playwright JSON, Vitest JSON, and JUnit XML outputs into a unified summary with totals, pass rate, and failure details. It supports text, JSON, and Markdown output plus a fail-threshold exit code.

What are the limitations of this web testing approach?▼

It does not run tests by itself; every test type is executed by real runners like Vitest, Playwright, or k6 that the agent invokes. It does not apply to non-web targets such as native mobile apps or backends without an HTTP surface.