diff options
author | Grzegorz Bizon <grzesiek.bizon@gmail.com> | 2018-01-12 13:04:41 +0300 |
---|---|---|
committer | Grzegorz Bizon <grzesiek.bizon@gmail.com> | 2018-01-12 13:04:41 +0300 |
commit | 31656239a6983377a8c7f46c52079a653601e606 (patch) | |
tree | af39213bfc7b708216211f0e7f7362aee06b8aa8 /qa | |
parent | 8ab611509adf841008bf0e4ecaffaf0e58d8b7fe (diff) |
Add a note about GitLab QA page objects validator to docs
Diffstat (limited to 'qa')
-rw-r--r-- | qa/README.md | 11 |
1 files changed, 11 insertions, 0 deletions
diff --git a/qa/README.md b/qa/README.md index 8fa04e80825..3c1b61900d9 100644 --- a/qa/README.md +++ b/qa/README.md @@ -17,6 +17,17 @@ against any existing instance. 1. Along with GitLab Docker Images we also build and publish GitLab QA images. 1. GitLab QA project uses these images to execute integration tests. +## Validating GitLab views / partials / selectors in merge requests + +We recently added a new CI job that is going to be triggered for every push +event in CE and EE projects. The job is called `qa:selectors` and it will +verify coupling between page objects implemented as a part of GitLab QA +and corresponding views / partials / selectors in CE / EE. + +Whenever `qa:selectors` job fails in your merge request, you are supposed to +fix [page objects](qa/page/README.md). You should also trigger end-to-end tests +using `package-qa` manual action, to test if everything works fine. + ## How can I use it? You can use GitLab QA to exercise tests on any live instance! For example, the |