Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
mrgoonie avatar

Web Testing

  • 403 installs
  • 2.2k repo stars
  • Updated April 3, 2026
  • mrgoonie/claudekit-skills

web-testing is a Claude Code agent skill that plans and runs comprehensive web tests with Playwright, Vitest, and k6 for developers who need unit, E2E, load, security, visual, and accessibility validation before release.

About

web-testing is a Claude Code skill from mrgoonie/claudekit-skills for comprehensive browser and API testing before release. It recommends a testing pyramid of roughly 70% unit (Vitest/Jest under 50ms), 20% integration (Vitest with fixtures, 100–500ms), and 10% E2E (Playwright, 5–30s). Quick-start commands include `npx vitest run`, `npx playwright test`, `k6 run load-test.js`, `npx @axe-core/cli`, and `npx lighthouse`. Reference docs cover E2E Playwright workflows, component testing, flakiness mitigation, Core Web Vitals, mobile gestures, cross-browser matrices, and CI gates where unit tests fail fast before E2E and accessibility checks. Developers reach for web-testing to automate regression checks, load validation, visual regression, and a11y scans on critical flows like login, checkout, and payment.

  • E2E flow validation
  • Regression checklists
  • Browser behavior checks
  • UI interaction testing
  • Pre-release sign-off

Web Testing by the numbers

  • 403 all-time installs (skills.sh)
  • +3 installs in the week ending Jul 26, 2026 (Skillselion tracking)
  • Ranked #649 of 2,155 Testing & QA skills by installs in the Skillselion catalog
  • Data as of Aug 3, 2026 (Skillselion catalog sync)
npx skills add https://github.com/mrgoonie/claudekit-skills --skill web-testing

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs403
repo stars2.2k
Last updatedApril 3, 2026
Repositorymrgoonie/claudekit-skills

How do you automate web app testing before release?

Plan and execute web app tests—manual flows, regression checks, and browser-level validation—before release using Claudekit web-testing guidance.

Who is it for?

Full-stack developers shipping web apps who need Playwright E2E, Vitest unit/integration, k6 load tests, and axe/Lighthouse quality gates in one agent-guided workflow.

Skip if: Native mobile-only apps without browser surfaces, or backend services with no frontend where PHPUnit/Go test skills are a better fit.

When should I use this skill?

User asks to plan regression tests, fix flaky Playwright specs, run load tests, or add accessibility and Lighthouse checks before release.

What you get

Vitest unit reports, Playwright E2E results, k6 load metrics, axe accessibility findings, and Lighthouse performance scores in CI gates.

  • Test plans
  • Playwright and Vitest specs
  • CI gate configuration

By the numbers

  • Testing pyramid ratio: 70% unit, 20% integration, 10% E2E
  • Integrates 5 test tools: Vitest, Playwright, k6, axe-core CLI, and Lighthouse

Files

SKILL.mdMarkdownGitHub ↗

Web Testing Skill

Comprehensive web testing: unit, integration, E2E, load, security, visual regression, accessibility.

Quick Start

npx vitest run                    # Unit tests
npx playwright test               # E2E tests
npx playwright test --ui          # E2E with UI
k6 run load-test.js               # Load tests
npx @axe-core/cli https://example.com  # Accessibility
npx lighthouse https://example.com     # Performance

Testing Pyramid (70-20-10)

LayerRatioFrameworkSpeed
Unit70%Vitest/Jest<50ms
Integration20%Vitest + fixtures100-500ms
E2E10%Playwright5-30s

When to Use

  • Unit: Functions, utilities, state logic
  • Integration: API endpoints, database ops, modules
  • E2E: Critical flows (login, checkout, payment)
  • Load: Pre-release performance validation
  • Security: Pre-deploy vulnerability scanning
  • Visual: UI regression detection

Reference Documentation

Core Testing

  • ./references/unit-integration-testing.md - Unit/integration patterns
  • ./references/e2e-testing-playwright.md - Playwright E2E workflows
  • ./references/component-testing.md - React/Vue/Angular component testing
  • ./references/testing-pyramid-strategy.md - Test ratios, priority matrix

Cross-Browser & Mobile

  • ./references/cross-browser-checklist.md - Browser/device matrix
  • ./references/mobile-gesture-testing.md - Touch, swipe, orientation
  • ./references/shadow-dom-testing.md - Web components testing

Interactive & Forms

  • ./references/interactive-testing-patterns.md - Forms, keyboard, drag-drop
  • ./references/functional-testing-checklist.md - Feature testing

Performance & Quality

  • ./references/performance-core-web-vitals.md - LCP/CLS/INP, Lighthouse CI
  • ./references/visual-regression.md - Screenshot comparison
  • ./references/test-flakiness-mitigation.md - Stability strategies

Accessibility

  • ./references/accessibility-testing.md - WCAG checklist, axe-core

Security

  • ./references/security-testing-overview.md - OWASP Top 10, tools
  • ./references/security-checklists.md - Auth, API, headers
  • ./references/vulnerability-payloads.md - SQL/XSS/CSRF payloads

API & Load

  • ./references/api-testing.md - API test patterns
  • ./references/load-testing-k6.md - k6 load test patterns

Checklists

  • ./references/pre-release-checklist.md - Complete release checklist

CI/CD Integration

jobs:
  test:
    steps:
      - run: npm run test:unit      # Gate 1: Fast fail
      - run: npm run test:e2e       # Gate 2: After unit pass
      - run: npm run test:a11y      # Accessibility
      - run: npx lhci autorun       # Performance

Related skills

How it compares

Pick web-testing over chrome-devtools alone when you need full pyramid planning—Vitest unit gates, Playwright E2E, k6 load, and axe/Lighthouse quality checks in one skill.

FAQ

Which frameworks does web-testing use?

web-testing centers on Vitest or Jest for unit and integration tests, Playwright for E2E flows, k6 for load testing, `@axe-core/cli` for accessibility, and Lighthouse for performance and Core Web Vitals.

What testing pyramid does web-testing recommend?

web-testing recommends roughly 70% unit tests under 50ms, 20% integration tests at 100–500ms, and 10% Playwright E2E tests at 5–30s per spec, prioritizing fast fail gates in CI.

When should web-testing run E2E versus unit tests?

web-testing assigns unit tests to functions and state logic, integration tests to API and database modules, and Playwright E2E to critical user flows such as login, checkout, and payment before release.

Testing & QAtestingfrontend

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.