Repository navigation
Run browser tests with Selenium in CI - #178
Merged
Merged
Conversation
The unit tests cannot tell when the page loads but a button does nothing, which is the easiest way to break Compare: one blocked inline handler or one missing data-action entry. Until now that could only be caught by clicking through the page by hand. A separate workflow now builds the site and drives it in headless Chrome with Selenium, serving it with the real Content-Security-Policy. The tests go through the main flows and fail on any browser error or CSP violation. Linting and unit tests stay in their own workflow, so a lint failure and a broken page show up as separate checks. Assisted-by: Claude Opus 5.5 noreply@anthropic.com
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.
The unit tests cannot tell when the page loads but a button does nothing, which is the easiest way to break Compare: one blocked inline handler or one missing data-action entry. Until now that could only be caught by clicking through the page by hand.
A separate workflow now builds the site and drives it in headless Chrome with Selenium, serving it with the real Content-Security-Policy. The tests go through the main flows and fail on any browser error or CSP violation. Linting and unit tests stay in their own workflow, so a lint failure and a broken page show up as separate checks.
Assisted-by: Claude Opus 5.5 noreply@anthropic.com