envelope-editor-v2-e2e

Automating Playwright E2E tests for multiple editor surfaces involves using a unified test architecture with helper fixtures to seed users and manage envelopes across document, template, and embedded workflows. This ensures consistent test execution across different UI states.

To verify UI actions persist correctly during Playwright end-to-end testing, you can use Prisma for database validation. This connects your test assertions directly to the database state to confirm that actions like updating settings are successfully saved.

Yes, you can use fixtures like openEmbeddedEnvelopeEditor to handle surface differences in Playwright. These fixtures manage tokens and embedded persistence helpers to reconcile differences such as the Add Myself button and toast expectations across workflows.

The best way to test envelope editor workflows across document and embedded create surfaces is by applying reusable flow functions within a unified Playwright test architecture. This approach handles surface differences while validating recipient additions and envelope persistence.

You need Prisma to run E2E tests for envelope editor workflows if you require database validation to ensure UI actions persist correctly. It is utilized specifically within the test architecture to verify that data mutations match the expected state.