diff options
| author | Grzegorz Bizon <grzesiek.bizon@gmail.com> | 2017-12-20 14:05:02 +0100 |
|---|---|---|
| committer | Grzegorz Bizon <grzesiek.bizon@gmail.com> | 2018-01-02 13:39:09 +0100 |
| commit | 1f50eb4f57ae14336a677f53d9a2c9501033f966 (patch) | |
| tree | 6e03d2923e01df0fe563bda74968dfbccdac359a | |
| parent | 81dcd8ed8f71968215c7e776da482e83823c8b74 (diff) | |
| download | gitlab-ce-1f50eb4f57ae14336a677f53d9a2c9501033f966.tar.gz | |
Add docs about end-to-end testing / GitLab QA tests
| -rw-r--r-- | doc/development/testing_guide/end_to_end_tests.md | 42 | ||||
| -rw-r--r-- | doc/development/testing_guide/index.md | 8 |
2 files changed, 50 insertions, 0 deletions
diff --git a/doc/development/testing_guide/end_to_end_tests.md b/doc/development/testing_guide/end_to_end_tests.md new file mode 100644 index 00000000000..87a21b9f7fc --- /dev/null +++ b/doc/development/testing_guide/end_to_end_tests.md @@ -0,0 +1,42 @@ +# End-to-End Testing + +## What is End-to-End testing? + +End-to-End testing is a strategy used to check whether your application works +as expected across entire software stack and architecture, including +integration of all microservices and components that are supposed to work +together. + +## How do we test GitLab? + +We use [Omnibus GitLab][omnibus-gitlab] to build GitLab packages and then we +test these packages using [GitLab QA][gitlab-qa] project, which is entirely +black-box, click-driven testing framework. + +### Testing nightly builds + +We run scheduled pipeline each night to test nightly builds created by Omnibus. +You can find these nightly pipelines at [GitLab QA pipelines page][gitlab-qa-pipelines]. + +### Testing code in merge requests + +It is also possible to trigger packages build and [GitLab QA pipeline][gitlab-qa-pipelines] +using a manual action that should be present in the merge request widget on +your merge request. Look for `package-qa` manual action. + +Below you can read more about how to use it and how does it work. + +## How does it work? + +We are using _multi-project pipelines_ to run end-to-end tests. + +## How do I test my code? + +## How do I contribute? + +## Where can I ask for help? + + +[omnibus-gitlab]: https://gitlab.com/gitlab-org/omnibus-gitlab +[gitlab-qa]: https://gitlab.com/gitlab-org/gitlab-qa +[gitlab-qa-pipelines]: https://gitlab.com/gitlab-org/gitlab-qa/pipelines diff --git a/doc/development/testing_guide/index.md b/doc/development/testing_guide/index.md index 65386f231a0..4ca192aee7e 100644 --- a/doc/development/testing_guide/index.md +++ b/doc/development/testing_guide/index.md @@ -65,6 +65,13 @@ Everything you should know about how to test Rake tasks. --- +## [End-to-end tests](end_to_end_tests.md) + +Everything you should know about how to run end-to-end tests, also known as +[GitLab QA][gitlab-qa] tests. + +--- + ## Spinach (feature) tests GitLab [moved from Cucumber to Spinach](https://github.com/gitlabhq/gitlabhq/pull/1426) @@ -89,3 +96,4 @@ test should be re-implemented using RSpec instead. [Capybara]: https://github.com/teamcapybara/capybara [Karma]: http://karma-runner.github.io/ [Jasmine]: https://jasmine.github.io/ +[gitlab-qa]: https://gitlab.com/gitlab-org/gitlab-qa |