1
1
Feature : Check for new recipe versions
2
-
2
+ @docker
3
3
Scenario : Find newer version for a recipe
4
4
Given a recipe "foo"
5
5
And recipe "foo" generates file "README.md" with content "initial"
@@ -16,6 +16,7 @@ Feature: Check for new recipe versions
16
16
Then CLI produced an output "new versions found: v0\. 0\. 2"
17
17
Then CLI produced an output "To upgrade recipes to the latest version run:\n (.*) upgrade oci://localhost:\d +/foo:v0.0.2\n "
18
18
19
+ @docker
19
20
Scenario : Find multiple newer version for a recipe
20
21
Given a recipe "foo"
21
22
And recipe "foo" generates file "README.md" with content "initial"
@@ -33,6 +34,7 @@ Feature: Check for new recipe versions
33
34
Then CLI produced an output "new versions found: v0\. 0\. 2, v0\. 0\. 3"
34
35
Then CLI produced an output "To upgrade recipes to the latest version run:\n (.*) upgrade oci://localhost:\d +/foo:v0\. 0\. 3\n "
35
36
37
+ @docker
36
38
Scenario : Find newer version for multiple recipes
37
39
Given a recipe "foo"
38
40
And recipe "foo" generates file "foo.md" with content "initial"
@@ -59,6 +61,7 @@ Feature: Check for new recipe versions
59
61
Then CLI produced an output "foo: new versions found: v0\. 0\. 2"
60
62
And CLI produced an output "bar: new versions found: v0\. 0\. 2"
61
63
64
+ @docker
62
65
Scenario : Unable to find newer recipe versions
63
66
Given a recipe "foo"
64
67
And recipe "foo" generates file "README.md" with content "initial"
@@ -73,6 +76,7 @@ Feature: Check for new recipe versions
73
76
And I check new versions for recipe "foo"
74
77
Then CLI produced an output "no new versions found"
75
78
79
+ @docker
76
80
Scenario : Unable to find newer recipe versions for all recipes
77
81
Given a recipe "foo"
78
82
And recipe "foo" generates file "foo.md" with content "initial"
@@ -95,6 +99,7 @@ Feature: Check for new recipe versions
95
99
Then CLI produced an output "foo: new versions found: v0\. 0\. 2"
96
100
And CLI produced an output "bar: no new versions found"
97
101
102
+ @docker
98
103
Scenario : Executing remote recipe automatically adds the repo as source for the sauce
99
104
Given a recipe "foo"
100
105
And recipe "foo" generates file "README.md" with content "initial"
@@ -108,6 +113,7 @@ Feature: Check for new recipe versions
108
113
And I check new versions for recipe "foo"
109
114
Then CLI produced an output "new versions found: v0\. 0\. 2"
110
115
116
+ @docker
111
117
Scenario : Manually override the check from URL for locally executed recipe
112
118
Given a recipe "foo"
113
119
And recipe "foo" generates file "README.md" with content "initial"
@@ -121,6 +127,7 @@ Feature: Check for new recipe versions
121
127
Then CLI produced an output "new versions found: v0\. 0\. 2"
122
128
And the sauce in index 0 which should have property "CheckFrom" with value "^oci://localhost:\d +/foo$"
123
129
130
+ @docker
124
131
Scenario : Find and upgrade newer version for recipes
125
132
Given a recipe "foo"
126
133
And recipe "foo" generates file "README.md" with content "initial"
@@ -136,6 +143,7 @@ Feature: Check for new recipe versions
136
143
Then CLI produced an output "new versions found: v0\. 0\. 2"
137
144
Then CLI produced an output "Upgrade completed"
138
145
146
+ @docker
139
147
Scenario : Find and upgrade newer version for a specific recipe
140
148
Given a recipe "foo"
141
149
And recipe "foo" generates file "README.md" with content "initial"
@@ -157,6 +165,7 @@ Feature: Check for new recipe versions
157
165
Then CLI produced an output "new versions found: v0\. 0\. 2"
158
166
Then CLI produced an output "Upgrade completed"
159
167
168
+ @docker
160
169
Scenario : Find and upgrade newer versions for multiple recipes
161
170
Given a recipe "foo"
162
171
And recipe "foo" generates file "foo.md" with content "initial"
0 commit comments