You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Our test environment with regards to CI is messy. We have Drupal tests, Cypress, Playwright for dev environments (e2e testing), and Playwright for test environments (outside testing). We really should just have two (Drupal and Playwright). In addition, for Playwright tests, we should standardize on our docker-compose.test.yml infrastructure as that was designed for setup, modifying, and tearing down test environments, without impacting our (local) dev environments.
Optionally we might look at Gitlab's container registry to cache Docker images (we can also pull these images for use locally). We already do this in Github Actions (build-drupal-image essentially caches the resulting image to /tmp/image.tar). Note that we would ideally build these images via a separate Gitlab pipeline (this can be a separate ticket).
Likely this work would have to be broken out further as we fully transition to Gitlab CI.
Acceptance criteria
We have one Gitlab pipeline for tests
We have one Gitlab stage for Drupal testing only (using our test environment)
We have one Gitlab stage for Playwright only (using our test environment)
If we have not deprecated Cypress yet, we have one Gitlab stage for Cypress (using our test environment)
Documentation around testing has been updated
The text was updated successfully, but these errors were encountered:
Description
Our test environment with regards to CI is messy. We have Drupal tests, Cypress, Playwright for dev environments (e2e testing), and Playwright for test environments (outside testing). We really should just have two (Drupal and Playwright). In addition, for Playwright tests, we should standardize on our docker-compose.test.yml infrastructure as that was designed for setup, modifying, and tearing down test environments, without impacting our (local) dev environments.
Optionally we might look at Gitlab's container registry to cache Docker images (we can also pull these images for use locally). We already do this in Github Actions (
build-drupal-image
essentially caches the resulting image to/tmp/image.tar
). Note that we would ideally build these images via a separate Gitlab pipeline (this can be a separate ticket).Likely this work would have to be broken out further as we fully transition to Gitlab CI.
Acceptance criteria
The text was updated successfully, but these errors were encountered: