test: add Playwright e2e setup and initial editor tests - #93
Merged
Conversation
vitormattos
approved these changes
Sep 9, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Part of #82: first of the smaller PRs I mentioned, just the Playwright base so I can add axe and CI on top later.
Adds @playwright/test + Chromium, a config that runs against the demo on :5173 (Chromium only, trace on first retry), test:e2e scripts, and a few tests in e2e/: demo loads, load a PDF, add a signature. Also gitignored the Playwright output folders.
Next PRs: axe checks, CI workflow, the rest of the interactions.
Lint's clean, tests pass locally. The contributing guide mentions a CHANGELOG.md but there isn't one in the repo, so I skipped it, can add one if you want.