browser_ui/6_release/pages/pages_pipeline_spec.rb | Release Pages runs a Pages-specific pipeline
Problem
No end-to-end verification of Pages functionality currently exists
From gitlab-org/gitlab-qa#411:
We should add tests, either in
gitlab-qa
orgitlab-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.
Proposal
Add orchestrated test to configure pages and test creation of accessible Pages site
A test should be written for each of the following (barring sufficient feature/integration tests):
Create
- Creating a Pages-accessible website from a pre-existing template
- Creating a Pages-accessible website using a new template
- Creating a Pages-accessible website using a
.gitlab-ci.yml
template - Creating a Pages-accessible website using a new
.gitlab-ci.yml
file
Read
- Accessing an existing Pages site correctly
- Custom Domains / TLS certificates
- Let's Encrypt integration
- Redirects(?)
Update
- Accessing an existing Pages site, then updating content.
Delete
- Accessing an existing Pages site, then tearing down.