fix(browser-tests): start the landing app for the landing-page specs - #86
Merged
Conversation
The 01-landing-page specs target :3002, which the Playwright config never started — locally they quietly skipped, in CI (first scheduled run of browser-tests.yml) they failed with ERR_CONNECTION_REFUSED. Co-Authored-By: Claude Opus 5 (1M context) <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
1 participant
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.
First scheduled validation run of
browser-tests.ymlfailed on the 01-landing-page specs: they target:3002(the landing app), which the PlaywrightwebServerlist never started. Locally the absent server made them skip quietly; in CI they hard-fail withERR_CONNECTION_REFUSED. Adds the landing dev server to the managed set.Will re-dispatch the workflow after merge to confirm the suite goes green in CI.
🤖 Generated with Claude Code