-
Notifications
You must be signed in to change notification settings - Fork 187
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #2900 from owncloud/shareSpace
[tests-only] ApiTest: share space
- Loading branch information
Showing
3 changed files
with
199 additions
and
2 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,63 @@ | ||
@api @skipOnOcV10 | ||
Feature: Share spaces | ||
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 | ||
See https://github.com/owncloud/ocis/issues/1542 and https://github.com/owncloud/ocis/pull/839 | ||
|
||
Background: | ||
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" | ||
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" | ||
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: | ||
| key | value | | ||
| driveType | share | | ||
| id | %space_id% | | ||
| name | Share space to Brian | | ||
| quota@@@state | normal | | ||
| 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" | ||
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" | ||
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" | ||
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: | ||
| key | value | | ||
| driveType | share | | ||
| id | %space_id% | | ||
| name | Unshare space | | ||
When user "Alice" unshares a space "Unshare space" to user "Brian" | ||
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" | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters