Continue #58 - use official images (seleniarm)

[ol0lll]

• Update docker-compose.selenium-chrome.yaml
• Bump Drupal core used in testing
• Remove -v option to phpunit. Add a composer.json
• Remove unwanted composer installer cruft
• Use seleniarm
• Use current mink args, see https://git.drupalcode.org/project/gitlab_templates/-/blob/main/includes/include.drupalci.main.yml\?ref_type\=heads\#L46

[stasadev]

Rebased to resolve conflicts.

There are now artifacts (for the nightwatch and others) in the tests, so it's easier to see what went wrong: https://github.com/ddev/ddev-selenium-standalone-chrome/actions/runs/16074002275?pr=65

[stasadev]

From what I see, this is the only PR that does not hang, because it fails much faster 🙂

[weitzman]

Thanks for the tip. I moved the test suite to Drupal 11 and merged that into this PR. We are still seeing errors unfortunately.

FYI, the composer.json added here is not needed. The test suite installs Drupal and dependencies.

[kentr]

The nightwatch errors of "An error occurred while creating a new Selenium Server session ..." may be due to missing / incorrect env variable(s).

This change in config.selenium-standalone-chrome.yaml removed the nightwatch errors for me (on M3 Mac):

   - DRUPAL_TEST_WEBDRIVER_HOSTNAME=selenium-chrome
   - DRUPAL_TEST_WEBDRIVER_PORT=4444
   - DRUPAL_TEST_WEBDRIVER_PATH_PREFIX=/wd/hub
-  - DRUPAL_TEST_WEBDRIVER_CHROME_ARGS=--disable-gpu --headless --no-sandbox --disable-dev-shm-usage
+  - DRUPAL_TEST_WEBDRIVER_CHROME_ARGS='--disable-dev-shm-usage --disable-gpu --headless --dns-prefetch-disable'
+  - DRUPAL_TEST_WEBDRIVER_W3C=true
   - DRUPAL_TEST_CHROMEDRIVER_AUTOSTART=false
   - DRUPAL_NIGHTWATCH_SEARCH_DIRECTORY=../
   - DRUPAL_NIGHTWATCH_IGNORE_DIRECTORIES=node_modules,vendor,.*,sites/*/files,sites/*/private,sites/simpletest

I arrived at this from seeing that Drupal's nightwatch.conf.js gets the configuration from environment variables and using the values that are set by Drupal's gitlab pipeline.

Also works with --no-sandbox in DRUPAL_TEST_WEBDRIVER_CHROME_ARGS.

[kentr]

FWIW, the image selenium/standalone-chromium:127.0 also appears to work, at least for nightwatch tests. No failures or errors from a full test run.

[weitzman]

See #49