Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Gitlab: consolidate tests in CI #1795

Open
5 tasks
jamestranovich-noaa opened this issue Sep 18, 2024 · 2 comments
Open
5 tasks

Gitlab: consolidate tests in CI #1795

jamestranovich-noaa opened this issue Sep 18, 2024 · 2 comments
Labels
DX Developer Experience Eng Gitlab
Milestone

Comments

@jamestranovich-noaa
Copy link
Collaborator

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

  • 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
@colinmurphy01
Copy link
Collaborator

I assume this is a solve for #1677?

@jamestranovich-noaa
Copy link
Collaborator Author

Yes! Apologies, I missed that ticket entirely.

@colinmurphy01 colinmurphy01 added the DX Developer Experience label Sep 20, 2024
@colinmurphy01 colinmurphy01 modified the milestones: V3, V2 Sep 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
DX Developer Experience Eng Gitlab
Projects
Status: Now - Expand - V2
Development

No branches or pull requests

2 participants