Reword Spaces API scenario descriptions

This commit is contained in:
Phil Davis
2021-12-21 13:55:59 +05:45
parent 0718f96446
commit b7fc7ee990
5 changed files with 50 additions and 52 deletions
@@ -1,6 +1,6 @@
@api @skipOnOcV10
Feature: Share spaces
As the owner of a space
As the owner of a space
I want to be able to add members to a space, and to remove access for them
Note - this feature is run in CI with ACCOUNTS_HASH_DIFFICULTY set to the default for production
@@ -10,16 +10,16 @@ Feature: Share spaces
Given user "Alice" has been created with default attributes and without skeleton files
And user "Brian" has been created with default attributes and without skeleton files
And the administrator has given "Alice" the role "Admin" using the settings api
Scenario: Alice shares space to Brian, she expects a 200 response code
Given user "Alice" has created a space "Space to share" of type "project" with quota "10"
Scenario: A user can share a space to another user
Given user "Alice" has created a space "Space to share" of type "project" with quota "10"
When user "Alice" shares a space "Space to share" to user "Brian"
Then the HTTP status code should be "200"
Scenario: Brian checks that a shared space is available
Given user "Alice" has created a space "Share space to Brian" of type "project" with quota "10"
Scenario: A user can see that a received shared space is available
Given user "Alice" has created a space "Share space to Brian" of type "project" with quota "10"
And user "Alice" has shared a space "Share space to Brian" to user "Brian"
When user "Brian" lists all available spaces via the GraphApi
Then the json responded should contain a space "Share space to Brian" with these key and value pairs:
@@ -31,24 +31,24 @@ Feature: Share spaces
| root@@@webDavUrl | %base_url%/dav/spaces/%space_id% |
Scenario: Brian can see files in shared space
Given user "Alice" has created a space "Share space with file" of type "project" with quota "10"
Scenario: A user can see a file in a received shared space
Given user "Alice" has created a space "Share space with file" of type "project" with quota "10"
And user "Alice" has uploaded a file inside space "Share space with file" with content "Test" to "test.txt"
When user "Alice" has shared a space "Share space with file" to user "Brian"
Then for user "Brian" the space "Share space with file" should contain these entries:
| test.txt |
Scenario: Brian can see folder in shared space
Given user "Alice" has created a space "Share space with folder" of type "project" with quota "10"
And user "Alice" has created a folder "Folder Main" in space "Share space with folder"
Scenario: A user can see a folder in received shared space
Given user "Alice" has created a space "Share space with folder" of type "project" with quota "10"
And user "Alice" has created a folder "Folder Main" in space "Share space with folder"
When user "Alice" has shared a space "Share space with folder" to user "Brian"
Then for user "Brian" the space "Share space with folder" should contain these entries:
| Folder Main |
Scenario: When Alice unshares space, the space becomes unavailable to Brian
Given user "Alice" has created a space "Unshare space" of type "project" with quota "10"
Scenario: When a user unshares a space, the space becomes unavailable to the receiver
Given user "Alice" has created a space "Unshare space" of type "project" with quota "10"
And user "Alice" has shared a space "Unshare space" to user "Brian"
When user "Brian" lists all available spaces via the GraphApi
Then the json responded should contain a space "Unshare space" with these key and value pairs:
@@ -60,4 +60,3 @@ Feature: Share spaces
Then the HTTP status code should be "200"
And user "Brian" lists all available spaces via the GraphApi
And the json responded should not contain a space "Unshare space"