envelope-editor-v2-e2e

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

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/LKPioniere/lohnlab-esign --skill envelope-editor-v2-e2e-lkpioniere
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: envelope-editor-v2-e2e
Source: https://github.com/LKPioniere/lohnlab-esign/tree/main/.agents/skills/envelope-editor-v2-e2e
Command: npx skills add https://github.com/LKPioniere/lohnlab-esign --skill envelope-editor-v2-e2e-lkpioniere

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enables automated end-to-end testing of the Envelope Editor V2 using Playwright, ensuring robust validation of create, modify, and verify flows across surfaces.

Core Features & Use Cases

  • End-to-end Playwright tests for Envelope Editor V2 across document, template, embedded create, and embedded edit surfaces
  • Shared test architecture with fixtures for opening editors, uploading PDFs, and asserting persistent state in the database
  • Use case coverage including attachments, recipients, fields/items, and settings across native and embedded contexts

Quick Start

Run the Envelope Editor V2 Playwright tests from the repository's packages/app-tests/e2e/envelope-editor-v2 directory using your 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 automate end-to-end testing for an envelope editor using Playwright?

Automate envelope editor end-to-end testing by using Playwright to validate creation, modification, and verification flows across document, template, and embedded create/edit scenarios. Tests utilize fixtures to open editors, upload assets, and assert database state via Prisma.

What is the best way to test embedded envelope creation and modification flows in e2e tests?

Testing embedded envelope creation and modification flows requires Playwright test fixtures to open the editor surfaces, upload necessary PDFs, and apply settings. This approach validates recipients, fields, and attachments across all embedded contexts.

How do I verify envelope editor database state after running e2e tests?

Verify envelope editor database state after e2e tests by utilizing Prisma utilities within your Playwright test architecture. These utilities persist embedded envelopes and assert the final state of attachments, recipients, and fields in the database.

Can I use this Playwright testing framework to validate attachments and recipients across different editor surfaces?

Yes, this Playwright testing framework validates attachments, recipients, fields, and settings across document, template, embedded create, and embedded edit surfaces. Shared test architecture ensures robust coverage for all four native and embedded contexts.

Do I need a specific test project structure to run envelope editor Playwright tests?

Yes, running envelope editor Playwright tests requires a Playwright-based test project structure with test fixtures. This setup is necessary to open editors, upload PDF assets, and execute database assertions from the designated e2e directory.