Add DRUPAL_TEST_WEBDRIVER_CHROME_ARGS for Nightwatch tests with login #27
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.
Edit: tl;dr Please see the test results, where Drupal core's
tests/Drupal/Nightwatch/Tests/loginTest.js
fails to run against the main branch but passes with the additional configuration in place.I followed the Nightwatch setup steps in the README.
What I'm seeing is Nightwatch tests that log in to Drupal fail to execute. After I add the following line to
.ddev/config.selenium-standalone-chrome.yaml
and runddev start
, these tests run smoothly.- DRUPAL_TEST_WEBDRIVER_CHROME_ARGS=--disable-gpu --headless --no-sandbox --disable-dev-shm-usage
For example, run:
Log output (before making this change):
And this different log message that I got at another point while testing:
Finally, log with the changes in place:
See also:
Or (as far as I can tell) any tests that call
drupalLoginAsAdmin()
ordrupalLogin()
.I believe my ddev setup is fairly standard. I ran
ddev config
and nothing changed: