Merge branch 'docs-mention-qa-executor-project' into 'master'

Mention gitlab-qa-executor in development documentation

See merge request https://gitlab.com/gitlab-org/omnibus-gitlab/-/merge_requests/7150

Merged-by: Evan Read <[email protected]>
Approved-by: Jason Plum <[email protected]>
Approved-by: Evan Read <[email protected]>
Co-authored-by: Achilleas Pipinellis <[email protected]>
Co-authored-by: Nailia Iskhakova <[email protected]>

Author: 3 people

doc/development/allure-test-report.md

@@ -46,7 +46,7 @@ The environment variables used in `qa-subset-test` are the same that are used in
 
 ## QA-SUBSET-TEST child pipeline
 
-This pipeline runs a subset of all the orchestrated tests using GitLab QA project which in turn uses allure gem to generate report source files for each test that is executed and stores the files in a common folder. Certain orchestrated jobs like `instance`, `decomposition-single-db`, `decomposition-multiple-db` and `praefect` run only smoke and reliable tests which intially used to run the entire suite.
+This pipeline runs a subset of all the orchestrated tests using GitLab QA project which in turn uses allure gem to generate report source files for each test that is executed and stores the files in a common folder. Certain orchestrated jobs like `instance`, `decomposition-single-db`, `decomposition-multiple-db` and `praefect` run only smoke and reliable tests which initially used to run the entire suite.
 
 ### e2e-test-report job
 

doc/development/setup.md

@@ -131,6 +131,10 @@ This ensures that your new work is behaving as expected, and not breaking anythi
    GITLAB_USERNAME=$USERNAME GITLAB_PASSWORD=$PASSWORD bundle exec bin/qa Test::Instance $DEV_INSTANCE_URL
    ```
 
+### Trigger QA pipeline against deployed instance
+
+If there is sustained network access to the deployed instance, you can trigger GitLab QA tests against the deployed instance using the [GitLab QA Executor](https://gitlab.com/gitlab-org/quality/gitlab-qa-executor) project. It contains CI configuration to run GitLab QA against self-managed GitLab environments with parallelization.
+
 ## Run specific chefspec tests
 
 You can also test your changes against the current tests (or to test your newly added tests).