Open
Conversation
- Adds Playwright setup, teardown, and inv command - Adds tests across Chromium, Webkit, and Gecko - Adds dedicated database volume for E2E tests - Seeds database with test data during runs - Adds a few organization tests for validation - Disables rate limits when running locally - Updates README with E2E testing instructions
Since this is an expensive and time-consuming operation, we just want to make sure our `master` branch is protected against incoming changes that fail E2E. For workflows where we're merging into a feature branch, this helps us stay nimble while ensuring the feature is stable.
mitchelljkotler
approved these changes
Feb 11, 2026
Member
mitchelljkotler
left a comment
There was a problem hiding this comment.
This looks good to me - I'd be interested in if it runs on GitHub actions so it can be run automatically
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
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.
I used Claude Code to help me setup and author a basic suite of E2E tests for our organization pages.
Right now, these only run locally after setting up your local dev environment.
I haven't yet investigated whether these can run in a GitHub Action as part of our CI process.I've validated this, and E2E tests successfully run in GitHub Actions! 🎉 See the action log below.The tests aren't lightning fast, but they're not sluggish. This suite of 34 tests takes about 60s to run on my local machine, and about 90s to run on GitHub Actions once the environment was built—there may be some performance optimizations we can make to our runner config.