Skip to content

Commit f687904

Browse files
Art4Art4
committed
improve tags in behat features
1 parent 0eb970b commit f687904

File tree

11 files changed

+28
-67
lines changed

11 files changed

+28
-67
lines changed

‎tests/Behat/features/attachments.feature‎

Lines changed: 4 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -1,9 +1,9 @@
1+
@attachment
12
Feature: Interacting with the REST API for attachments
23
In order to interact with REST API for attachments
34
As a user
45
I want to make sure the Redmine server replies with the correct response
56

6-
@attachment
77
Scenario: Uploading an attachment
88
Given I have a "NativeCurlClient" client
99
When I upload the content of the file "%tests_dir%/Fixtures/testfile_01.txt" with the following data
@@ -26,7 +26,7 @@ Feature: Interacting with the REST API for attachments
2626
| id | 1 |
2727
| token | 1.7b962f8af22e26802b87abfa0b07b21dbd03b984ec8d6888dabd3f69cff162f8 |
2828

29-
@attachment
29+
3030
Scenario: Updating the details of an attachment
3131
Given I have a "NativeCurlClient" client
3232
And I create a project with name "Test Project" and identifier "test-project"
@@ -41,7 +41,6 @@ Feature: Interacting with the REST API for attachments
4141
And the response has the content ""
4242
And the returned data is true
4343

44-
@attachment
4544
Scenario: Showing the details of an attachment
4645
Given I have a "NativeCurlClient" client
4746
And I upload the content of the file "%tests_dir%/Fixtures/testfile_01.txt" with the following data
@@ -80,7 +79,7 @@ Feature: Interacting with the REST API for attachments
8079
| id | 1 |
8180
| name | Redmine Admin |
8281

83-
@attachment @error
82+
@error
8483
Scenario: Try to show details of a non-existing attachment
8584
Given I have a "NativeCurlClient" client
8685
When I show the attachment with the id "1"
@@ -89,7 +88,6 @@ Feature: Interacting with the REST API for attachments
8988
And the response has the content ""
9089
And the returned data is false
9190

92-
@attachment
9391
Scenario: Downloading an attachment
9492
Given I have a "NativeCurlClient" client
9593
And I upload the content of the file "%tests_dir%/Fixtures/testfile_01.txt" with the following data
@@ -111,7 +109,7 @@ Feature: Interacting with the REST API for attachments
111109
112110
"""
113111

114-
@attachment @error
112+
@error
115113
Scenario: Try to download a non-existing attachment
116114
Given I have a "NativeCurlClient" client
117115
When I download the attachment with the id "1"
@@ -121,7 +119,6 @@ Feature: Interacting with the REST API for attachments
121119
# And the response has the content "<!DOCTYPE html><html lang="en">..."
122120
And the returned data is false
123121

124-
@attachment
125122
Scenario: Deleting an attachment
126123
Given I have a "NativeCurlClient" client
127124
And I upload the content of the file "%tests_dir%/Fixtures/testfile_01.txt" with the following data

‎tests/Behat/features/groups.feature‎

Lines changed: 2 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -1,9 +1,9 @@
1+
@group
12
Feature: Interacting with the REST API for groups
23
In order to interact with REST API for groups
34
As a user
45
I want to make sure the Redmine server replies with the correct response
56

6-
@group
77
Scenario: Creating a group with minimal parameters
88
Given I have a "NativeCurlClient" client
99
When I create a group with name "Test Group"
@@ -20,7 +20,6 @@ Feature: Interacting with the REST API for groups
2020
| id | 4 |
2121
| name | Test Group |
2222

23-
@group
2423
Scenario: Listing of zero groups
2524
Given I have a "NativeCurlClient" client
2625
When I list all groups
@@ -33,7 +32,6 @@ Feature: Interacting with the REST API for groups
3332
And the returned data "groups" property is an array
3433
And the returned data "groups" property contains "0" items
3534

36-
@group
3735
Scenario: Listing of one group
3836
Given I have a "NativeCurlClient" client
3937
And I create a group with name "Test Group"
@@ -57,7 +55,6 @@ Feature: Interacting with the REST API for groups
5755
| id | 4 |
5856
| name | Test Group |
5957

60-
@group
6158
Scenario: Listing names of all groups
6259
Given I have a "NativeCurlClient" client
6360
And I create a group with name "Test Group 1"
@@ -78,7 +75,6 @@ Feature: Interacting with the REST API for groups
7875
| 7 | Test Group 4 |
7976
| 8 | Test Group 5 |
8077

81-
@group
8278
Scenario: Showing a specific group
8379
Given I have a "NativeCurlClient" client
8480
And I create a group with name "Test Group"
@@ -100,7 +96,7 @@ Feature: Interacting with the REST API for groups
10096
| id | 4 |
10197
| name | Test Group |
10298

103-
@group @error
99+
@error
104100
Scenario: Try to show a non-existing group
105101
Given I have a "NativeCurlClient" client
106102
When I show the group with id "40"
@@ -109,7 +105,6 @@ Feature: Interacting with the REST API for groups
109105
And the response has the content ""
110106
And the returned data is false
111107

112-
@group
113108
Scenario: Updating a group
114109
Given I have a "NativeCurlClient" client
115110
And I create a group with the following data
@@ -123,7 +118,6 @@ Feature: Interacting with the REST API for groups
123118
And the response has the content ""
124119
And the returned data is exactly ""
125120

126-
@group
127121
Scenario: Adding an user to a group
128122
Given I have a "NativeCurlClient" client
129123
And I create a group with name "Test Group"
@@ -133,7 +127,6 @@ Feature: Interacting with the REST API for groups
133127
And the response has the content ""
134128
And the returned data is exactly ""
135129

136-
@group
137130
Scenario: Removing an user from a group
138131
Given I have a "NativeCurlClient" client
139132
And I create a group with name "Test Group"
@@ -144,7 +137,6 @@ Feature: Interacting with the REST API for groups
144137
And the response has the content ""
145138
And the returned data is exactly ""
146139

147-
@group
148140
Scenario: Deleting a group
149141
Given I have a "NativeCurlClient" client
150142
And I create a group with name "Test Group"

‎tests/Behat/features/issue.feature‎

Lines changed: 2 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -1,9 +1,9 @@
1+
@issue
12
Feature: Interacting with the REST API for issues
23
In order to interact with REST API for issues
34
As a user
45
I want to make sure the Redmine server replies with the correct response
56

6-
@issue
77
Scenario: Creating an issue with miminal data
88
Given I have a "NativeCurlClient" client
99
And I have an issue status with the name "New"
@@ -113,7 +113,6 @@ Feature: Interacting with the REST API for issues
113113
| id | 1 |
114114
| name | Redmine Admin |
115115

116-
@issue
117116
Scenario: Updating an issue
118117
Given I have a "NativeCurlClient" client
119118
And I have an issue status with the name "New"
@@ -139,7 +138,7 @@ Feature: Interacting with the REST API for issues
139138
And the response has the content ""
140139
And the returned data is exactly ""
141140

142-
@issue @error
141+
@error
143142
Scenario: Showing a not existing issue
144143
Given I have a "NativeCurlClient" client
145144
When I show the issue with id "10"
@@ -148,7 +147,6 @@ Feature: Interacting with the REST API for issues
148147
And the response has the content ""
149148
And the returned data is false
150149

151-
@issue
152150
Scenario: Adding a watcher to an issue
153151
Given I have a "NativeCurlClient" client
154152
And I have an issue status with the name "New"
@@ -168,7 +166,6 @@ Feature: Interacting with the REST API for issues
168166
And the response has the content ""
169167
And the returned data is exactly ""
170168

171-
@issue
172169
Scenario: Removing a watcher from an issue
173170
Given I have a "NativeCurlClient" client
174171
And I have an issue status with the name "New"
@@ -189,7 +186,6 @@ Feature: Interacting with the REST API for issues
189186
And the response has the content ""
190187
And the returned data is exactly ""
191188

192-
@issue
193189
Scenario: Removing an issue
194190
Given I have a "NativeCurlClient" client
195191
And I have an issue status with the name "New"

‎tests/Behat/features/issue_category.feature‎

Lines changed: 1 addition & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,9 +1,9 @@
1+
@issue_category
12
Feature: Interacting with the REST API for issue categories
23
In order to interact with REST API for issue categories
34
As a user
45
I want to make sure the Redmine server replies with the correct response
56

6-
@issue_category
77
Scenario: Creating an issue category with miminal data
88
Given I have a "NativeCurlClient" client
99
And I create a project with name "Test Project" and identifier "test-project"
@@ -36,7 +36,6 @@ Feature: Interacting with the REST API for issue categories
3636
| id | 1 |
3737
| name | Test Project |
3838

39-
@issue_category
4039
Scenario: Creating an issue category with all data
4140
Given I have a "NativeCurlClient" client
4241
And I create a project with name "Test Project" and identifier "test-project"
@@ -83,7 +82,6 @@ Feature: Interacting with the REST API for issue categories
8382
| id | 1 |
8483
| name | Redmine Admin |
8584

86-
@issue_category
8785
Scenario: Updating an issue category with all data
8886
Given I have a "NativeCurlClient" client
8987
And I create a project with name "Test Project" and identifier "test-project"
@@ -100,7 +98,6 @@ Feature: Interacting with the REST API for issue categories
10098
And the response has the content ""
10199
And the returned data is exactly ""
102100

103-
@issue_category
104101
Scenario: Deleting an issue category
105102
Given I have a "NativeCurlClient" client
106103
And I create a project with name "Test Project" and identifier "test-project"

‎tests/Behat/features/issue_relation.feature‎

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,9 +1,9 @@
1+
@issue_relation
12
Feature: Interacting with the REST API for issue relations
23
In order to interact with REST API for issue relations
34
As a user
45
I want to make sure the Redmine server replies with the correct response
56

6-
@issue_relation
77
Scenario: Creating an issue relation with miminal data
88
Given I have a "NativeCurlClient" client
99
And I have an issue status with the name "New"
@@ -50,7 +50,6 @@ Feature: Interacting with the REST API for issue relations
5050
| relation_type | relates |
5151
| delay | null |
5252

53-
@issue_relation
5453
Scenario: Deleting an issue relation
5554
Given I have a "NativeCurlClient" client
5655
And I have an issue status with the name "New"

‎tests/Behat/features/membership.feature‎

Lines changed: 1 addition & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,9 +1,9 @@
1+
@membership
12
Feature: Interacting with the REST API for memberships
23
In order to interact with REST API for memberships
34
As a user
45
I want to make sure the Redmine server replies with the correct response
56

6-
@membership
77
Scenario: Creating a membership
88
Given I have a "NativeCurlClient" client
99
And I have a role with the name "Developer"
@@ -16,7 +16,6 @@ Feature: Interacting with the REST API for memberships
1616
And the response has the content type "application/xml"
1717
And the returned data is an instance of "SimpleXMLElement"
1818

19-
@membership
2019
Scenario: Updating a membership
2120
Given I have a "NativeCurlClient" client
2221
And I have a role with the name "Developer"
@@ -34,7 +33,6 @@ Feature: Interacting with the REST API for memberships
3433
And the response has the content ""
3534
And the returned data is exactly ""
3635

37-
@membership
3836
Scenario: Removing a membership
3937
Given I have a "NativeCurlClient" client
4038
And I have a role with the name "Developer"
@@ -49,7 +47,6 @@ Feature: Interacting with the REST API for memberships
4947
And the response has the content ""
5048
And the returned data is exactly ""
5149

52-
@membership
5350
Scenario: Removing an user from a project
5451
Given I have a "NativeCurlClient" client
5552
And I have a role with the name "Developer"

‎tests/Behat/features/projects.feature‎

Lines changed: 6 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -1,9 +1,9 @@
1+
@project
12
Feature: Interacting with the REST API for projects
23
In order to interact with REST API for projects
34
As a user
45
I want to make sure the Redmine server replies with the correct response
56

6-
@project
77
Scenario: Creating a project with minimal parameters
88
Given I have a "NativeCurlClient" client
99
When I create a project with name "Test Project" and identifier "test-project"
@@ -29,7 +29,6 @@ Feature: Interacting with the REST API for projects
2929
| name | Test Project |
3030
| identifier | test-project |
3131

32-
@project
3332
Scenario: Creating a project with multiple parameters
3433
Given I have a "NativeCurlClient" client
3534
When I create a project with the following data
@@ -51,7 +50,6 @@ Feature: Interacting with the REST API for projects
5150
| is_public | true |
5251
| inherit_members | false |
5352

54-
@project
5553
Scenario: Showing a specific project
5654
Given I have a "NativeCurlClient" client
5755
And I create a project with name "Test Project" and identifier "test-project"
@@ -91,7 +89,6 @@ Feature: Interacting with the REST API for projects
9189
| trackers | [] |
9290
| issue_categories | [] |
9391

94-
@project
9592
Scenario: Listing of zero projects
9693
Given I have a "NativeCurlClient" client
9794
When I list all projects
@@ -112,7 +109,6 @@ Feature: Interacting with the REST API for projects
112109
| offset | 0 |
113110
| limit | 25 |
114111

115-
@project
116112
Scenario: Listing of one project
117113
Given I have a "NativeCurlClient" client
118114
And I create a project with name "Test Project" and identifier "test-project"
@@ -154,7 +150,6 @@ Feature: Interacting with the REST API for projects
154150
updated_on
155151
"""
156152

157-
@project
158153
Scenario: Updating a project
159154
Given I have a "NativeCurlClient" client
160155
And I create a project with name "Test Project" and identifier "test-project"
@@ -167,7 +162,7 @@ Feature: Interacting with the REST API for projects
167162
And the response has the content ""
168163
And the returned data is exactly ""
169164

170-
@project @since50000
165+
@since50000
171166
Scenario: Closing a project
172167
Given I have a "NativeCurlClient" client
173168
And I create a project with name "Test Project" and identifier "test-project"
@@ -181,7 +176,7 @@ Feature: Interacting with the REST API for projects
181176
| property | value |
182177
| status | 5 |
183178

184-
@project @since50000
179+
@since50000
185180
Scenario: Reopening a project
186181
Given I have a "NativeCurlClient" client
187182
And I create a project with name "Test Project" and identifier "test-project"
@@ -196,7 +191,7 @@ Feature: Interacting with the REST API for projects
196191
| property | value |
197192
| status | 1 |
198193

199-
@project @since50000
194+
@since50000
200195
Scenario: Archiving a project
201196
Given I have a "NativeCurlClient" client
202197
And I create a project with name "Test Project" and identifier "test-project"
@@ -206,7 +201,7 @@ Feature: Interacting with the REST API for projects
206201
And the response has the content ""
207202
And the returned data is true
208203

209-
@project @since50000 @error
204+
@since50000 @error
210205
Scenario: Showing an archived project is not possible
211206
Given I have a "NativeCurlClient" client
212207
And I create a project with name "Test Project" and identifier "test-project"
@@ -217,7 +212,7 @@ Feature: Interacting with the REST API for projects
217212
And the response has the content ""
218213
And the returned data is false
219214

220-
@project @since50000
215+
@since50000
221216
Scenario: Unarchiving a project
222217
Given I have a "NativeCurlClient" client
223218
And I create a project with name "Test Project" and identifier "test-project"
@@ -232,7 +227,6 @@ Feature: Interacting with the REST API for projects
232227
| property | value |
233228
| status | 1 |
234229

235-
@project
236230
Scenario: Removing a project
237231
Given I have a "NativeCurlClient" client
238232
And I create a project with name "Test Project" and identifier "test-project"

0 commit comments

Comments
 (0)