envelope-editor-v2-e2e

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill standardizes and accelerates the development and maintenance of Playwright-based end-to-end tests for the Envelope Editor V2, enabling teams to create, debug, and extend tests across document, template, and embedded editor surfaces.

Core Features & Use Cases

  • E2E test suite organization for envelope-editor-v2 located at packages/app-tests/e2e/envelope-editor-v2 with surface-agnostic helpers and fixtures.
  • Provides consistent flows across four surfaces: document, template, embedded create, embedded edit.
  • Use cases include adding recipients, settings, and validating database persistence via Prisma fixtures.

Quick Start

Run a Playwright test suite for envelope-editor-v2 tests, ensuring a unique externalId for each run.

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 the Envelope Editor V2?

You can write Playwright E2E tests for the Envelope Editor V2 by adding tests to packages/app-tests/e2e/envelope-editor-v2, utilizing reusable testing surface abstractions and fixtures to standardize test creation.

What surfaces are covered by Envelope Editor V2 E2E testing?

Envelope Editor V2 E2E testing covers four distinct surfaces: document, template, embedded create, and embedded edit, providing consistent cross-surface flows for comprehensive test coverage.

How do I validate database persistence in Playwright E2E tests?

You validate database persistence in Playwright E2E tests by using Prisma fixtures to assert database states, tracking data with a unique externalId for each test run to ensure isolated verification.

Can I use this to debug existing Envelope Editor V2 Playwright tests?

Yes, you can use this to debug existing Envelope Editor V2 Playwright tests, as it supports creating, modifying, debugging, and extending tests across document, template, and embedded editor surfaces.

How do I add recipients and settings in Envelope Editor V2 E2E tests?

You add recipients and settings in Envelope Editor V2 E2E tests by leveraging the provided surface-agnostic helpers and fixtures, ensuring consistent flows across document, template, and embedded editor environments.

Does Envelope Editor V2 E2E testing require TypeScript and Playwright?

Yes, Envelope Editor V2 E2E testing requires TypeScript and Playwright, automating end-to-end testing with TypeScript implementations and providing reusable abstractions for cross-surface test flows.