testing-e2e

Create Playwright end-to-end tests for Drumr applications.

Updated Sep 16, 2025
One-click install
npx skills add https://github.com/slingr-stack/qa-test-drumr --skill testing-e2e-slingr-stack
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: testing-e2e
Source: https://github.com/slingr-stack/qa-test-drumr/tree/main/core/skills/testing-e2e
Command: npx skills add https://github.com/slingr-stack/qa-test-drumr --skill testing-e2e-slingr-stack

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the friction of creating, debugging, and maintaining end-to-end tests for Drumr applications by turning complex browser flows into reliable, repeatable Playwright specs.

Core Features & Use Cases

  • Test Authoring: Generate runnable TypeScript E2E specs that follow DrumrTestKit conventions and repository-specific patterns.
  • Debugging and Maintenance: Diagnose failures using screenshots, traces, video, and accessibility snapshots, then apply targeted fixes without rewriting tests.
  • Workflow Coverage: Validate real user journeys such as CRUD operations, navigation, permissions, authentication, and form-driven interactions in both drawer-based and page-based views.

Quick Start

Ask this Skill to create or fix a Drumr Playwright E2E test for a specific user flow, and it will produce a runnable spec that matches the app’s conventions.

Frequently Asked Questions about testing-e2e

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

FAQPage Schema
How do I write reliable Playwright end-to-end tests for Drumr applications?

Use this Skill to generate runnable TypeScript Playwright E2E specs that follow DrumrTestKit conventions, covering real browser flows like CRUD operations, navigation, and authentication with deterministic waits and fail-fast handling.

What is the best way to debug flaky Playwright browser tests in a Drumr app?

Diagnose flaky Playwright browser tests by using screenshots, traces, video recordings, and accessibility snapshots to pinpoint failures, then apply targeted fixes to your E2E specs without rewriting the entire test.

Can I automate E2E testing for drawer-based and page-based UI views with Playwright?

Yes, this Skill automates E2E testing for both drawer-based and page-based UI views, generating Playwright specs that validate form-driven interactions, permissions, and navigation across different view layouts.

Do I need DrumrTestKit helpers to run Playwright end-to-end tests?

Yes, DrumrTestKit public helpers are required to generate and run the Playwright E2E tests, as the Skill relies on them for deterministic waits, app-specific import paths, and fail-fast handling of missing capabilities.

Why does my Playwright E2E test fail during authentication and permissions flows?

Authentication and permissions E2E test failures often stem from missing credentials or unsupported helper capabilities, which this Skill handles using a fail-fast approach to surface issues immediately.

How do I cover CRUD operations and navigation in TypeScript E2E browser tests?

Generate TypeScript Playwright E2E specs that cover real user journeys including CRUD operations and navigation, ensuring specs match repository-specific patterns and DrumrTestKit conventions for reliable execution.