feat: add BROWSER_ALWAYS_START_WEBSERVER env var
#156
Merged
Conversation
This file contains 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
kbond
force-pushed
the
always-start-webserver
branch
from
b549378
to
8d06fef
Compare
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.
This is a fix for the problem/hack described here: https://symfonycasts.com/screencast/last-stack/testing#loading-a-test-dev-server
When Panther goes to start a webserver, if one is already running for the project in the Symfony CLI, it does not start. When this env var is set to
1, this forces Panther to start a new webserver anyway.Further, it is likely you want your Panther webserver running the same environment as your test suite. When this env var is set to
1, we setPANTHER_APP_ENV = APP_ENV(likelytest).