gitlab-qa 2.3.0 → 2.4.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: f9cebacc84344d4f2fcf40f8e3fea53355e3c18a0df2e4411fe2f52bd85f2c0e
-  data.tar.gz: e28362d1ab57c9d1b82e127b186c15318981a00e39e43d571be07bd368fa653d
+  metadata.gz: 1dc61ff76fb45f254e883b53575de7e09482348b52f7b72a0e840f8b8024302e
+  data.tar.gz: 656af151c59ce81cfed572c9d3c73a4425234155b2f48da6dda7f633b3b2be20
 SHA512:
-  metadata.gz: 0434fa8431e7895cf572897c6cf6fdbf191627b92067153f051512fec9eda997f590a7f80c91675776f346c4e00003a29a88c1aac82873fcc793071da447fabc
-  data.tar.gz: ce014fcb3717205c49c0bf57437c5285cdb94e39e41d5f476408e33e0316019f53c249315395dc8ab32246849c02ccc7ddb9438e841840091946449ba97099c3
+  metadata.gz: cb409def7c5f6db99941f2632ffa51c58ccd42b862bbc65e61ab56d80988184e29950da6a62023225982472318bf367eafae57c3dbec733d202d87eed86ad86d
+  data.tar.gz: '0089c9e722eadfdb095b1fbbf60333d6e0ff7f19a8b18cba4bcc772c9b3765823e297eea19b8fce8b63577089ed53ab96a27ff0d9e6b58c4442ee6d5997138f2'

data/docs/how_it_works.md

@@ -12,7 +12,7 @@ For a visual architecture explanation, please read the
 1. A new `gitlab-ce` container is started with `Component::Gitlab.perform`
 1. Then `Component::Specs.perform` is called, which starts a `gitlab/gitlab-qa`
   container (from [`gitlab-org/gitlab-ce@qa/Dockerfile`][gitlab-dockerfile])
-  and pass it the instance-level scenario to run (e.g. `Test::Instance::All` for
+  and pass it the instance-level scenario to run (e.g. `Test::Instance` for
   [`gitlab-org/gitlab-qa@lib/gitlab/qa/scenario/test/instance/image.rb`][instance-image]),
   then the address of the live instance to be tested, and optional extra arguments.
 1. Within the `gitlab/gitlab-qa` container, these arguments are passed to `bin/test` (since it's
@@ -20,7 +20,7 @@ For a visual architecture explanation, please read the
   [`ENTRYPOINT` defined at `gitlab-org/gitlab-ce@qa/Dockerfile`][gitlab-dockerfile]),
   and then to `bin/qa`.
 1. `bin/qa` then calls `.launch!` on the fully qualified constant `QA::Scenario::` +
-  the scenario name, e.g. `QA::Scenario::Test::Instance::All`, and ultimately calls
+  the scenario name, e.g. `QA::Scenario::Test::Instance`, and ultimately calls
   [`.perform`][instance]
 1. The `.perform` method [saves the instance address for later][instance], then sets up an
   `RSpec::Core::Runner`, pass it the extra arguments,

data/docs/what_tests_can_be_run.md

@@ -48,7 +48,7 @@ This tests that a GitLab Docker container works as expected by running
 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::All`
+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).
@@ -216,7 +216,7 @@ 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::All` scenario (located under
+`Test::Instance` scenario (located under
 [`gitlab-org/gitlab-ce@qa/qa/scenario/test/instance.rb`][test-instance] in the
 in the GitLab CE project).
 
@@ -243,7 +243,7 @@ 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::All` scenario (located under
+`Test::Instance` scenario (located under
 [`gitlab-org/gitlab-ce@qa/qa/scenario/test/instance.rb`][test-instance] in the
 in the GitLab CE project).
 

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

@@ -10,7 +10,7 @@ module Gitlab
           class Any < Scenario::Template
             def perform(edition_and_tag, address, *rspec_args)
               Component::Specs.perform do |specs|
-                specs.suite = 'Test::Instance::All'
+                specs.suite = 'Test::Instance'
                 specs.release = Release.new(edition_and_tag)
                 specs.args = [address, *rspec_args]
               end

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

@@ -18,7 +18,7 @@ module Gitlab
 
                 gitlab.instance do
                   Component::Specs.perform do |specs|
-                    specs.suite = 'Test::Instance::All'
+                    specs.suite = 'Test::Instance'
                     specs.release = gitlab.release
                     specs.network = gitlab.network
                     specs.args = [gitlab.address]

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

@@ -24,7 +24,7 @@ module Gitlab
               end
 
               Component::Specs.perform do |specs|
-                specs.suite = 'Test::Instance::All'
+                specs.suite = 'Test::Instance'
                 specs.release = release
                 specs.args = [Component::Staging::ADDRESS, *rspec_args]
               end

data/lib/gitlab/qa/version.rb

@@ -1,5 +1,5 @@
 module Gitlab
   module QA
-    VERSION = '2.3.0'.freeze
+    VERSION = '2.4.0'.freeze
   end
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: gitlab-qa
 version: !ruby/object:Gem::Version
-  version: 2.3.0
+  version: 2.4.0
 platform: ruby
 authors:
 - Grzegorz Bizon
 autorequire: 
 bindir: exe
 cert_chain: []
-date: 2018-08-20 00:00:00.000000000 Z
+date: 2018-08-29 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: climate_control