Resolve "Improve Drupal Validation Pipelines with consistent approach"
Description
This merge request adds the web-team testing jobs for drupal sites.
In detail, following the specifications detailed in the related design issue the pipeline has now three more jobs in the E2E test stage:
- A manual job called
E2E test-existing-site-selenium
that has no dependeces and allows failures to not impact in the result of the pipelin that can be used to test any existing drupal site just passing the site url in the variableSITENAME
- An automatic job called
E2E-test-newsite-selenium
which depends on theinfrastructure-test-newsite-provision
that tests the new site created in the previous job. - An automatic job called
E2E-test-clonesite-selenium
which depends on theinfrastructure-test-clonesite-provision
that tests the cloned site in the previous job.
Here you can see the new structure and the dependencies between the jobs of the pipeline:
Usage
All the new jobs have a common structure:
- The latest docker image available of the Automated testing suite is pulled from the gitlab-registry. This ensures a clear division and a modular structure between the drupal distribution and the testing suite.
- The 'SITENAME' variable that indicates the site to test is populated manually by the user or inherited by the setting file.
- The image is executed testing the basic modules functionalities of the site thorugh selenium. Please note that some customisations in the html can affect the result of the tests one example of this is the 'https://procurement.web.cern.ch' site
Related repos:
Related issues:
Docs
You can find more documentation about the testing suite on the readme of the project.
Closes #42
Edited by Lorenzo Del Pianta