agentleFS
hu465hu465/claude-skills-/.claude/skills/web-testing/SKILL.md

web-testing

Skill0 starsChanged 23 days agoMITView on GitHub

Web testing with Playwright, Vitest, k6. E2E/unit/integration/load/security/visual/a11y testing. Use for test automation, flakiness, Core Web Vitals, mobile gestures, cross-browser.

10 other projects use a version of this, 3 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use web-design-guidelines and research.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • VercelSkill

    web-design-guidelines

    Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".

    Also in 3 projects that use this

  • NVIDIASkill

    research

    Before designing a feature, research how comparable libraries solve the problem, check best practices, known pitfalls, and upstream changes. Use when starting a new feature, investigating an unfamiliar area, or the user asks to research something.

    Also in 3 projects that use this

The file

Files
SKILL.md

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

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.