Skip to content

Commit

Permalink
Merge pull request #413 from Art4/support-for-many-issuecategories
Browse files Browse the repository at this point in the history 
Support for many issue_categories
  • Loading branch information
@Art4
Art4 authored Jul 5, 2024
2 parents 3de40b4 + d3e35ba commit 8fab7fb
Show file tree
Hide file tree
Showing 2 changed files with 44 additions and 23 deletions.
28 changes: 28 additions & 0 deletions tests/Behat/Bootstrap/IssueCategoryContextTrait.php
View file
Original file line number Diff line number Diff line change
Expand Up @@ -9,6 +9,34 @@

trait IssueCategoryContextTrait
{
/**
* @Given I create :count issue categories for project identifier :identifier
*/
public function iCreateIssueCategoriesForProjectIdentifier(int $count, $identifier)
{
while ($count > 0) {
$this->iCreateAnIssueCategoryForProjectIdentifierAndWithTheName(
$identifier,
'Issue Category ' . $count,
);

$count--;
}
}

/**
* @When I create an issue category for project identifier :identifier and with the name :name
*/
public function iCreateAnIssueCategoryForProjectIdentifierAndWithTheName($identifier, $name)
{
$table = new TableNode([
['property', 'value'],
['name', $name],
]);

$this->iCreateAnIssueCategoryForProjectIdentifierAndWithTheFollowingData($identifier, $table);
}

/**
* @When I create an issue category for project identifier :identifier and with the following data
*/
Expand Down
39 changes: 16 additions & 23 deletions tests/Behat/features/issue_category.feature
View file
Original file line number Diff line number Diff line change
Expand Up @@ -7,9 +7,7 @@ Feature: Interacting with the REST API for issue categories
Scenario: Creating an issue category with miminal data
Given I have a "NativeCurlClient" client
And I create a project with name "Test Project" and identifier "test-project"
When I create an issue category for project identifier "test-project" and with the following data
| property | value |
| name | Category name |
When I create an issue category for project identifier "test-project" and with the name "Category name"
Then the response has the status code "201"
And the response has the content type "application/xml"
And the returned data is an instance of "SimpleXMLElement"
Expand Down Expand Up @@ -101,12 +99,8 @@ Feature: Interacting with the REST API for issue categories
Scenario: Listing of multiple issue categories
Given I have a "NativeCurlClient" client
And I create a project with name "Test Project" and identifier "test-project"
And I create an issue category for project identifier "test-project" and with the following data
| property | value |
| name | Category name B |
And I create an issue category for project identifier "test-project" and with the following data
| property | value |
| name | Category name A |
And I create an issue category for project identifier "test-project" and with the name "Category name B"
And I create an issue category for project identifier "test-project" and with the name "Category name A"
When I list all issue categories for project identifier "test-project"
Then the response has the status code "200"
And the response has the content type "application/json"
Expand Down Expand Up @@ -154,12 +148,8 @@ Feature: Interacting with the REST API for issue categories
Scenario: Listing of multiple issue category names
Given I have a "NativeCurlClient" client
And I create a project with name "Test Project" and identifier "test-project"
And I create an issue category for project identifier "test-project" and with the following data
| property | value |
| name | Category name B |
And I create an issue category for project identifier "test-project" and with the following data
| property | value |
| name | Category name A |
And I create an issue category for project identifier "test-project" and with the name "Category name B"
And I create an issue category for project identifier "test-project" and with the name "Category name A"
When I list all issue category names for project identifier "test-project"
Then the response has the status code "200"
And the response has the content type "application/json"
Expand All @@ -168,13 +158,19 @@ Feature: Interacting with the REST API for issue categories
| 1 | Category name B |
| 2 | Category name A |

Scenario: Listing a lot of issue category names
Given I have a "NativeCurlClient" client
And I create a project with name "Test Project" and identifier "test-project"
And I create "108" issue categories for project identifier "test-project"
When I list all issue category names for project identifier "test-project"
Then the response has the status code "200"
And the response has the content type "application/json"
And the returned data contains "108" items

Scenario: Updating an issue category with all data
Given I have a "NativeCurlClient" client
And I create a project with name "Test Project" and identifier "test-project"
And I create an issue category for project identifier "test-project" and with the following data
| property | value |
| name | Category name |
| assigned_to_id | 1 |
And I create an issue category for project identifier "test-project" and with the name "Category name"
When I update the issue category with id "1" and the following data
| property | value |
| name | New category name |
Expand All @@ -187,10 +183,7 @@ Feature: Interacting with the REST API for issue categories
Scenario: Deleting an issue category
Given I have a "NativeCurlClient" client
And I create a project with name "Test Project" and identifier "test-project"
And I create an issue category for project identifier "test-project" and with the following data
| property | value |
| name | Category name |
| assigned_to_id | 1 |
And I create an issue category for project identifier "test-project" and with the name "Category name"
When I remove the issue category with id "1"
Then the response has the status code "204"
And the response has an empty content type
Expand Down

0 comments on commit 8fab7fb

Please sign in to comment.