e2e-testing

Automate critical user journeys with Playwright end-to-end tests.

Updated Feb 20, 2026
One-click install
npx skills add https://github.com/jota-batuta/batuta-dots --skill e2e-testing-jota-batuta
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: e2e-testing
Source: https://github.com/jota-batuta/batuta-dots/tree/main/BatutaClaude/skills/e2e-testing
Command: npx skills add https://github.com/jota-batuta/batuta-dots --skill e2e-testing-jota-batuta

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

End-to-end tests validate user journeys across UI, API, and data stores, but without clear patterns they become expensive, brittle, and hard to maintain.

Core Features & Use Cases

  • Page Object pattern for robust, maintainable selectors and interactions.
  • Tenant-isolation checks to ensure data boundaries across tenants.
  • sdd-verify integration to enforce presence and pass of E2E tests for features with UI.
  • Structured e2e layouts per feature with clear test journeys and reusable fixtures.

Quick Start

Write and run Playwright end-to-end tests following Batuta conventions.

Frequently Asked Questions about e2e-testing

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

FAQPage Schema
How do I automate end-to-end tests with Playwright using page objects?

Automate end-to-end tests with Playwright by structuring tests with Page Object models for maintainable selectors, explicit waits for resilient interactions, and tenant-scoped fixtures to ensure repeatability across UI, API, and data layers.

How do I test multi-tenant isolation in E2E test automation?

Test multi-tenant isolation by implementing tenant-scoped fixtures and specific isolation checks in your E2E tests, verifying that data boundaries are maintained across different tenants during critical user journeys.

How do I prevent flaky Playwright tests with explicit waits?

Prevent flaky Playwright tests by replacing implicit waits with explicit waits for UI state changes, combining them with accessible page objects and resilient selectors to ensure reliable and repeatable test execution.

What is the best way to structure Playwright E2E tests per feature?

Structure Playwright E2E tests per feature by creating structured layouts with clear test journeys and reusable tenant-scoped fixtures, ensuring critical user paths are isolated and maintainable.

Can I enforce E2E tests pass for features with UI in CI?

You can enforce E2E tests for UI features by integrating with sdd-verify requirements, which govern execution and validate the presence and successful pass of critical end-to-end test journeys before deployment.

Why do brittle E2E tests break and how can I make them maintainable?

Brittle E2E tests break due to unclear patterns and fragile selectors; making them maintainable requires adopting Page Object models, explicit waits, and reusable fixtures to validate user journeys robustly.