browser-testing

Codify Playwright and Puppeteer best practices into a reusable browser testing framework.

Updated Feb 7, 2026
One-click install
npx skills add https://github.com/jsamuelsen11/claude-config --skill browser-testing-jsamuelsen11
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: browser-testing
Source: https://github.com/jsamuelsen11/claude-config/tree/main/plugins/ccfg-core/skills/browser-testing
Command: npx skills add https://github.com/jsamuelsen11/claude-config --skill browser-testing-jsamuelsen11

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Browser-based UI testing is complex, brittle, and time-consuming. This Skill codifies best practices and reusable patterns to reduce flaky tests, accelerate test authoring, and ensure consistent test quality across projects.

Core Features & Use Cases

  • Clear test structure: arrange-act-assert and organized test suites.
  • Resilient element selection: semantic and role-based selectors.
  • Robust waiting and assertions: automatic retries with explicit waits when needed.
  • Page Object Model: reusable page interactions to promote maintainability.
  • Visual regression checks and accessibility: end-to-end coverage for UI quality.

Quick Start

Install or import the browser-testing skill into your project and begin authoring Playwright tests following the patterns outlined above.

Frequently Asked Questions about browser-testing

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

FAQPage Schema
How do I reduce flaky Playwright tests using resilient selectors?

To reduce flaky Playwright tests, use semantic and role-based resilient selectors combined with automatic retries and explicit waits. This framework codifies those waiting strategies and element selection patterns into a reusable structure.

What's the best way to structure end-to-end testing for maintainability?

The best way to structure end-to-end testing for maintainability is using the arrange-act-assert pattern alongside a Page Object Model. This approach provides reusable page interactions and organized test suites.

Does this browser testing framework support visual regression and accessibility audits?

Yes, this browser testing framework supports both visual regression checks and accessibility audits. It provides end-to-end coverage for UI quality by applying Playwright and Puppeteer best practices across modern web applications.

Can I use Puppeteer best practices for DevTools automation with this framework?

Yes, you can use Puppeteer best practices for DevTools automation with this framework. It streamlines browser-based testing by codifying Puppeteer patterns for reliable execution across modern web applications.

Why does my e2e-testing suite break frequently without a page object model?

Your e2e-testing suite likely breaks frequently without a page object model due to brittle selectors and disjointed test structures. Implementing reusable page interactions and resilient waiting strategies resolves these maintainability issues.