webapp-testing

Design stable Playwright end-to-end tests with semantic selectors and storageState authentication.

Updated May 19, 2026
One-click install
npx skills add https://github.com/TimeKast/AgendaInteligente --skill webapp-testing-timekast
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: webapp-testing
Source: https://github.com/TimeKast/AgendaInteligente/tree/main/.agent/skills/webapp-testing
Command: npx skills add https://github.com/TimeKast/AgendaInteligente --skill webapp-testing-timekast

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the problem of flaky, hard-to-maintain browser end-to-end tests by prescribing battle-tested rules for stable Playwright suites.

Core Features & Use Cases

  • E2E test strategy: Defines a practical testing pyramid and prioritization for user flows, RBAC, CRUD, and error paths.
  • Stability guardrails: Enforces semantic selectors, isolated test data, independent tests, deterministic factories, and hydration-aware waiting.
  • Playwright patterns: Recommends storageState-based authentication, correct alert dialog handling, calibrated timeouts, and serial execution for heavy CRUD pages.
  • RBAC access verification: Provides a parametrized ACL × roles approach for zero-maintenance route security coverage.

Quick Start

Use the webapp-testing skill to design a Playwright E2E suite that verifies critical user flows and RBAC using semantic selectors and storageState-driven auth.

Frequently Asked Questions about webapp-testing

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

FAQPage Schema
Why are my Playwright E2E tests flaky and how do I stabilize them?

Playwright E2E tests become flaky due to fragile selectors and timing issues. You can stabilize them by enforcing semantic selectors, deterministic test data, and hydration-aware waits to prevent race conditions.

How do I set up Playwright authentication using storageState?

Playwright authentication setup uses storageState to save and reuse browser session data. This approach bypasses UI login flows for each test, dramatically reducing test execution time and authentication flakiness.

What is the best way to test RBAC route access in Playwright?

The best way to test RBAC route access is using a parametrized ACL × roles approach. This method iterates through user roles and protected routes to verify authorization rules with zero maintenance overhead.

Does the webapp-testing skill work for testing CRUD actions and edge cases?

Yes, the webapp-testing skill applies to E2E coverage for CRUD actions and error paths. It enforces serial execution for heavy pages and isolated test data to ensure deterministic CRUD testing.

When should I use hydration-aware waits in web app testing?

Hydration-aware waits are necessary when testing modern web frameworks where DOM elements render before interactive. Using them prevents test scripts from interacting with non-hydrated elements and causing false failures.