gitlab-qa 2.2.0 → 2.3.0
Sign up to get free protection for your applications and to get access to all the features.
- checksums.yaml +4 -4
- data/docs/how_it_works.md +2 -2
- data/docs/what_tests_can_be_run.md +3 -3
- data/lib/gitlab/qa.rb +1 -0
- data/lib/gitlab/qa/scenario/test/instance/any.rb +1 -1
- data/lib/gitlab/qa/scenario/test/instance/image.rb +1 -1
- data/lib/gitlab/qa/scenario/test/instance/smoke.rb +23 -0
- data/lib/gitlab/qa/scenario/test/instance/staging.rb +1 -1
- data/lib/gitlab/qa/version.rb +1 -1
- metadata +2 -1
checksums.yaml
CHANGED
@@ -1,7 +1,7 @@
|
|
1
1
|
---
|
2
2
|
SHA256:
|
3
|
-
metadata.gz:
|
4
|
-
data.tar.gz:
|
3
|
+
metadata.gz: f9cebacc84344d4f2fcf40f8e3fea53355e3c18a0df2e4411fe2f52bd85f2c0e
|
4
|
+
data.tar.gz: e28362d1ab57c9d1b82e127b186c15318981a00e39e43d571be07bd368fa653d
|
5
5
|
SHA512:
|
6
|
-
metadata.gz:
|
7
|
-
data.tar.gz:
|
6
|
+
metadata.gz: 0434fa8431e7895cf572897c6cf6fdbf191627b92067153f051512fec9eda997f590a7f80c91675776f346c4e00003a29a88c1aac82873fcc793071da447fabc
|
7
|
+
data.tar.gz: ce014fcb3717205c49c0bf57437c5285cdb94e39e41d5f476408e33e0316019f53c249315395dc8ab32246849c02ccc7ddb9438e841840091946449ba97099c3
|
data/docs/how_it_works.md
CHANGED
@@ -12,7 +12,7 @@ For a visual architecture explanation, please read the
|
|
12
12
|
1. A new `gitlab-ce` container is started with `Component::Gitlab.perform`
|
13
13
|
1. Then `Component::Specs.perform` is called, which starts a `gitlab/gitlab-qa`
|
14
14
|
container (from [`gitlab-org/gitlab-ce@qa/Dockerfile`][gitlab-dockerfile])
|
15
|
-
and pass it the instance-level scenario to run (e.g. `Test::Instance` for
|
15
|
+
and pass it the instance-level scenario to run (e.g. `Test::Instance::All` for
|
16
16
|
[`gitlab-org/gitlab-qa@lib/gitlab/qa/scenario/test/instance/image.rb`][instance-image]),
|
17
17
|
then the address of the live instance to be tested, and optional extra arguments.
|
18
18
|
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
|
|
20
20
|
[`ENTRYPOINT` defined at `gitlab-org/gitlab-ce@qa/Dockerfile`][gitlab-dockerfile]),
|
21
21
|
and then to `bin/qa`.
|
22
22
|
1. `bin/qa` then calls `.launch!` on the fully qualified constant `QA::Scenario::` +
|
23
|
-
the scenario name, e.g. `QA::Scenario::Test::Instance`, and ultimately calls
|
23
|
+
the scenario name, e.g. `QA::Scenario::Test::Instance::All`, and ultimately calls
|
24
24
|
[`.perform`][instance]
|
25
25
|
1. The `.perform` method [saves the instance address for later][instance], then sets up an
|
26
26
|
`RSpec::Core::Runner`, pass it the extra arguments,
|
@@ -48,7 +48,7 @@ This tests that a GitLab Docker container works as expected by running
|
|
48
48
|
instance-level tests against it.
|
49
49
|
|
50
50
|
To run tests against the GitLab containers, a GitLab QA (`gitlab/gitlab-qa`)
|
51
|
-
container is spun up and tests are run from it by running the `Test::Instance`
|
51
|
+
container is spun up and tests are run from it by running the `Test::Instance::All`
|
52
52
|
scenario (located under
|
53
53
|
[`gitlab-org/gitlab-ce@qa/qa/scenario/test/instance.rb`][test-instance] in the
|
54
54
|
GitLab CE project).
|
@@ -216,7 +216,7 @@ against it.
|
|
216
216
|
|
217
217
|
To run tests against the GitLab instance, a GitLab QA (`gitlab/gitlab-qa`)
|
218
218
|
container is spun up and tests are run from it by running the
|
219
|
-
`Test::Instance` scenario (located under
|
219
|
+
`Test::Instance::All` scenario (located under
|
220
220
|
[`gitlab-org/gitlab-ce@qa/qa/scenario/test/instance.rb`][test-instance] in the
|
221
221
|
in the GitLab CE project).
|
222
222
|
|
@@ -243,7 +243,7 @@ works as expected by running tests against it.
|
|
243
243
|
|
244
244
|
To run tests against the GitLab instance, a GitLab QA (`gitlab/gitlab-qa`)
|
245
245
|
container is spun up and tests are run from it by running the
|
246
|
-
`Test::Instance` scenario (located under
|
246
|
+
`Test::Instance::All` scenario (located under
|
247
247
|
[`gitlab-org/gitlab-ce@qa/qa/scenario/test/instance.rb`][test-instance] in the
|
248
248
|
in the GitLab CE project).
|
249
249
|
|
data/lib/gitlab/qa.rb
CHANGED
@@ -10,7 +10,7 @@ module Gitlab
|
|
10
10
|
class Any < Scenario::Template
|
11
11
|
def perform(edition_and_tag, address, *rspec_args)
|
12
12
|
Component::Specs.perform do |specs|
|
13
|
-
specs.suite = 'Test::Instance'
|
13
|
+
specs.suite = 'Test::Instance::All'
|
14
14
|
specs.release = Release.new(edition_and_tag)
|
15
15
|
specs.args = [address, *rspec_args]
|
16
16
|
end
|
@@ -0,0 +1,23 @@
|
|
1
|
+
module Gitlab
|
2
|
+
module QA
|
3
|
+
module Scenario
|
4
|
+
module Test
|
5
|
+
module Instance
|
6
|
+
##
|
7
|
+
# Run smoke test suite against any GitLab instance,
|
8
|
+
# including staging and on-premises installation.
|
9
|
+
#
|
10
|
+
class Smoke < Scenario::Template
|
11
|
+
def perform(edition_and_tag, address, *rspec_args)
|
12
|
+
Component::Specs.perform do |specs|
|
13
|
+
specs.suite = 'Test::Instance::Smoke'
|
14
|
+
specs.release = Release.new(edition_and_tag)
|
15
|
+
specs.args = [address, *rspec_args]
|
16
|
+
end
|
17
|
+
end
|
18
|
+
end
|
19
|
+
end
|
20
|
+
end
|
21
|
+
end
|
22
|
+
end
|
23
|
+
end
|
data/lib/gitlab/qa/version.rb
CHANGED
metadata
CHANGED
@@ -1,7 +1,7 @@
|
|
1
1
|
--- !ruby/object:Gem::Specification
|
2
2
|
name: gitlab-qa
|
3
3
|
version: !ruby/object:Gem::Version
|
4
|
-
version: 2.
|
4
|
+
version: 2.3.0
|
5
5
|
platform: ruby
|
6
6
|
authors:
|
7
7
|
- Grzegorz Bizon
|
@@ -156,6 +156,7 @@ files:
|
|
156
156
|
- lib/gitlab/qa/scenario/template.rb
|
157
157
|
- lib/gitlab/qa/scenario/test/instance/any.rb
|
158
158
|
- lib/gitlab/qa/scenario/test/instance/image.rb
|
159
|
+
- lib/gitlab/qa/scenario/test/instance/smoke.rb
|
159
160
|
- lib/gitlab/qa/scenario/test/instance/staging.rb
|
160
161
|
- lib/gitlab/qa/scenario/test/integration/geo.rb
|
161
162
|
- lib/gitlab/qa/scenario/test/integration/kubernetes.rb
|