Add QA tests for gitlab-pages functionality
Problem to solve
In gitlab-com/gl-infra/delivery#497 (comment 224907219) we identified a test gap that I've been implicitly aware of for some time: the interface between gitlab-rails
and gitlab-pages
has no automated tests at all.
Proposal
We should add tests, either in gitlab-qa
or gitlab-rails
, that configures Pages, including major features like access control or HTTPS, and checks that the Pages sites are created as expected and access control works as expected.
The current interface between Pages and Rails is a config.json
file written by Rails and read by Pages. Writing the file is tested in Rails, and reading it is tested in Pages, but if we make a mistake when changing this interface, the first time we'll know about it is when Pages breaks in production.
This page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.