-
Notifications
You must be signed in to change notification settings - Fork 42
/
components_in_s3_vertx.feature
427 lines (371 loc) · 20.4 KB
/
components_in_s3_vertx.feature
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
Feature: Checks the component metadata in AWS S3 database
@requires_s3_access @requires_bayesian_core_data_bucket @requires_bayesian_core_package_data_bucket
Scenario: Initial check if we are able to login to AWS S3 and that the component and package bucket exists
Given System is running
When I connect to the AWS S3 database
Then I should see bayesian-core-data bucket
And I should see bayesian-core-package-data bucket
@requires_s3_access @requires_bayesian_core_data_bucket @requires_bayesian_core_package_data_bucket
Scenario: Check the toplevel metadata schema for io.vertx:vertx-core (startup)
Given System is running
When I connect to the AWS S3 database
Then I should see bayesian-core-data bucket
When I read component toplevel metadata for the package io.vertx:vertx-core version 3.4.0 in ecosystem maven from the AWS S3 database bucket bayesian-core-data
Then I should find that the metadata conformns to component_toplevel schema
When I read component toplevel metadata for the package io.vertx:vertx-core version 3.5.1 in ecosystem maven from the AWS S3 database bucket bayesian-core-data
Then I should find that the metadata conformns to component_toplevel schema
@requires_s3_access @requires_bayesian_core_data_bucket @requires_bayesian_core_package_data_bucket
Scenario Outline: Check the toplevel metadata for all versions of the io.vertx packages
Given System is running
When I connect to the AWS S3 database
Then I should see bayesian-core-data bucket
When I read component toplevel metadata for the package <package> version <version> in ecosystem maven from the AWS S3 database bucket bayesian-core-data
Then I should find that the metadata conformns to component_toplevel schema
Examples: versions
|package|version|
|io.vertx:vertx-core|2.0.0-final|
|io.vertx:vertx-core|2.0.1-final|
|io.vertx:vertx-core|2.0.2-final|
|io.vertx:vertx-core|2.1.1|
|io.vertx:vertx-core|2.1.2|
|io.vertx:vertx-core|2.1.5|
|io.vertx:vertx-core|2.1.6|
|io.vertx:vertx-core|2.1|
|io.vertx:vertx-core|3.0.0-milestone2|
|io.vertx:vertx-core|3.0.0-milestone5|
|io.vertx:vertx-core|3.0.0|
|io.vertx:vertx-core|3.1.0|
|io.vertx:vertx-core|3.2.0|
|io.vertx:vertx-core|3.2.1|
|io.vertx:vertx-core|3.3.0|
|io.vertx:vertx-core|3.3.1|
|io.vertx:vertx-core|3.3.2|
|io.vertx:vertx-core|3.3.3|
|io.vertx:vertx-core|3.4.0.Beta1|
|io.vertx:vertx-core|3.4.0|
|io.vertx:vertx-core|3.4.1|
|io.vertx:vertx-core|3.4.2|
|io.vertx:vertx-core|3.5.0|
|io.vertx:vertx-core|3.5.1|
@requires_s3_access @requires_bayesian_core_data_bucket @requires_bayesian_core_package_data_bucket
Scenario: Check the code metrics metadata schema for io.vertx:vertx-core (startup)
Given System is running
When I connect to the AWS S3 database
Then I should see bayesian-core-data bucket
When I read code metrics metadata for the package io.vertx:vertx-core version 3.4.0 in ecosystem maven from the AWS S3 database bucket bayesian-core-data
Then I should find that the metadata conformns to component_code_metrics schema
@requires_s3_access @requires_bayesian_core_data_bucket @requires_bayesian_core_package_data_bucket
Scenario Outline: Check the code metrics metadata for all versions of the io.vertx packages
Given System is running
When I connect to the AWS S3 database
Then I should see bayesian-core-data bucket
When I read code metrics metadata for the package <package> version <version> in ecosystem maven from the AWS S3 database bucket bayesian-core-data
Then I should find that the metadata conformns to component_code_metrics schema
Examples: versions
|package|version|
|io.vertx:vertx-core|2.0.0-final|
|io.vertx:vertx-core|2.0.1-final|
|io.vertx:vertx-core|2.0.2-final|
|io.vertx:vertx-core|2.1.1|
|io.vertx:vertx-core|2.1.2|
|io.vertx:vertx-core|2.1.5|
|io.vertx:vertx-core|2.1.6|
|io.vertx:vertx-core|2.1|
|io.vertx:vertx-core|3.0.0-milestone2|
|io.vertx:vertx-core|3.0.0-milestone5|
|io.vertx:vertx-core|3.0.0|
|io.vertx:vertx-core|3.1.0|
|io.vertx:vertx-core|3.2.0|
|io.vertx:vertx-core|3.2.1|
|io.vertx:vertx-core|3.3.0|
|io.vertx:vertx-core|3.3.1|
|io.vertx:vertx-core|3.3.2|
# |io.vertx:vertx-core|3.3.3| # disabled, see https://github.com/openshiftio/openshift.io/issues/3243
|io.vertx:vertx-core|3.4.0.Beta1|
|io.vertx:vertx-core|3.4.0|
|io.vertx:vertx-core|3.4.1|
# |io.vertx:vertx-core|3.4.2| # the worker has been disabled by Frido
# |io.vertx:vertx-core|3.5.0| # the worker has been disabled by Frido
# |io.vertx:vertx-core|3.5.1| # the worker has been disabled by Frido
@requires_s3_access @requires_bayesian_core_data_bucket @requires_bayesian_core_package_data_bucket
Scenario: Check the digests metadata schema for io.vertx:vertx-core (startup)
Given System is running
When I connect to the AWS S3 database
Then I should see bayesian-core-data bucket
When I read digests metadata for the package io.vertx:vertx-core version 3.5.1 in ecosystem maven from the AWS S3 database bucket bayesian-core-data
Then I should find that the metadata conformns to component_digests schema
@requires_s3_access @requires_bayesian_core_data_bucket @requires_bayesian_core_package_data_bucket
Scenario Outline: Check the digests metadata schema for io.vertx:vertx-core
Given System is running
When I connect to the AWS S3 database
Then I should see bayesian-core-data bucket
When I read digests metadata for the package <package> version <version> in ecosystem maven from the AWS S3 database bucket bayesian-core-data
Then I should find that the metadata conformns to component_digests schema
Examples: versions
|package|version|
|io.vertx:vertx-core|2.0.0-final|
|io.vertx:vertx-core|2.0.1-final|
|io.vertx:vertx-core|2.0.2-final|
|io.vertx:vertx-core|2.1.1|
|io.vertx:vertx-core|2.1.2|
|io.vertx:vertx-core|2.1.5|
|io.vertx:vertx-core|2.1.6|
|io.vertx:vertx-core|2.1|
|io.vertx:vertx-core|3.0.0-milestone2|
|io.vertx:vertx-core|3.0.0-milestone5|
|io.vertx:vertx-core|3.0.0|
|io.vertx:vertx-core|3.1.0|
|io.vertx:vertx-core|3.2.0|
|io.vertx:vertx-core|3.2.1|
|io.vertx:vertx-core|3.3.0|
|io.vertx:vertx-core|3.3.1|
|io.vertx:vertx-core|3.3.2|
# |io.vertx:vertx-core|3.3.3| #!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
|io.vertx:vertx-core|3.4.0.Beta1|
|io.vertx:vertx-core|3.4.0|
|io.vertx:vertx-core|3.4.1|
|io.vertx:vertx-core|3.4.2|
|io.vertx:vertx-core|3.5.0|
|io.vertx:vertx-core|3.5.1|
@requires_s3_access @requires_bayesian_core_data_bucket @requires_bayesian_core_package_data_bucket
Scenario: Check the source licenses metadata schema for io.vertx:vertx-core (startup), schema is determined automatically
Given System is running
When I connect to the AWS S3 database
Then I should see bayesian-core-data bucket
When I read source licenses metadata for the package io.vertx:vertx-core version 3.5.1 in ecosystem maven from the AWS S3 database bucket bayesian-core-data
Then I should find that the metadata conformns to component_source_licenses schema
@requires_s3_access @requires_bayesian_core_data_bucket @requires_bayesian_core_package_data_bucket
Scenario: Check the source licenses metadata schema for io.vertx:vertx-core (startup), schema is determined automatically
Given System is running
When I connect to the AWS S3 database
Then I should see bayesian-core-data bucket
When I read source licenses metadata for the package io.vertx:vertx-core version 2.0.0-final in ecosystem maven from the AWS S3 database bucket bayesian-core-data
Then I should find that the metadata conformns to component_source_licenses schema
@requires_s3_access @requires_bayesian_core_data_bucket @requires_bayesian_core_package_data_bucket
Scenario Outline: Check the source licenses metadata schema for io.vertx:vertx-core
Given System is running
When I connect to the AWS S3 database
Then I should see bayesian-core-data bucket
When I read source licenses metadata for the package <package> version <version> in ecosystem maven from the AWS S3 database bucket bayesian-core-data
Then I should find that the metadata conformns to component_source_licenses schema
Examples: versions
|package|version|
|io.vertx:vertx-core|2.0.0-final|
|io.vertx:vertx-core|2.0.1-final|
|io.vertx:vertx-core|2.0.2-final|
|io.vertx:vertx-core|2.1.1|
|io.vertx:vertx-core|2.1.2|
|io.vertx:vertx-core|2.1.5|
|io.vertx:vertx-core|2.1.6|
|io.vertx:vertx-core|2.1|
|io.vertx:vertx-core|3.0.0-milestone2|
|io.vertx:vertx-core|3.0.0-milestone5|
|io.vertx:vertx-core|3.0.0|
|io.vertx:vertx-core|3.1.0|
|io.vertx:vertx-core|3.2.0|
|io.vertx:vertx-core|3.2.1|
|io.vertx:vertx-core|3.3.0|
|io.vertx:vertx-core|3.3.1|
|io.vertx:vertx-core|3.3.2|
|io.vertx:vertx-core|3.3.3| # missing data
|io.vertx:vertx-core|3.4.0.Beta1|
|io.vertx:vertx-core|3.4.0|
|io.vertx:vertx-core|3.4.1|
|io.vertx:vertx-core|3.4.2|
|io.vertx:vertx-core|3.5.0|
|io.vertx:vertx-core|3.5.1|
@requires_s3_access @requires_bayesian_core_data_bucket @requires_bayesian_core_package_data_bucket
Scenario: Check the dependency snapshot metadata schema for io.vertx:vertx-core (startup), schema is determined automatically
Given System is running
When I connect to the AWS S3 database
Then I should see bayesian-core-data bucket
When I read dependency snapshot metadata for the package io.vertx:vertx-core version 3.5.1 in ecosystem maven from the AWS S3 database bucket bayesian-core-data
Then I should find that the metadata conformns to component_dependency_snapshot schema
@requires_s3_access @requires_bayesian_core_data_bucket @requires_bayesian_core_package_data_bucket
Scenario: Check the dependency snapshot metadata schema for io.vertx:vertx-core (startup), schema is determined automatically
Given System is running
When I connect to the AWS S3 database
Then I should see bayesian-core-data bucket
When I read dependency snapshot metadata for the package io.vertx:vertx-core version 2.0.0-final in ecosystem maven from the AWS S3 database bucket bayesian-core-data
Then I should find that the metadata conformns to component_dependency_snapshot schema
@requires_s3_access @requires_bayesian_core_data_bucket @requires_bayesian_core_package_data_bucket
Scenario Outline: Check the dependency snapshot metadata schema for io.vertx:vertx-core
Given System is running
When I connect to the AWS S3 database
Then I should see bayesian-core-data bucket
When I read dependency snapshot metadata for the package <package> version <version> in ecosystem maven from the AWS S3 database bucket bayesian-core-data
Then I should find that the metadata conformns to component_dependency_snapshot schema
Examples: versions
|package|version|
|io.vertx:vertx-core|2.0.0-final|
|io.vertx:vertx-core|2.0.1-final|
|io.vertx:vertx-core|2.0.2-final|
|io.vertx:vertx-core|2.1.1|
|io.vertx:vertx-core|2.1.2|
|io.vertx:vertx-core|2.1.5|
|io.vertx:vertx-core|2.1.6|
|io.vertx:vertx-core|2.1|
|io.vertx:vertx-core|3.0.0-milestone2|
|io.vertx:vertx-core|3.0.0-milestone5|
|io.vertx:vertx-core|3.0.0|
|io.vertx:vertx-core|3.1.0|
|io.vertx:vertx-core|3.2.0|
|io.vertx:vertx-core|3.2.1|
|io.vertx:vertx-core|3.3.0|
|io.vertx:vertx-core|3.3.1|
|io.vertx:vertx-core|3.3.2|
|io.vertx:vertx-core|3.3.3| # missing data
|io.vertx:vertx-core|3.4.0.Beta1|
|io.vertx:vertx-core|3.4.0|
|io.vertx:vertx-core|3.4.1|
|io.vertx:vertx-core|3.4.2|
|io.vertx:vertx-core|3.5.0|
|io.vertx:vertx-core|3.5.1|
@requires_s3_access @requires_bayesian_core_data_bucket @requires_bayesian_core_package_data_bucket
Scenario: Check the security issues metadata schema for io.vertx:vertx-core (startup), schema is determined automatically
Given System is running
When I connect to the AWS S3 database
Then I should see bayesian-core-data bucket
When I read security issues metadata for the package io.vertx:vertx-core version 3.5.1 in ecosystem maven from the AWS S3 database bucket bayesian-core-data
Then I should find that the metadata conformns to component_security_issues schema
@requires_s3_access @requires_bayesian_core_data_bucket @requires_bayesian_core_package_data_bucket
Scenario: Check the security issues metadata schema for io.vertx:vertx-core (startup), schema is determined automatically
Given System is running
When I connect to the AWS S3 database
Then I should see bayesian-core-data bucket
When I read security issues metadata for the package io.vertx:vertx-core version 2.0.0-final in ecosystem maven from the AWS S3 database bucket bayesian-core-data
Then I should find that the metadata conformns to component_security_issues schema
@requires_s3_access @requires_bayesian_core_data_bucket @requires_bayesian_core_package_data_bucket
Scenario Outline: Check the security issues metadata schema for io.vertx:vertx-core
Given System is running
When I connect to the AWS S3 database
Then I should see bayesian-core-data bucket
When I read security issues metadata for the package <package> version <version> in ecosystem maven from the AWS S3 database bucket bayesian-core-data
Then I should find that the metadata conformns to component_security_issues schema
Examples: versions
|package|version|
|io.vertx:vertx-core|2.0.0-final|
|io.vertx:vertx-core|2.0.1-final|
|io.vertx:vertx-core|2.0.2-final|
|io.vertx:vertx-core|2.1.1|
|io.vertx:vertx-core|2.1.2|
|io.vertx:vertx-core|2.1.5|
|io.vertx:vertx-core|2.1.6|
|io.vertx:vertx-core|2.1|
|io.vertx:vertx-core|3.0.0-milestone2|
|io.vertx:vertx-core|3.0.0-milestone5|
|io.vertx:vertx-core|3.0.0|
|io.vertx:vertx-core|3.1.0|
|io.vertx:vertx-core|3.2.0|
|io.vertx:vertx-core|3.2.1|
|io.vertx:vertx-core|3.3.0|
|io.vertx:vertx-core|3.3.1|
|io.vertx:vertx-core|3.3.2|
|io.vertx:vertx-core|3.3.3| # missing data
|io.vertx:vertx-core|3.4.0.Beta1|
|io.vertx:vertx-core|3.4.0|
|io.vertx:vertx-core|3.4.1|
|io.vertx:vertx-core|3.4.2|
|io.vertx:vertx-core|3.5.0|
|io.vertx:vertx-core|3.5.1|
@requires_s3_access @requires_bayesian_core_data_bucket @requires_bayesian_core_package_data_bucket
Scenario: Check the metadata metadata schema for io.vertx:vertx-core (startup), schema is determined automatically
Given System is running
When I connect to the AWS S3 database
Then I should see bayesian-core-data bucket
When I read metadata metadata for the package io.vertx:vertx-core version 3.5.1 in ecosystem maven from the AWS S3 database bucket bayesian-core-data
Then I should find that the metadata conformns to component_metadata schema
@requires_s3_access @requires_bayesian_core_data_bucket @requires_bayesian_core_package_data_bucket
Scenario: Check the metadata metadata schema for io.vertx:vertx-core (startup), schema is determined automatically
Given System is running
When I connect to the AWS S3 database
Then I should see bayesian-core-data bucket
When I read metadata metadata for the package io.vertx:vertx-core version 3.4.1 in ecosystem maven from the AWS S3 database bucket bayesian-core-data
Then I should find that the metadata conformns to component_metadata schema
@requires_s3_access @requires_bayesian_core_data_bucket @requires_bayesian_core_package_data_bucket
Scenario: Check the metadata metadata schema for io.vertx:vertx-core (startup), schema is determined automatically
Given System is running
When I connect to the AWS S3 database
Then I should see bayesian-core-data bucket
When I read metadata metadata for the package io.vertx:vertx-core version 2.0.0-final in ecosystem maven from the AWS S3 database bucket bayesian-core-data
Then I should find that the metadata conformns to component_metadata schema
@requires_s3_access @requires_bayesian_core_data_bucket @requires_bayesian_core_package_data_bucket
Scenario Outline: Check the metadata metadata schema for io.vertx:vertx-core
Given System is running
When I connect to the AWS S3 database
Then I should see bayesian-core-data bucket
When I read metadata metadata for the package <package> version <version> in ecosystem maven from the AWS S3 database bucket bayesian-core-data
Then I should find that the metadata conformns to component_metadata schema
Examples: versions
|package|version|
|io.vertx:vertx-core|2.0.0-final|
|io.vertx:vertx-core|2.0.1-final|
|io.vertx:vertx-core|2.0.2-final|
|io.vertx:vertx-core|2.1.1|
|io.vertx:vertx-core|2.1.2|
|io.vertx:vertx-core|2.1.5|
|io.vertx:vertx-core|2.1.6|
|io.vertx:vertx-core|2.1|
|io.vertx:vertx-core|3.0.0-milestone2|
|io.vertx:vertx-core|3.0.0-milestone5|
|io.vertx:vertx-core|3.0.0|
|io.vertx:vertx-core|3.1.0|
|io.vertx:vertx-core|3.2.0|
|io.vertx:vertx-core|3.2.1|
|io.vertx:vertx-core|3.3.0|
|io.vertx:vertx-core|3.3.1|
|io.vertx:vertx-core|3.3.2|
|io.vertx:vertx-core|3.3.3| # missing data
|io.vertx:vertx-core|3.4.0.Beta1|
|io.vertx:vertx-core|3.4.0|
|io.vertx:vertx-core|3.4.1|
|io.vertx:vertx-core|3.4.2|
|io.vertx:vertx-core|3.5.0|
|io.vertx:vertx-core|3.5.1|
@requires_s3_access @requires_bayesian_core_data_bucket @requires_bayesian_core_package_data_bucket
Scenario: Check the keywords tagging metadata schema for io.vertx:vertx-core (startup), schema is determined automatically
Given System is running
When I connect to the AWS S3 database
Then I should see bayesian-core-data bucket
When I read keywords tagging metadata for the package io.vertx:vertx-core version 3.5.1 in ecosystem maven from the AWS S3 database bucket bayesian-core-data
Then I should find that the metadata conformns to component_keywords_tagging schema
@requires_s3_access @requires_bayesian_core_data_bucket @requires_bayesian_core_package_data_bucket
Scenario: Check the keywords tagging metadata schema for io.vertx:vertx-core (startup), schema is determined automatically
Given System is running
When I connect to the AWS S3 database
Then I should see bayesian-core-data bucket
When I read keywords tagging metadata for the package io.vertx:vertx-core version 3.4.1 in ecosystem maven from the AWS S3 database bucket bayesian-core-data
Then I should find that the metadata conformns to component_keywords_tagging schema
@requires_s3_access @requires_bayesian_core_data_bucket @requires_bayesian_core_package_data_bucket
Scenario Outline: Check the keywors tagging schema for io.vertx:vertx-core
Given System is running
When I connect to the AWS S3 database
Then I should see bayesian-core-data bucket
When I read keywords tagging metadata for the package <package> version <version> in ecosystem maven from the AWS S3 database bucket bayesian-core-data
Then I should find that the metadata conformns to component_keywords_tagging schema
Examples: versions
|package|version|
# N/A |io.vertx:vertx-core|2.0.0-final|
# N/A |io.vertx:vertx-core|2.0.1-final|
# N/A |io.vertx:vertx-core|2.0.2-final|
# N/A |io.vertx:vertx-core|2.1.1|
# N/A |io.vertx:vertx-core|2.1.2|
# N/A |io.vertx:vertx-core|2.1.5|
# N/A |io.vertx:vertx-core|2.1.6|
# N/A |io.vertx:vertx-core|2.1|
# N/A |io.vertx:vertx-core|3.0.0-milestone2|
# N/A |io.vertx:vertx-core|3.0.0-milestone5|
# N/A |io.vertx:vertx-core|3.0.0|
# N/A |io.vertx:vertx-core|3.1.0|
# N/A |io.vertx:vertx-core|3.2.0|
# N/A |io.vertx:vertx-core|3.2.1|
# N/A |io.vertx:vertx-core|3.3.0|
# N/A |io.vertx:vertx-core|3.3.1|
# N/A |io.vertx:vertx-core|3.3.2|
# N/A |io.vertx:vertx-core|3.3.3| # missing data
# N/A |io.vertx:vertx-core|3.4.0.Beta1|
# N/A |io.vertx:vertx-core|3.4.0|
|io.vertx:vertx-core|3.4.1|
|io.vertx:vertx-core|3.4.2|
|io.vertx:vertx-core|3.5.0|
|io.vertx:vertx-core|3.5.1|