write-e2e-tests

Automate end-to-end tests for critical user journeys using the repository's E2E framework.

37|20|Updated Mar 2, 2026
One-click install
npx skills add https://github.com/fieldsphere/cursor-team-marketplace-template --skill write-e2e-tests-fieldsphere
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: write-e2e-tests
Source: https://github.com/fieldsphere/cursor-team-marketplace-template/tree/main/plugins/testing/skills/write-e2e-tests
Command: npx skills add https://github.com/fieldsphere/cursor-team-marketplace-template --skill write-e2e-tests-fieldsphere

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Add or update end-to-end tests that protect critical user flows from the user's point of view.

Core Features & Use Cases

  • Discover and reuse the repository's E2E framework, fixtures, selectors, helpers, and file layout.
  • Cover the happy path and one meaningful failure, guard, or empty-state path to protect critical journeys.
  • Provide clear outputs including files added/updated, user journeys covered, and run results; or blockers if environment constraints prevent execution.

Quick Start

Run the existing E2E test suite to validate critical user journeys against the repository's browser stack.

Frequently Asked Questions about write-e2e-tests

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

FAQPage Schema
How do I automate end-to-end tests for real user journeys in my web application?

End-to-end tests automate multi-step web flows using your repository's existing browser test stack. This Skill reuses your current framework, fixtures, and selectors to validate critical user journeys and provide clear pass or fail run results.

What do I need to run E2E tests against my existing browser stack?

E2E tests require your repository's existing test framework, fixtures, selectors, helpers, and file layout. If environment constraints prevent execution, the process outputs blockers instead of run results to indicate missing dependencies.

How do I add UI regression protection for critical multi-step workflows?

UI regression protection covers the happy path plus one meaningful failure or empty-state path for critical journeys. It outputs files added or updated alongside test outcomes to ensure multi-step interfaces remain functional.

Does E2E test automation work with my existing Playwright fixtures and selectors?

E2E test automation discovers and reuses your repository's existing Playwright fixtures, selectors, helpers, and file layout to validate web interfaces. It adapts to your established framework rather than requiring a new test architecture.

What outputs should I expect when validating critical user flows with E2E tests?

Validating critical user flows outputs a list of files added or updated, the user journeys covered, and the final test run results. It targets both the happy path and a meaningful failure to ensure comprehensive coverage.