skills.rest
madarasz
madaraszCOMMUNITY
Explore all skills by this author →
GitHub

e2e

Automates enforcement of end-to-end testing conventions for the tests/e2e directory.

23|5|Updated Sep 19, 2016
Search Tags:#vitest#e2e#playwright#quality-assurance#test-automation#testing-conventions#browser-manager
One-click install
npx skills add https://github.com/madarasz/always-be-running --skill e2e-madarasz
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: e2e
Source: https://github.com/madarasz/always-be-running/tree/main/.agents/skills/e2e
Command: npx skills add https://github.com/madarasz/always-be-running --skill e2e-madarasz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Establishes and enforces consistent end-to-end testing practices for the tests/e2e directory, ensuring reliable, maintainable Playwright and Vitest test suites.

Core Features & Use Cases

  • Standardized test layout: tests/*.test.ts, page objects (pages/), helpers (helpers/), and a dedicated vitest configuration.
  • Reusable testing utilities: BrowserManager-based page objects and a structured test fixture to isolate tests and capture traces and screenshots on failure.
  • Clear guidelines for deterministic tests: strict wait strategies, proper isolation, and consistent test data handling.

Quick Start

Run the E2E test suite from the tests/e2e directory using the project's test setup.

Frequently Asked Questions about e2e

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

FAQPage Schema
How do I structure end-to-end tests with Vitest and Playwright?▼

Structure end-to-end tests using a tests/e2e directory containing test files (*.test.ts), page objects in pages/, helpers in helpers/, and a dedicated Vitest configuration to enforce consistent suite organization.

What is the best way to isolate Playwright E2E tests and capture failure artifacts?▼

Use a structured test fixture with a BrowserManager-based Page Object pattern to isolate Playwright E2E tests, automatically capturing traces and screenshots as failure artifacts when a test errors.

How do I manage browser instances for automated E2E testing?▼

Manage browser instances for E2E testing by implementing a reusable BrowserManager utility that handles browser setup and execution within page objects, ensuring strict test isolation and proper resource cleanup.

Why do my Playwright E2E tests have flaky wait strategies?▼

Flaky Playwright E2E tests often result from improper wait strategies; enforcing strict, deterministic wait guidelines and consistent test data handling eliminates timing race conditions and improves reliability.

Does this E2E testing convention work without external dependencies?▼

Yes, this E2E testing convention operates without external dependencies, applying standardized test isolation, browser management, and failure artifact capture directly to your Vitest and Playwright setup.

Can I use this approach to standardize test data and helpers in E2E suites?▼

Yes, you can standardize test data and helpers in E2E suites by organizing reusable utilities into dedicated helpers/ and pages/ directories, applying consistent conventions for deterministic test execution.

Related Skills

Explore More Software Engineering Skills→
eventua11yeventua11y
1

writing-tests

Automate E2E and unit test setup and execution with Playwright and Vitest.

Official
Intermediate
Muath2000Muath2000

qa-architect

Design software quality assurance strategies and automated testing frameworks.

Community
Advanced
nanorepublicananorepublica
61

Testing Unit Tests

Standardize unit-test coding practices across Claude Code projects.

Community
Basic
simotasimota
68

Voyager

Builds end-to-end browser automation suites with Playwright, Cypress, or WebdriverIO.

Community
Advanced