ck:web-testing

Automate web testing across unit, integration, E2E, load, security, visual, and accessibility suites.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/nam3886/golang-echo-boilerplate --skill ck-web-testing-nam3886
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ck:web-testing
Source: https://github.com/nam3886/golang-echo-boilerplate/tree/main/.claude/skills/web-testing
Command: npx skills add https://github.com/nam3886/golang-echo-boilerplate --skill ck-web-testing-nam3886

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Web testing is fragmented across tools and formats, making it hard to run consistent unit, integration, E2E, load, security, visual regression, and accessibility checks across local and CI environments. This Skill unifies testing strategy, best practices, and repeatable fixtures so teams can catch bugs earlier, reduce flakiness, and enforce performance and accessibility gates.

Core Features & Use Cases

  • Cross-tool coverage: Guidance and examples for Playwright, Vitest, k6, axe-core, Lighthouse and contract testing.
  • Test infrastructure: Patterns for CI sharding, testcontainers-backed databases, worker-scoped fixtures, and result aggregation.
  • Stability & quality: Flakiness mitigation, visual regression, Core Web Vitals measurement, and accessibility checklists to enforce quality gates.
  • Automation helpers: Scripts to initialize Playwright projects and to parse and summarize Playwright/Vitest/JUnit results for merge reports and CI artifacts.

Quick Start

Initialize the Playwright scaffold, run unit and E2E suites and then analyze results with the included analyze-test-results script against your local server.

Frequently Asked Questions about ck:web-testing

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

FAQPage Schema
How do I run E2E and accessibility tests in a CI pipeline?

You can automate E2E and accessibility web testing in CI pipelines using Playwright and axe-core with test sharding and JUnit outputs. The Skill includes result aggregation scripts to parse and summarize test artifacts for merge reports.

What is the best way to measure Core Web Vitals and run performance audits?

The best way to measure Core Web Vitals and run performance audits is by integrating Lighthouse and k6. This Skill unifies these tools to enforce performance gates and capture web vitals measurements across local and CI environments.

Does this approach support testcontainers for database fixtures in integration testing?

Yes, this web testing approach supports testcontainers-backed database fixtures for integration testing. It provides patterns for worker-scoped fixtures to ensure stable and repeatable test data across local and CI environments.

How do I reduce test flakiness in cross-browser E2E testing?

To reduce test flakiness in cross-browser E2E testing, this Skill provides flakiness mitigation patterns and visual regression testing. It uses Playwright to validate interfaces across browsers and mobile gestures, ensuring consistent stability.

Can I use Vitest for unit testing alongside Playwright for E2E testing?

Yes, you can use Vitest for unit testing alongside Playwright for E2E testing. This Skill offers cross-tool coverage, providing guidance and examples to run consistent unit, integration, and end-to-end checks within a unified testing strategy.

What are the limitations of aggregating JUnit and JSON test results?

A limitation of aggregating JUnit and JSON test results is that it requires consistent output formats across Vitest, Playwright, and other tools. This Skill provides automation helper scripts to parse and summarize these specific formats for CI reporting.