Merged
Conversation
…ncy=1 The multi-project browser config scenario is already covered by the e2e/browser-mode/multi-project-config fixture. With browser-projects removed, the only remaining browser example is browser-react, so the port conflict that required serial execution is gone.
9aoy
approved these changes
Mar 10, 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.
Summary
--browser.headlessCLI flags from all scripts — headless behavior is already controlled per-fixtureheadless: trueto the twomulti-project-configfixtures that were omittedCI || RSTEST_E2E_RUN_HEADEDso they are skipped locally by defaultBROWSER_HEADLESSenv var chain from e2e config/helpersexamples/browser-projects— the existingmulti-project-confige2e fixture already covers this scenariorstest.config.mtsprojects into an explicittest:examplesCI stepRSTEST_E2E_RUN_HEADEDin contributor and agent docsBackground
The
browser.headlessdefault isisCI(viastd-env). However, the e2e child processes explicitly clearCIandGITHUB_ACTIONSviadefaultEnvOverrides, soisCIis alwaysfalseinside fixtures — making explicitheadless: truein each fixture config essential.The previous
--browser.headlessflags in package scripts were therefore redundant. Two fixtures were missingheadless: trueand are now fixed. Removing the flags keeps the mechanism in one place and avoids confusion.Opt-in to headed tests locally