skills.rest
GitLaw-co
GitLaw-coOFFICIAL
Explore all skills by this author →
GitHub

envelope-editor-v2-e2e

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

Updated Nov 24, 2025
Search Tags:#automation#testing#qa#playwright#e2e-testing#envelope-editor
One-click install
npx skills add https://github.com/GitLaw-co/documenso --skill envelope-editor-v2-e2e-gitlaw-co
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: envelope-editor-v2-e2e
Source: https://github.com/GitLaw-co/documenso/tree/main/.agents/skills/envelope-editor-v2-e2e
Command: npx skills add https://github.com/GitLaw-co/documenso --skill envelope-editor-v2-e2e-gitlaw-co

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Writing and maintaining robust Playwright end-to-end tests for the Envelope Editor V2 can be time-consuming and error-prone without a structured approach.

Core Features & Use Cases

  • Provides a standardized pattern for testing envelope workflows across document, template, and embedded surfaces.
  • Includes fixtures and helpers to drive envelope actions (uploading PDFs, managing recipients, and verifying persistence).
  • Supports end-to-end validation of settings, field edits, and data persistence across multiple surfaces.

Quick Start

Run the tests to validate end-to-end envelope editor flows across document, template, and embedded surfaces.

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 structure Playwright E2E tests for an envelope editor workflow?▼

Structure Playwright E2E tests for envelope editor workflows using standardized fixtures, surface abstractions, and database assertions with Prisma to validate document, template, and embedded surfaces consistently.

What is the best way to test PDF uploads and recipient management in Playwright?▼

Test PDF uploads and recipient management in Playwright by using helpers that drive envelope actions, verifying settings, field edits, and data persistence across multiple editor surfaces.

Does this Playwright testing approach support parallel runs for envelope workflows?▼

Yes, it supports parallel runs for envelope workflows by generating unique external IDs for each test, preventing data collisions during automated end-to-end execution.

Can I validate data persistence across sessions in Playwright without direct database queries?▼

Validating data persistence across sessions requires database assertions using Prisma to confirm that envelope settings, field edits, and recipient data are saved and maintained correctly.

How do I test embedded envelope creation surfaces differently from standard document surfaces?▼

Test embedded envelope creation surfaces by applying surface abstractions in your Playwright fixtures to handle the distinct create and edit paths for documents, templates, and embedded contexts.

Related Skills

Explore More Software Engineering Skills→
documensodocumenso
14.3k

envelope-editor-v2-e2e

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

Official
Advanced
vddgmbhvddgmbh

envelope-editor-v2-e2e

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

Official
Advanced
oaknationaloaknational
31

testing

Run and report Jest, React Testing Library, and Playwright tests for Oak AI projects.

Official
Intermediate
JaiminVadadoriyaJaiminVadadoriya
1

playwright-migration

Map Cypress or Selenium commands to Playwright for incremental migration.

Community
Advanced