Commit 88dffa45 authored by Toon Claes's avatar Toon Claes

Rename `package-qa` in docs

In gitlab-org/gitlab-ce!17807 the `package-qa` job was renamed to
`package-and-qa`. But it was not renamed in the docs. So this change
fixes that.
parent 57c5cb56
...@@ -22,7 +22,7 @@ You can find these nightly pipelines at [GitLab QA pipelines page][gitlab-qa-pip ...@@ -22,7 +22,7 @@ You can find these nightly pipelines at [GitLab QA pipelines page][gitlab-qa-pip
It is possible to run end-to-end tests (eventually being run within a It is possible to run end-to-end tests (eventually being run within a
[GitLab QA pipeline][gitlab-qa-pipelines]) for a merge request by triggering [GitLab QA pipeline][gitlab-qa-pipelines]) for a merge request by triggering
the `package-qa` manual action, that should be present in a merge request the `package-and-qa` manual action, that should be present in a merge request
widget. widget.
Manual action that starts end-to-end tests is also available in merge requests Manual action that starts end-to-end tests is also available in merge requests
......
...@@ -26,7 +26,7 @@ and corresponding views / partials / selectors in CE / EE. ...@@ -26,7 +26,7 @@ and corresponding views / partials / selectors in CE / EE.
Whenever `qa:selectors` job fails in your merge request, you are supposed to 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 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. using `package-and-qa` manual action, to test if everything works fine.
## How can I use it? ## How can I use it?
......
...@@ -40,7 +40,7 @@ the time it would take to build packages and test everything. ...@@ -40,7 +40,7 @@ the time it would take to build packages and test everything.
That is why when someone changes `t.text_field :login` to That is why when someone changes `t.text_field :login` to
`t.text_field :username` in the _new session_ view we won't know about this `t.text_field :username` in the _new session_ view we won't know about this
change until our GitLab QA nightly pipeline fails, or until someone triggers change until our GitLab QA nightly pipeline fails, or until someone triggers
`package-qa` action in their merge request. `package-and-qa` action in their merge request.
Obviously such a change would break all tests. We call this problem a _fragile Obviously such a change would break all tests. We call this problem a _fragile
tests problem_. tests problem_.
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment