@@ -7,9 +7,7 @@ Feature: Interacting with the REST API for issue categories
7
7
Scenario : Creating an issue category with miminal data
8
8
Given I have a "NativeCurlClient" client
9
9
And I create a project with name "Test Project" and identifier "test-project"
10
- When I create an issue category for project identifier "test-project" and with the following data
11
- | property | value |
12
- | name | Category name |
10
+ When I create an issue category for project identifier "test-project" and with the name "Category name"
13
11
Then the response has the status code "201"
14
12
And the response has the content type "application/xml"
15
13
And the returned data is an instance of "SimpleXMLElement"
@@ -101,12 +99,8 @@ Feature: Interacting with the REST API for issue categories
101
99
Scenario : Listing of multiple issue categories
102
100
Given I have a "NativeCurlClient" client
103
101
And I create a project with name "Test Project" and identifier "test-project"
104
- And I create an issue category for project identifier "test-project" and with the following data
105
- | property | value |
106
- | name | Category name B |
107
- And I create an issue category for project identifier "test-project" and with the following data
108
- | property | value |
109
- | name | Category name A |
102
+ And I create an issue category for project identifier "test-project" and with the name "Category name B"
103
+ And I create an issue category for project identifier "test-project" and with the name "Category name A"
110
104
When I list all issue categories for project identifier "test-project"
111
105
Then the response has the status code "200"
112
106
And the response has the content type "application/json"
@@ -154,12 +148,8 @@ Feature: Interacting with the REST API for issue categories
154
148
Scenario : Listing of multiple issue category names
155
149
Given I have a "NativeCurlClient" client
156
150
And I create a project with name "Test Project" and identifier "test-project"
157
- And I create an issue category for project identifier "test-project" and with the following data
158
- | property | value |
159
- | name | Category name B |
160
- And I create an issue category for project identifier "test-project" and with the following data
161
- | property | value |
162
- | name | Category name A |
151
+ And I create an issue category for project identifier "test-project" and with the name "Category name B"
152
+ And I create an issue category for project identifier "test-project" and with the name "Category name A"
163
153
When I list all issue category names for project identifier "test-project"
164
154
Then the response has the status code "200"
165
155
And the response has the content type "application/json"
@@ -168,13 +158,19 @@ Feature: Interacting with the REST API for issue categories
168
158
| 1 | Category name B |
169
159
| 2 | Category name A |
170
160
161
+ Scenario : Listing a lot of issue category names
162
+ Given I have a "NativeCurlClient" client
163
+ And I create a project with name "Test Project" and identifier "test-project"
164
+ And I create "108" issue categories for project identifier "test-project"
165
+ When I list all issue category names for project identifier "test-project"
166
+ Then the response has the status code "200"
167
+ And the response has the content type "application/json"
168
+ And the returned data contains "108" items
169
+
171
170
Scenario : Updating an issue category with all data
172
171
Given I have a "NativeCurlClient" client
173
172
And I create a project with name "Test Project" and identifier "test-project"
174
- And I create an issue category for project identifier "test-project" and with the following data
175
- | property | value |
176
- | name | Category name |
177
- | assigned_to_id | 1 |
173
+ And I create an issue category for project identifier "test-project" and with the name "Category name"
178
174
When I update the issue category with id "1" and the following data
179
175
| property | value |
180
176
| name | New category name |
@@ -187,10 +183,7 @@ Feature: Interacting with the REST API for issue categories
187
183
Scenario : Deleting an issue category
188
184
Given I have a "NativeCurlClient" client
189
185
And I create a project with name "Test Project" and identifier "test-project"
190
- And I create an issue category for project identifier "test-project" and with the following data
191
- | property | value |
192
- | name | Category name |
193
- | assigned_to_id | 1 |
186
+ And I create an issue category for project identifier "test-project" and with the name "Category name"
194
187
When I remove the issue category with id "1"
195
188
Then the response has the status code "204"
196
189
And the response has an empty content type
0 commit comments