Disable SCRIPT_DEBUG for local e2e tests run #14638
Merged
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.
Description
There is this issue that e2e tests run locally will fail at the moment because
SCRIPT_DEBUG
is set totrue
and we need to fix React warnings. It is disabled on Travis and this PR does it for local env as well.In theorhy we should need only:
However, I run into some issues where I could update
SCRIPT_DEBUG
forwordpress
container but notwordpress_e2e_tests
container so I applied a few changes based on this Stack Overflow page:https://stackoverflow.com/questions/50999848/how-to-run-wp-cli-in-docker-compose-yml/51001043#51001043
I also removed
bin/run-e2e-tests.sh
file which is no longer in use.How has this been tested?
npm run test-e2e
locally.