e2e-test-writer

Automate end-to-end testing workflows for browser, UI, API, and database journeys.

1|Updated Mar 4, 2026
One-click install
npx skills add https://github.com/Prathmesh2000/cursor_agent-orchestrator --skill e2e-test-writer-prathmesh2000
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: e2e-test-writer
Source: https://github.com/Prathmesh2000/cursor_agent-orchestrator/tree/main/agent-system/skills/e2e-test-writer
Command: npx skills add https://github.com/Prathmesh2000/cursor_agent-orchestrator --skill e2e-test-writer-prathmesh2000

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Write end-to-end tests that simulate complete user journeys through the real application, covering browser, UI, API, and database to ensure the system works end-to-end.

Core Features & Use Cases

  • Automated E2E Scenarios: Validate critical paths like login, navigation, data creation, and error handling across the full stack.
  • Tooling & Architecture: Leverage Playwright or Cypress with a page-object-model pattern for maintainability and scalable test data management.
  • Use Case: Imagine a signup journey where a new user registers, logs in, creates a profile, and first-time setup flows; this skill ensures the full journey works as intended.

Quick Start

Create an end-to-end test suite that validates a complete user signup flow using Playwright.

Frequently Asked Questions about e2e-test-writer

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

FAQPage Schema
How do I write end-to-end tests for full user journeys like signup and login?

Automated end-to-end testing validates complete user journeys across browser, UI, API, and database layers. It ensures real application flows like signup, login, and data creation work as intended.

What is the page-object-model pattern for E2E test automation?

The page-object-model pattern structures E2E test automation by separating UI element definitions from test logic. This ensures scalable test architecture and maintainable tests within an E2E framework.

Does this E2E testing approach support Playwright and Cypress in CI pipelines?

Yes, this E2E testing approach supports leveraging Playwright or Cypress within CI pipelines. It automates testing workflows to validate real user journeys across the full stack application.

How do I manage test data for E2E testing across a full-stack application?

Test data management for E2E testing handles data creation and error handling across a full-stack application. It ensures reliable data states are maintained within the E2E framework.

What is the best way to automate E2E scenarios for navigation and data creation?

The best way to automate E2E scenarios is validating critical paths like navigation and data creation using Playwright or Cypress. This ensures scalable test architecture and reliable test data management.

Why use E2E tests instead of isolated UI or API tests for critical paths?

E2E tests validate real user journeys across browser, UI, API, and database simultaneously, unlike isolated tests. This ensures the full stack application works end-to-end for critical paths like login and error handling.