envelope-editor-v2-e2e

Automate Playwright end-to-end tests for Envelope Editor V2 across four surfaces.

14.3k|3.0k|Updated Mar 12, 2023
One-click install
npx skills add https://github.com/documenso/documenso --skill envelope-editor-v2-e2e
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: envelope-editor-v2-e2e
Source: https://github.com/documenso/documenso/tree/main/.agents/skills/envelope-editor-v2-e2e
Command: npx skills add https://github.com/documenso/documenso --skill envelope-editor-v2-e2e

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a repeatable, maintainable pattern for writing Playwright end-to-end tests for the Envelope Editor V2 so teams can verify UI flows, persistence, and edge cases across native and embedded surfaces without flaky or duplicated test logic.

Core Features & Use Cases

  • Surface Normalization: A single TEnvelopeEditorSurface abstraction unifies Document, Template, Embedded Create, and Embedded Edit flows so tests run the same logical flow across four surfaces.
  • Fixture Helpers & Locators: Ready-made locator and action helpers simplify uploading PDFs, managing recipients, toggling settings, navigating steps, and asserting toasts.
  • Database Assertions & Persistence: Prisma-based assertions and explicit persistEmbeddedEnvelope handling allow reliable verification of server-side state and guard against parallel-test collisions.
  • Use Case: Add a new spec that tests recipient management and field placement, run it across all surfaces, and assert persistence using an externalId generated per test.

Quick Start

Create a new spec in the envelope-editor-v2 test folder, implement a runXxxFlow that uses the provided fixture helpers and externalId pattern, and run the envelope-editor-v2 tests with the repository test runner.

Frequently Asked Questions about envelope-editor-v2-e2e

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

FAQPage Schema
How do I write Playwright E2E tests for an envelope editor across embedded and native surfaces?

Playwright E2E tests for an envelope editor use a single surface normalization abstraction to unify document, template, embedded create, and embedded edit flows. Fixture helpers manage locators and actions like uploading PDFs and toggling settings, while Prisma assertions verify server-side persistence.

What is surface normalization in Playwright end-to-end testing?

Surface normalization in Playwright E2E testing uses a single abstraction to run identical logical test flows across document, template, embedded create, and embedded edit surfaces. This prevents duplicated test logic and ensures UI flows, persistence, and edge cases are verified consistently.

How do I assert database state in Playwright tests using Prisma?

Prisma-based assertions verify server-side state by querying the database directly during end-to-end tests. Combined with explicit embedded envelope persistence handling and per-test external IDs, these assertions reliably confirm data was saved without causing parallel-test collisions.

How do I prevent parallel-test collisions in Playwright E2E suites?

Parallel-test isolation in Playwright E2E suites is maintained by generating a unique externalId per test. This pattern explicitly handles embedded persistence, ensuring database assertions and locator actions do not collide when multiple tests run concurrently.

Does this E2E testing pattern support testing recipient management and field placement?

Yes, this E2E testing pattern supports recipient management and field placement through ready-made fixture helpers. These helpers simplify uploading PDFs, managing recipients, navigating steps, toggling settings, and asserting toasts across all envelope editor surfaces.