kotovalexarian-likes-gitlab
/
gitlab-org--gitlab-foss
1
0
Fork 0
Code Releases Activity

Rephrase paragraph about e2e tests in merge requests in docs

This commit is contained in:
Grzegorz Bizon 2018-01-05 15:32:41 +01:00
parent e8acb3f117
commit 8bdc6c74e8
1 changed files with 6 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
doc/development/testing_guide/end_to_end_tests.md
View File

@ -20,15 +20,13 @@ You can find these nightly pipelines at [GitLab QA pipelines page][gitlab-qa-pip
### Testing code in merge requests
It is also possible to trigger build of GitLab packages and then pass these
package to GitLab QA to run tests in a [pipeline][gitlab-qa-pipelines].
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
the `package-qa` manual action, that should be present in a merge request
widget.
Developers can trigger the `package-qa` manual action, that should be present in
the merge request widget.
It is also possible to trigger Gitlab QA pipeline from merge requests in
Omnibus GitLab project. You can find a manual action that is similar to
`package-qa`, mentioned above, in your Omnibus-related merge requests as well.
Mmanual action that starts end-to-end tests is also available in merge requests
in Omnibus GitLab project.
Below you can read more about how to use it and how does it work.