Reuse the core code
This commit is contained in:
@@ -16,6 +16,7 @@ Feature: Change data of space
|
||||
And user "Alice" has created a space "Project Jupiter" of type "project" with quota "20"
|
||||
And user "Alice" has shared a space "Project Jupiter" to user "Brian" with role "editor"
|
||||
And user "Alice" has shared a space "Project Jupiter" to user "Bob" with role "viewer"
|
||||
And using spaces DAV path
|
||||
|
||||
|
||||
Scenario Outline: Only space admin user can change the name of a Space via the Graph API
|
||||
|
||||
@@ -9,6 +9,7 @@ Feature: copy file
|
||||
| username |
|
||||
| Alice |
|
||||
| Brian |
|
||||
And using spaces DAV path
|
||||
|
||||
|
||||
Scenario Outline: Copying a file within a same space project with role manager and editor
|
||||
@@ -527,9 +528,9 @@ Feature: copy file
|
||||
Then the HTTP status code should be "204"
|
||||
And as "Alice" folder "/Sample-Folder-A/sample-folder-b/sample-folder-c" should exist
|
||||
And for user "Alice" folder "BRIAN-FOLDER" of the space "Shares Jail" should contain these entries:
|
||||
| /second-level-folder/third-level-folder/sample-folder-c |
|
||||
| /second-level-folder/third-level-folder/sample-folder-c/ |
|
||||
And for user "Brian" folder "BRIAN-FOLDER" of the space "Personal" should contain these files:
|
||||
| /second-level-folder/third-level-folder/sample-folder-c |
|
||||
| /second-level-folder/third-level-folder/sample-folder-c/ |
|
||||
And the response when user "Alice" gets the info of the last share should include
|
||||
| file_target | /Shares/BRIAN-FOLDER |
|
||||
|
||||
@@ -594,7 +595,7 @@ Feature: copy file
|
||||
And for user "Alice" folder "BRIAN-FOLDER" of the space "Shares Jail" should contain these entries:
|
||||
| /second-level-folder/third-level-file.txt/third-level-folder |
|
||||
And for user "Alice" folder "BRIAN-FOLDER" of the space "Shares Jail" should not contain these entries:
|
||||
| /second-level-folder/second-level-folder |
|
||||
| /second-level-folder/second-level-folder/ |
|
||||
And the response when user "Alice" gets the info of the last share should include
|
||||
| file_target | /Shares/BRIAN-FOLDER |
|
||||
|
||||
@@ -616,7 +617,7 @@ Feature: copy file
|
||||
Then the HTTP status code should be "204"
|
||||
And as "Alice" folder "/Sample-Folder-A/sample-folder-b/sample-folder-c" should exist
|
||||
And for user "Alice" folder "BRIAN-FOLDER" of the space "Shares Jail" should contain these files:
|
||||
| /second-level-folder/third-level-folder/sample-folder-c |
|
||||
| /second-level-folder/third-level-folder/sample-folder-c/ |
|
||||
And the response when user "Alice" gets the info of the last share should include
|
||||
| file_target | /Shares/BRIAN-FOLDER |
|
||||
|
||||
@@ -684,8 +685,8 @@ Feature: copy file
|
||||
When user "Alice" copies folder "/FOLDER/second-level-folder" from space "Personal" to "/BRIAN-FOLDER/second-level-folder/third-level-file.txt" inside space "Shares Jail" using the WebDAV API
|
||||
Then the HTTP status code should be "204"
|
||||
And for user "Alice" folder "BRIAN-FOLDER" of the space "Shares Jail" should contain these files:
|
||||
| /second-level-folder/third-level-file.txt |
|
||||
| /second-level-folder/third-level-file.txt/third-level-folder |
|
||||
| /second-level-folder/third-level-file.txt/ |
|
||||
| /second-level-folder/third-level-file.txt/third-level-folder/ |
|
||||
And as "Alice" folder "FOLDER/second-level-folder/third-level-folder" should exist
|
||||
And for user "Alice" folder "BRIAN-FOLDER" of the space "Shares Jail" should not contain these files:
|
||||
| /second-level-folder/second-level-folder |
|
||||
|
||||
@@ -18,12 +18,12 @@ Feature: create file or folder named similar to Shares folder
|
||||
When user "Brian" creates folder "<folder_name>" using the WebDAV API
|
||||
Then the HTTP status code should be "201"
|
||||
And for user "Brian" the space "Personal" should contain these entries:
|
||||
| /<folder_name> |
|
||||
| <folder_name>/ |
|
||||
Examples:
|
||||
| folder_name |
|
||||
| /Share |
|
||||
| /shares |
|
||||
| /Share1 |
|
||||
| Share |
|
||||
| shares |
|
||||
| Share1 |
|
||||
|
||||
Scenario Outline: create a file with a name similar to Shares
|
||||
Given using spaces DAV path
|
||||
@@ -31,25 +31,25 @@ Feature: create file or folder named similar to Shares folder
|
||||
Then the HTTP status code should be "201"
|
||||
And the content of file "<file_name>" for user "Brian" should be "some text"
|
||||
And for user "Brian" the space "Personal" should contain these entries:
|
||||
| /<file_name> |
|
||||
| <file_name> |
|
||||
And for user "Brian" the space "Shares Jail" should contain these entries:
|
||||
| /FOLDER |
|
||||
| FOLDER/ |
|
||||
Examples:
|
||||
| file_name |
|
||||
| /Share |
|
||||
| /shares |
|
||||
| /Share1 |
|
||||
| Share |
|
||||
| shares |
|
||||
| Share1 |
|
||||
|
||||
Scenario: try to create a folder named Shares
|
||||
Given using spaces DAV path
|
||||
When user "Brian" creates folder "/Shares" using the WebDAV API
|
||||
Then the HTTP status code should be "201"
|
||||
And for user "Brian" the space "Shares Jail" should contain these entries:
|
||||
| /FOLDER |
|
||||
| FOLDER/ |
|
||||
|
||||
Scenario: try to create a file named Shares
|
||||
Given using spaces DAV path
|
||||
When user "Brian" uploads file with content "some text" to "/Shares" using the WebDAV API
|
||||
Then the HTTP status code should be "201"
|
||||
And for user "Brian" the space "Shares Jail" should contain these entries:
|
||||
| /FOLDER |
|
||||
| FOLDER/ |
|
||||
|
||||
@@ -11,6 +11,7 @@ Feature: Download file in project space
|
||||
| Alice |
|
||||
| Brian |
|
||||
| Bob |
|
||||
And using spaces DAV path
|
||||
And the administrator has given "Alice" the role "Space Admin" using the settings api
|
||||
And user "Alice" has created a space "download file" with the default quota using the GraphApi
|
||||
And user "Alice" has uploaded a file inside space "download file" with content "some content" to "file.txt"
|
||||
|
||||
@@ -14,6 +14,7 @@ Feature: A manager of the space can edit public link
|
||||
| username |
|
||||
| Alice |
|
||||
| Brian |
|
||||
And using spaces DAV path
|
||||
And the administrator has given "Alice" the role "Space Admin" using the settings api
|
||||
And user "Alice" has created a space "edit space" with the default quota using the GraphApi
|
||||
And user "Alice" has created a public link share of the space "edit space" with settings:
|
||||
|
||||
@@ -11,6 +11,7 @@ Feature: Preview file in project space
|
||||
| Alice |
|
||||
And the administrator has given "Alice" the role "Space Admin" using the settings api
|
||||
And user "Alice" has created a space "previews of the files" with the default quota using the GraphApi
|
||||
And using spaces DAV path
|
||||
|
||||
|
||||
Scenario Outline: An user can preview created txt files in the project space
|
||||
|
||||
@@ -8,6 +8,7 @@ Feature: List and create spaces
|
||||
|
||||
Background:
|
||||
Given user "Alice" has been created with default attributes and without skeleton files
|
||||
And using spaces DAV path
|
||||
|
||||
|
||||
Scenario: An ordinary user can request information about their Space via the Graph API
|
||||
|
||||
@@ -9,6 +9,7 @@ Feature: move (rename) file
|
||||
| username |
|
||||
| Alice |
|
||||
| Brian |
|
||||
And using spaces DAV path
|
||||
|
||||
Scenario Outline: Moving a file within same space project with role manager and editor
|
||||
Given the administrator has given "Brian" the role "Space Admin" using the settings api
|
||||
|
||||
@@ -14,6 +14,7 @@ Feature: State of the quota
|
||||
Background:
|
||||
Given user "Alice" has been created with default attributes and without skeleton files
|
||||
And the administrator has given "Alice" the role "Space Admin" using the settings api
|
||||
And using spaces DAV path
|
||||
|
||||
|
||||
Scenario Outline: Quota information is returned in the list of spaces returned via the Graph API
|
||||
|
||||
@@ -13,6 +13,7 @@ Feature: Remove files, folder
|
||||
| username |
|
||||
| Alice |
|
||||
| Brian |
|
||||
And using spaces DAV path
|
||||
And the administrator has given "Alice" the role "Space Admin" using the settings api
|
||||
And user "Alice" has created a space "delete objects" with the default quota using the GraphApi
|
||||
And user "Alice" has created a folder "folderForDeleting/sub1/sub2" in space "delete objects"
|
||||
|
||||
@@ -14,6 +14,7 @@ Feature: Restore files, folder
|
||||
| Brian |
|
||||
| Bob |
|
||||
| Carol |
|
||||
And using spaces DAV path
|
||||
And the administrator has given "Alice" the role "Space Admin" using the settings api
|
||||
And user "Alice" creates a space "restore objects" of type "project" with the default quota using the GraphApi
|
||||
And user "Alice" has created a folder "newFolder" in space "restore objects"
|
||||
|
||||
@@ -16,6 +16,7 @@ Feature: Restoring space
|
||||
| Bob |
|
||||
And the administrator has given "Alice" the role "Space Admin" using the settings api
|
||||
And user "Alice" has created a space "restore a space" of type "project" with quota "10"
|
||||
And using spaces DAV path
|
||||
|
||||
|
||||
Scenario: An owner can restore a Space via the Graph API
|
||||
|
||||
@@ -10,12 +10,12 @@ Feature: Search
|
||||
| username |
|
||||
| Alice |
|
||||
| Brian |
|
||||
And using new DAV path
|
||||
And using spaces DAV path
|
||||
And the administrator has given "Alice" the role "Space Admin" using the settings api
|
||||
And user "Alice" has created a space "find data" with the default quota using the GraphApi
|
||||
And user "Alice" has created a folder "folder/SubFolder1/subFOLDER2" in space "find data"
|
||||
And user "Alice" has uploaded a file inside space "find data" with content "some content" to "folder/SubFolder1/subFOLDER2/insideTheFolder.txt"
|
||||
|
||||
And using new DAV path
|
||||
|
||||
Scenario: Alice can find data from the project space
|
||||
When user "Alice" searches for "fol" using the WebDAV API
|
||||
@@ -51,7 +51,7 @@ Feature: Search
|
||||
| /SubFolder1/subFOLDER2 |
|
||||
| /SubFolder1/subFOLDER2/insideTheFolder.txt |
|
||||
And for user "Brian" the search result should contain space "mountpoint/folder"
|
||||
|
||||
|
||||
|
||||
Scenario: User can find hidden file
|
||||
Given user "Alice" has created a folder ".space" in space "find data"
|
||||
@@ -72,7 +72,7 @@ Feature: Search
|
||||
| /SubFolder1/subFOLDER2 |
|
||||
| /SubFolder1/subFOLDER2/insideTheFolder.txt |
|
||||
|
||||
|
||||
|
||||
Scenario: User cannot find declined folder
|
||||
Given user "Alice" shares the following entity "folder" inside of space "find data" with user "Brian" with role "viewer"
|
||||
And user "Brian" has declined share "/folder" offered by user "Alice"
|
||||
@@ -90,7 +90,7 @@ Feature: Search
|
||||
When user "Alice" searches for "folder" using the WebDAV API
|
||||
Then the HTTP status code should be "207"
|
||||
And the search result should contain "0" entries
|
||||
|
||||
|
||||
|
||||
Scenario: User can find project space by name
|
||||
When user "Alice" searches for "find data" using the WebDAV API
|
||||
|
||||
@@ -14,6 +14,7 @@ Feature: Share spaces
|
||||
| Bob |
|
||||
And the administrator has given "Alice" the role "Space Admin" using the settings api
|
||||
And user "Alice" has created a space "share space" with the default quota using the GraphApi
|
||||
And using spaces DAV path
|
||||
|
||||
|
||||
Scenario Outline:: A user can share a space to another user
|
||||
|
||||
@@ -11,6 +11,7 @@ Feature: Share spaces via link
|
||||
| username |
|
||||
| Alice |
|
||||
| Brian |
|
||||
And using spaces DAV path
|
||||
And the administrator has given "Alice" the role "Space Admin" using the settings api
|
||||
And user "Alice" has created a space "share space" with the default quota using the GraphApi
|
||||
And user "Alice" has uploaded a file inside space "share space" with content "some content" to "test.txt"
|
||||
|
||||
@@ -13,13 +13,15 @@ Feature: Share a file or folder that is inside a space
|
||||
| Alice |
|
||||
| Brian |
|
||||
| Bob |
|
||||
And using spaces DAV path
|
||||
And the administrator has given "Alice" the role "Space Admin" using the settings api
|
||||
And user "Alice" has created a space "share sub-item" with the default quota using the GraphApi
|
||||
And user "Alice" has created a folder "folder" in space "share sub-item"
|
||||
And user "Alice" has uploaded a file inside space "share sub-item" with content "some content" to "file.txt"
|
||||
And using new DAV path
|
||||
|
||||
|
||||
Scenario Outline: A manager of the space can share an entity inside project space to another user with role:
|
||||
|
||||
Scenario Outline: A manager of the space can share an entity inside project space to another user with role
|
||||
When user "Alice" shares the following entity "<entity>" inside of space "share sub-item" with user "Brian" with role "<role>"
|
||||
Then the HTTP status code should be "200"
|
||||
And the OCS status code should be "200"
|
||||
|
||||
@@ -23,6 +23,7 @@ Feature: Share a file or folder that is inside a space via public link
|
||||
| username |
|
||||
| Alice |
|
||||
| Brian |
|
||||
And using spaces DAV path
|
||||
And the administrator has given "Alice" the role "Space Admin" using the settings api
|
||||
And user "Alice" has created a space "share sub-item" with the default quota using the GraphApi
|
||||
And user "Alice" has created a folder "folder" in space "share sub-item"
|
||||
|
||||
@@ -14,6 +14,7 @@ Feature: Upload files into a space
|
||||
| Bob |
|
||||
And the administrator has given "Alice" the role "Space Admin" using the settings api
|
||||
And user "Alice" has created a space "Project Ceres" of type "project" with quota "2000"
|
||||
And using spaces DAV path
|
||||
|
||||
|
||||
Scenario Outline: An user creates a folder in the Space via the Graph API
|
||||
|
||||
Reference in New Issue
Block a user