gitlab-qa 7.12.0 → 7.13.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 6b9dcb4935c0cc27ed0c101098a6ef19a63db8697aec420844b499b614190669
-  data.tar.gz: fff48c4b8887be1b5915885bf6698d1b34c289c794dafab5d12f63ce1ec52262
+  metadata.gz: f5669f64ddb8066f756cfa50165883c6615a787810e566d19108e71bfc088527
+  data.tar.gz: cb0af955d1b67846a9b738b26b90cdd5babc8b8b2ad2b4ed3c70b03513ef0acf
 SHA512:
-  metadata.gz: 98c19eeafde92cb7931460363ef0f29ee664af8e7e74ff22840b43b797ae24cac0adb3511c395810f33d017d0af3f3aa4618739a58f3cc111aed2046a8c04afc
-  data.tar.gz: c18900856b311a2a8f49260620684f276f69bf2dab35c0fdc1befe41572a1f92b549f00798646fb6c50b1d8fc9d578cc59721978cd5459a3bb45307dabf79919
+  metadata.gz: 74a3906216c1efcffaa0761cefd932d5a06dd68878ca4940eaffd12e80882250cd58b0667ab02546ebeb167afd1b680e2f0a179498a4136dfd05dc2dae1227b8
+  data.tar.gz: 85b86bd17e11d3a1cb8a9264c67ebf5be8a59a1c32a094432a53703fd38dadeeb7d6948881a8984a976a16411796f8a1498b8e8b4360152c88b066dde40484df

data/docs/what_tests_can_be_run.md

@@ -1,5 +1,7 @@
 # What tests can be run?
+
 [[_TOC_]]
+
 ## The two types of QA tests
 
 First of all, the first thing to choose is whether you want to run orchestrated
@@ -245,8 +247,8 @@ instance-level tests against it.
 To run tests against the GitLab containers, a GitLab QA (`gitlab/gitlab-qa`)
 container is spun up and tests are run from it by running the `Test::Instance`
 scenario (located under
-[`gitlab-org/gitlab-ce@qa/qa/scenario/test/instance.rb`][test-instance] in the
-GitLab CE project).
+[`gitlab-org/gitlab/qa/qa/scenario/test/instance.rb`][test-instance] in the
+GitLab project).
 
 Example:
 
@@ -370,8 +372,8 @@ that LDAP-related features work as expected.
 To run tests against the GitLab containers, a GitLab QA (`gitlab/gitlab-qa`)
 container is spun up and tests are run from it by running the
 `Test::Integration::LDAPNoTLS` scenario (located under
-[`gitlab-org/gitlab-ce@qa/qa/scenario/test/integration/ldap_no_tls.rb`][test-integration-ldap-no-tls]
-in the GitLab CE project).
+[`gitlab-org/gitlab/qa/qa/scenario/test/integration/ldap_no_tls.rb`][test-integration-ldap-no-tls]
+in the GitLab project).
 
 In EE, both the GitLab standard and LDAP credentials are needed:
 
@@ -393,7 +395,7 @@ $ export EE_LICENSE=$(cat /path/to/Geo.gitlab_license)
 $ gitlab-qa Test::Integration::LDAPNoTLS EE
 ```
 
-[test-integration-ldap-no-tls]: https://gitlab.com/gitlab-org/gitlab-ce/blob/master/qa/qa/scenario/test/integration/ldap_no_tls.rb
+[test-integration-ldap-no-tls]: https://gitlab.com/gitlab-org/gitlab/blob/master/qa/qa/scenario/test/integration/ldap_no_tls.rb
 
 ### `Test::Integration::LDAPTLS CE|EE|<full image address>`
 
@@ -411,8 +413,8 @@ that LDAP-related features work as expected.
 To run tests against the GitLab containers, a GitLab QA (`gitlab/gitlab-qa`)
 container is spun up and tests are run from it by running the
 `Test::Integration::LDAPTLS` scenario (located under
-[`gitlab-org/gitlab-ce@qa/qa/scenario/test/integration/ldap_tls.rb`][test-integration-ldap-tls]
-in the GitLab CE project).
+[`gitlab-org/gitlab/qa/qa/scenario/test/integration/ldap_tls.rb`][test-integration-ldap-tls]
+in the GitLab project).
 
 In EE, both the GitLab standard and LDAP credentials are needed:
 
@@ -434,8 +436,8 @@ $ export EE_LICENSE=$(cat /path/to/Geo.gitlab_license)
 $ gitlab-qa Test::Integration::LDAPTLS EE
 ```
 
-[test-integration-ldap-tls]: https://gitlab.com/gitlab-org/gitlab-ce/blob/master/qa/qa/scenario/test/integration/ldap_tls.rb
-[test-integration-ldap-tls-certs]: https://gitlab.com/gitlab-org/gitlab-ce/blob/master/tls_certificates/gitlab
+[test-integration-ldap-tls]: https://gitlab.com/gitlab-org/gitlab/blob/master/qa/qa/scenario/test/integration/ldap_tls.rb
+[test-integration-ldap-tls-certs]: https://gitlab.com/gitlab-org/gitlab/blob/master/tls_certificates/gitlab
 
 ### `Test::Integration::LDAPNoServer EE|<full image address>`
 
@@ -504,9 +506,9 @@ using SAML.
 
 To run tests against the GitLab containers, a GitLab QA (`gitlab/gitlab-qa`)
 container is spun up and tests are run from it by running the
-`Test::Integration::InstanceSAML` scenario (located under [`gitlab-org/gitlab-ce@qa/qa/scenario/test/integration/instance_saml.rb`][test-integration-instance-saml] in the GitLab CE project).
+`Test::Integration::InstanceSAML` scenario (located under [`gitlab-org/gitlab-ce@qa/qa/scenario/test/integration/instance_saml.rb`][test-integration-instance-saml] in the GitLab project).
 
-[test-integration-instance-saml]: https://gitlab.com/gitlab-org/gitlab-ce/blob/master/qa/qa/scenario/test/integration/instance_saml.rb
+[test-integration-instance-saml]: https://gitlab.com/gitlab-org/gitlab/blob/master/qa/qa/scenario/test/integration/instance_saml.rb
 
 **Required environment variables:**
 
@@ -531,8 +533,8 @@ Mattermost server (see `Test::Instance::Image` above).
 To run tests against the GitLab container, a GitLab QA (`gitlab/gitlab-qa`)
 container is spun up and tests are run from it by running the
 `Test::Integration::Mattermost` scenario (located under
-[`gitlab-org/gitlab-ce@qa/qa/scenario/test/integration/mattermost.rb`][test-integration-mattermost]
-in the GitLab CE project).
+[`gitlab-org/gitlab/qa/qa/scenario/test/integration/mattermost.rb`][test-integration-mattermost]
+in the GitLab project).
 
 **Required environment variables:**
 
@@ -549,7 +551,7 @@ $ export EE_LICENSE=$(cat /path/to/Geo.gitlab_license)
 $ gitlab-qa Test::Integration::Mattermost EE
 ```
 
-[test-integration-mattermost]: https://gitlab.com/gitlab-org/gitlab-ce/blob/master/qa/qa/scenario/test/integration/mattermost.rb
+[test-integration-mattermost]: https://gitlab.com/gitlab-org/gitlab/blob/master/qa/qa/scenario/test/integration/mattermost.rb
 
 ### `Test::Integration::Packages CE|EE|<full image address>`
 
@@ -668,8 +670,8 @@ against it.
 To run tests against the GitLab instance, a GitLab QA (`gitlab/gitlab-qa`)
 container is spun up and tests are run from it by running the
 `Test::Instance` scenario (located under
-[`gitlab-org/gitlab-ce@qa/qa/scenario/test/instance.rb`][test-instance] in the
-in the GitLab CE project).
+[`gitlab-org/gitlab/qa/qa/scenario/test/instance.rb`][test-instance] in the
+in the GitLab project).
 
 Example:
 
@@ -695,8 +697,8 @@ works as expected by running tests against it.
 To run tests against the GitLab instance, a GitLab QA (`gitlab/gitlab-qa`)
 container is spun up and tests are run from it by running the
 `Test::Instance` scenario (located under
-[`gitlab-org/gitlab-ce@qa/qa/scenario/test/instance.rb`][test-instance] in the
-in the GitLab CE project).
+[`gitlab-org/gitlab/qa/qa/scenario/test/instance.rb`][test-instance] in the
+in the GitLab project).
 
 **Required environment variables:**
 
@@ -723,6 +725,42 @@ $ export GITLAB_PASSWORD="$GITLAB_QA_PASSWORD"
 $ gitlab-qa Test::Instance::Staging
 ```
 
+### `Test::Instance::StagingRef`
+
+This scenario tests that the [`Staging Ref`](https://staging-ref.testbed.gitlab.net)
+works as expected by running tests against it.
+
+To run tests against the GitLab instance, a GitLab QA (`gitlab/gitlab-qa`)
+container is spun up and tests are run from it by running the
+`Test::Instance` scenario (located under
+[`gitlab-org/gitlab/qa/qa/scenario/test/instance.rb`][test-instance] in the
+in the GitLab project).
+
+**Required environment variables:**
+
+- `GITLAB_QA_ACCESS_TOKEN`: A valid personal access token with the `api` scope.
+  This is used to retrieve the version that staging is currently running.
+  Staging Ref QA users credentials can be found in the shared GitLab QA 1Password vault.
+
+**Optional environment variables:**
+
+- `GITLAB_QA_DEV_ACCESS_TOKEN`: A valid personal access token for the
+  `gitlab-qa-bot` on `dev.gitlab.org` with the `registry` scope.
+  This is used to pull the QA Docker image from the Omnibus GitLab `dev` Container Registry.
+  If the variable isn't present, the QA image from Docker Hub will be used.
+  This can be found in the shared GitLab QA 1Password vault.
+
+Example:
+
+```
+$ export GITLAB_QA_ACCESS_TOKEN=your_api_access_token
+$ export GITLAB_QA_DEV_ACCESS_TOKEN=your_dev_registry_access_token
+$ export GITLAB_USERNAME="gitlab-qa"
+$ export GITLAB_PASSWORD="$GITLAB_QA_PASSWORD"
+
+$ gitlab-qa Test::Instance::StagingRef
+```
+
 ### `Test::Instance::StagingGeo`
 
 This scenario tests that the Geo staging deployment (with [`staging.gitlab.com`](https://staging.gitlab.com) as the primary site and [`geo.staging.gitlab.com`](https://geo.staging.gitlab.com) as the secondary site) works as expected by running tests tagged `:geo` against it. This is done by spinning up a GitLab QA (`gitlab/gitlab-qa`) container and running the `QA::EE::Scenario::Test::Geo` scenario. Note that the Geo setup steps in the `QA::EE::Scenario::Test::Geo` scenario are skipped when testing a live Geo deployment.
@@ -789,8 +827,8 @@ Smoke tests are quick tests that ensure that some basic functionality of GitLab
 To run tests against the GitLab instance, a GitLab QA (`gitlab/gitlab-qa`)
 container is spun up and tests are run from it by running the
 `Test::Instance::Smoke` scenario (located under
-[`gitlab-org/gitlab-ce@qa/qa/scenario/test/smoke.rb`][smoke-instance] in the
-in the GitLab CE project).
+[`gitlab-org/gitlab/qa/qa/scenario/test/smoke.rb`][smoke-instance] in the
+in the GitLab project).
 
 Example:
 
@@ -863,5 +901,5 @@ $ gitlab-qa Test::Instance::Geo EE https://primary.gitlab.com https://secondary.
 
 [Back to README.md](../README.md)
 
-[test-instance]: https://gitlab.com/gitlab-org/gitlab-ce/blob/master/qa/qa/scenario/test/instance/all.rb
-[smoke-instance]: https://gitlab.com/gitlab-org/gitlab-ce/blob/master/qa/qa/scenario/test/instance/smoke.rb
+[test-instance]: https://gitlab.com/gitlab-org/gitlab/blob/master/qa/qa/scenario/test/instance/all.rb
+[smoke-instance]: https://gitlab.com/gitlab-org/gitlab/blob/master/qa/qa/scenario/test/instance/smoke.rb

data/lib/gitlab/qa/component/preprod.rb

@@ -1,7 +1,3 @@
-require 'net/http'
-require 'json'
-require 'uri'
-
 module Gitlab
   module QA
     module Component

data/lib/gitlab/qa/component/production.rb

@@ -1,7 +1,3 @@
-require 'net/http'
-require 'json'
-require 'uri'
-
 module Gitlab
   module QA
     module Component

data/lib/gitlab/qa/component/release.rb

@@ -1,7 +1,3 @@
-require 'net/http'
-require 'json'
-require 'uri'
-
 module Gitlab
   module QA
     module Component

data/lib/gitlab/qa/component/staging_ref.rb

@@ -0,0 +1,9 @@
+module Gitlab
+  module QA
+    module Component
+      class StagingRef < Staging
+        ADDRESS = 'https://staging-ref.testbed.gitlab.net'.freeze
+      end
+    end
+  end
+end

data/lib/gitlab/qa/report/report_as_issue.rb

@@ -113,7 +113,7 @@ module Gitlab
             "found:#{pipeline}.gitlab.com"
           when 'preprod'
             'found:pre.gitlab.com'
-          when 'staging-orchestrated', 'nightly', QA::Runtime::Env.default_branch
+          when 'staging-orchestrated', 'nightly', QA::Runtime::Env.default_branch, 'staging-ref'
             "found:#{pipeline}"
           else
             raise "No `found:*` label for the `#{pipeline}` pipeline!"

data/lib/gitlab/qa/scenario/test/instance/staging_ref.rb

@@ -0,0 +1,18 @@
+module Gitlab
+  module QA
+    module Scenario
+      module Test
+        module Instance
+          ##
+          # Run test suite against Staging Ref environment
+          #
+          class StagingRef < DeploymentBase
+            def deployment_component
+              Component::StagingRef
+            end
+          end
+        end
+      end
+    end
+  end
+end

data/lib/gitlab/qa/version.rb

@@ -1,5 +1,5 @@
 module Gitlab
   module QA
-    VERSION = '7.12.0'.freeze
+    VERSION = '7.13.0'.freeze
   end
 end

data/lib/gitlab/qa.rb

@@ -34,6 +34,7 @@ module Gitlab
           autoload :RelativeUrl, 'gitlab/qa/scenario/test/instance/relative_url'
           autoload :RepositoryStorage, 'gitlab/qa/scenario/test/instance/repository_storage'
           autoload :Staging, 'gitlab/qa/scenario/test/instance/staging'
+          autoload :StagingRef, 'gitlab/qa/scenario/test/instance/staging_ref'
           autoload :Production, 'gitlab/qa/scenario/test/instance/production'
           autoload :Smoke, 'gitlab/qa/scenario/test/instance/smoke'
           autoload :Preprod, 'gitlab/qa/scenario/test/instance/preprod'
@@ -87,6 +88,7 @@ module Gitlab
       autoload :SAML, 'gitlab/qa/component/saml'
       autoload :Specs, 'gitlab/qa/component/specs'
       autoload :Staging, 'gitlab/qa/component/staging'
+      autoload :StagingRef, 'gitlab/qa/component/staging_ref'
       autoload :Production, 'gitlab/qa/component/production'
       autoload :Minio, 'gitlab/qa/component/minio'
       autoload :Preprod, 'gitlab/qa/component/preprod'

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: gitlab-qa
 version: !ruby/object:Gem::Version
-  version: 7.12.0
+  version: 7.13.0
 platform: ruby
 authors:
 - GitLab Quality
 autorequire: 
 bindir: exe
 cert_chain: []
-date: 2021-10-26 00:00:00.000000000 Z
+date: 2021-10-27 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: climate_control
@@ -240,6 +240,7 @@ files:
 - lib/gitlab/qa/component/saml.rb
 - lib/gitlab/qa/component/specs.rb
 - lib/gitlab/qa/component/staging.rb
+- lib/gitlab/qa/component/staging_ref.rb
 - lib/gitlab/qa/docker/command.rb
 - lib/gitlab/qa/docker/engine.rb
 - lib/gitlab/qa/docker/shellout.rb
@@ -287,6 +288,7 @@ files:
 - lib/gitlab/qa/scenario/test/instance/smoke.rb
 - lib/gitlab/qa/scenario/test/instance/staging.rb
 - lib/gitlab/qa/scenario/test/instance/staging_geo.rb
+- lib/gitlab/qa/scenario/test/instance/staging_ref.rb
 - lib/gitlab/qa/scenario/test/integration/actioncable.rb
 - lib/gitlab/qa/scenario/test/integration/client_ssl.rb
 - lib/gitlab/qa/scenario/test/integration/elasticsearch.rb