using Graph instead Of Setting Method In Tests

This commit is contained in:
Viktor Scharf
2023-06-15 17:03:53 +02:00
parent 3cdc3bc485
commit 5867dae18f
44 changed files with 170 additions and 170 deletions
@@ -14,7 +14,7 @@ Feature: Disabling and deleting space
| Brian |
| Bob |
| Carol |
And the administrator has given "Alice" the role "Space Admin" using the settings api
And the administrator has assigned the role "Space Admin" to user "Alice" using the Graph API
And user "Alice" has created a space "Project Moon" with the default quota using the GraphApi
And user "Alice" has shared a space "Project Moon" with settings:
| shareWith | Brian |
@@ -25,7 +25,7 @@ Feature: Disabling and deleting space
Scenario Outline: user can disable their own space via the Graph API
Given the administrator has given "Alice" the role "<role>" using the settings api
Given the administrator has assigned the role "<role>" to user "Alice" using the Graph API
When user "Alice" disables a space "Project Moon"
Then the HTTP status code should be "204"
And the user "Brian" should not have a space called "Project Moon"
@@ -39,7 +39,7 @@ Feature: Disabling and deleting space
Scenario Outline: user with role user and user light cannot disable other space via the Graph API
Given the administrator has given "Carol" the role "<role>" using the settings api
Given the administrator has assigned the role "<role>" to user "Carol" using the Graph API
When user "Carol" tries to disable a space "Project Moon" owned by user "Alice"
Then the HTTP status code should be "404"
And the user "Brian" should have a space called "Project Moon"
@@ -61,7 +61,7 @@ Feature: Disabling and deleting space
Scenario Outline: user cannot delete their own space without first disabling it
Given the administrator has given "Alice" the role "<role>" using the settings api
Given the administrator has assigned the role "<role>" to user "Alice" using the Graph API
When user "Alice" deletes a space "Project Moon"
Then the HTTP status code should be "400"
And the user "Alice" should have a space called "Project Moon"
@@ -74,7 +74,7 @@ Feature: Disabling and deleting space
Scenario Outline: user can delete their own disabled space via the Graph API
Given the administrator has given "Alice" the role "<role>" using the settings api
Given the administrator has assigned the role "<role>" to user "Alice" using the Graph API
And user "Alice" has disabled a space "Project Moon"
When user "Alice" deletes a space "Project Moon"
Then the HTTP status code should be "204"
@@ -88,7 +88,7 @@ Feature: Disabling and deleting space
Scenario Outline: an admin and space manager can disable other space via the Graph API
Given the administrator has given "Carol" the role "<role>" using the settings api
Given the administrator has assigned the role "<role>" to user "Carol" using the Graph API
When user "Carol" disables a space "Project Moon" owned by user "Alice"
Then the HTTP status code should be "204"
And the user "Carol" should not have a space called "Project Moon"
@@ -99,7 +99,7 @@ Feature: Disabling and deleting space
Scenario Outline: an admin and space manager can delete other disabled Space
Given the administrator has given "Carol" the role "<role>" using the settings api
Given the administrator has assigned the role "<role>" to user "Carol" using the Graph API
And user "Alice" has disabled a space "Project Moon"
When user "Carol" deletes a space "Project Moon" owned by user "Alice"
Then the HTTP status code should be "204"
@@ -112,7 +112,7 @@ Feature: Disabling and deleting space
Scenario Outline: user with role user and user light cannot delete others disabled space via the Graph API
Given the administrator has given "Carol" the role "<role>" using the settings api
Given the administrator has assigned the role "<role>" to user "Carol" using the Graph API
And user "Alice" has disabled a space "Project Moon"
When user "Carol" tries to delete a space "Project Moon" owned by user "Alice"
Then the HTTP status code should be "404"