rebranding tests
This commit is contained in:
Viktor Scharf
@@ -2,7 +2,7 @@
|
||||
Feature: add user
|
||||
As an admin
|
||||
I want to be able to add users and store their password with the full hash difficulty
|
||||
So that I can give people controlled individual access to resources on the ownCloud server
|
||||
So that I can give people controlled individual access to resources on the OpenCloud server
|
||||
|
||||
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
|
||||
|
||||
+2
-2
@@ -11,10 +11,10 @@ Feature: sharing
|
||||
Scenario Outline: creating a share of a file with a user
|
||||
Given using OCS API version "<ocs-api-version>"
|
||||
And user "Alice" has been created with default attributes
|
||||
And user "Alice" has uploaded file with content "ownCloud test text file 0" to "/textfile0.txt"
|
||||
And user "Alice" has uploaded file with content "OpenCloud test text file 0" to "/textfile0.txt"
|
||||
And user "Brian" has been created with default attributes
|
||||
When user "Alice" shares file "textfile0.txt" with user "Brian" using the sharing API
|
||||
And the content of file "/Shares/textfile0.txt" for user "Brian" should be "ownCloud test text file 0"
|
||||
And the content of file "/Shares/textfile0.txt" for user "Brian" should be "OpenCloud test text file 0"
|
||||
Examples:
|
||||
| ocs-api-version |
|
||||
| 1 |
|
||||
|
||||
@@ -8,7 +8,7 @@ Feature: check activities
|
||||
|
||||
@issue-9712
|
||||
Scenario: check activities after uploading a file and a folder
|
||||
Given user "Alice" has uploaded file with content "ownCloud test text file 0" to "/textfile.txt"
|
||||
Given user "Alice" has uploaded file with content "OpenCloud test text file 0" to "/textfile.txt"
|
||||
And user "Alice" has created folder "/FOLDER"
|
||||
When user "Alice" lists the activities of file "textfile.txt" from space "Personal" using the Graph API
|
||||
Then the HTTP status code should be "200"
|
||||
@@ -185,8 +185,8 @@ Feature: check activities
|
||||
|
||||
@issue-10001
|
||||
Scenario: check edit activity of a file
|
||||
Given user "Alice" has uploaded file with content "ownCloud test text file" to "/textfile.txt"
|
||||
And user "Alice" has uploaded file with content "edited ownCloud test text file" to "/textfile.txt"
|
||||
Given user "Alice" has uploaded file with content "OpenCloud test text file" to "/textfile.txt"
|
||||
And user "Alice" has uploaded file with content "edited OpenCloud test text file" to "/textfile.txt"
|
||||
When user "Alice" lists the activities of file "/textfile.txt" from space "Personal" using the Graph API
|
||||
Then the HTTP status code should be "200"
|
||||
And the JSON data of the response should match
|
||||
@@ -290,7 +290,7 @@ Feature: check activities
|
||||
|
||||
@issue-9712
|
||||
Scenario: check activities after deleting a file and a folder
|
||||
Given user "Alice" has uploaded file with content "ownCloud test text file 0" to "/textfile.txt"
|
||||
Given user "Alice" has uploaded file with content "OpenCloud test text file 0" to "/textfile.txt"
|
||||
And user "Alice" has created folder "/FOLDER"
|
||||
And user "Alice" has deleted file "textfile.txt"
|
||||
And user "Alice" has deleted folder "FOLDER"
|
||||
@@ -667,7 +667,7 @@ Feature: check activities
|
||||
|
||||
|
||||
Scenario: check activities of destination file and folder after moving a file into it
|
||||
Given user "Alice" has uploaded file with content "ownCloud test text file" to "textfile.txt"
|
||||
Given user "Alice" has uploaded file with content "OpenCloud test text file" to "textfile.txt"
|
||||
And user "Alice" has created folder "/FOLDER"
|
||||
And user "Alice" has moved file "textfile.txt" to "FOLDER/textfile.txt"
|
||||
When user "Alice" lists the activities of file "FOLDER/textfile.txt" from space "Personal" using the Graph API
|
||||
@@ -1140,7 +1140,7 @@ Feature: check activities
|
||||
|
||||
|
||||
Scenario: check activities of destination file and folder after moving a file by renaming destination file
|
||||
Given user "Alice" has uploaded file with content "ownCloud test text file" to "textfile.txt"
|
||||
Given user "Alice" has uploaded file with content "OpenCloud test text file" to "textfile.txt"
|
||||
And user "Alice" has created folder "/FOLDER"
|
||||
And user "Alice" has moved file "textfile.txt" to "FOLDER/renamed.txt"
|
||||
When user "Alice" lists the activities of file "FOLDER/renamed.txt" from space "Personal" using the Graph API
|
||||
@@ -1612,7 +1612,7 @@ Feature: check activities
|
||||
|
||||
@issue-9712
|
||||
Scenario: check rename activity for a file and a folder
|
||||
Given user "Alice" has uploaded file with content "ownCloud test text file 0" to "/textfile.txt"
|
||||
Given user "Alice" has uploaded file with content "OpenCloud test text file 0" to "/textfile.txt"
|
||||
And user "Alice" has created folder "/FOLDER"
|
||||
And user "Alice" has moved file "textfile.txt" to "renamed.txt"
|
||||
And user "Alice" has moved folder "/FOLDER" to "RENAMED FOLDER"
|
||||
@@ -1840,7 +1840,7 @@ Feature: check activities
|
||||
Given user "Alice" has created folder "/New Folder"
|
||||
And user "Alice" has created folder "/New Folder/Folder"
|
||||
And user "Alice" has created folder "/New Folder/Sub Folder"
|
||||
And user "Alice" has uploaded file with content "ownCloud test text file 0" to "/New Folder/textfile.txt"
|
||||
And user "Alice" has uploaded file with content "OpenCloud test text file 0" to "/New Folder/textfile.txt"
|
||||
And user "Alice" has moved file "/New Folder/textfile.txt" to "/New Folder/Sub Folder/textfile.txt"
|
||||
And user "Alice" has moved folder "/New Folder/Folder" to "/New Folder/Sub Folder/Folder"
|
||||
And user "Alice" has moved file "/New Folder/Sub Folder/textfile.txt" to "/New Folder/Sub Folder/renamed.txt"
|
||||
@@ -2369,9 +2369,9 @@ Feature: check activities
|
||||
@issue-10210
|
||||
Scenario: check activities of a folder after renaming
|
||||
Given user "Alice" has created folder "FOLDER"
|
||||
And user "Alice" has uploaded file with content "ownCloud test text file" to "FOLDER/textfile.txt"
|
||||
And user "Alice" has uploaded file with content "OpenCloud test text file" to "FOLDER/textfile.txt"
|
||||
And user "Alice" has moved folder "FOLDER" to "RENAMED FOLDER"
|
||||
And user "Alice" has uploaded file with content "updated ownCloud test text file" to "RENAMED FOLDER/textfile.txt"
|
||||
And user "Alice" has uploaded file with content "updated OpenCloud test text file" to "RENAMED FOLDER/textfile.txt"
|
||||
When user "Alice" lists the activities of file "RENAMED FOLDER" from space "Personal" using the Graph API
|
||||
Then the HTTP status code should be "200"
|
||||
And the JSON data of the response should match
|
||||
@@ -2596,7 +2596,7 @@ Feature: check activities
|
||||
|
||||
@issue-9856 @issue-10127
|
||||
Scenario: check activity message with different language
|
||||
Given user "Alice" has uploaded file with content "ownCloud test text file" to "textfile.txt"
|
||||
Given user "Alice" has uploaded file with content "OpenCloud test text file" to "textfile.txt"
|
||||
And user "Alice" has switched the system language to "de" using the Graph API
|
||||
When user "Alice" lists the activities of file "textfile.txt" from space "Personal" using the Graph API
|
||||
Then the HTTP status code should be "200"
|
||||
@@ -2693,7 +2693,7 @@ Feature: check activities
|
||||
Scenario: check activity with -1 depth filter
|
||||
Given user "Alice" has created folder "/New Folder"
|
||||
And user "Alice" has created folder "/New Folder/Sub Folder"
|
||||
And user "Alice" has uploaded file with content "ownCloud test text file 0" to "/New Folder/Sub Folder/textfile.txt"
|
||||
And user "Alice" has uploaded file with content "OpenCloud test text file 0" to "/New Folder/Sub Folder/textfile.txt"
|
||||
When user "Alice" lists the activities of folder "New Folder" from space "Personal" with depth "-1" using the Graph API
|
||||
Then the HTTP status code should be "200"
|
||||
And the JSON data of the response should match
|
||||
@@ -2888,7 +2888,7 @@ Feature: check activities
|
||||
Scenario: check activity with depth filter
|
||||
Given user "Alice" has created folder "/New Folder"
|
||||
And user "Alice" has created folder "/New Folder/Sub Folder"
|
||||
And user "Alice" has uploaded file with content "ownCloud test text file 0" to "/New Folder/Sub Folder/textfile.txt"
|
||||
And user "Alice" has uploaded file with content "OpenCloud test text file 0" to "/New Folder/Sub Folder/textfile.txt"
|
||||
When user "Alice" lists the activities of folder "New Folder" from space "Personal" with depth "1" using the Graph API
|
||||
Then the HTTP status code should be "200"
|
||||
And the JSON data of the response should match
|
||||
@@ -3027,7 +3027,7 @@ Feature: check activities
|
||||
Scenario: check activity with limit filter
|
||||
Given user "Alice" has created folder "/New Folder"
|
||||
And user "Alice" has created folder "/New Folder/Sub Folder"
|
||||
And user "Alice" has uploaded file with content "ownCloud test text file 0" to "/New Folder/Sub Folder/textfile.txt"
|
||||
And user "Alice" has uploaded file with content "OpenCloud test text file 0" to "/New Folder/Sub Folder/textfile.txt"
|
||||
When user "Alice" lists the activities of folder "New Folder" from space "Personal" with limit "2" using the Graph API
|
||||
Then the HTTP status code should be "200"
|
||||
And the JSON data of the response should match
|
||||
@@ -3165,8 +3165,8 @@ Feature: check activities
|
||||
|
||||
Scenario: check activity with sort filter
|
||||
Given user "Alice" has created folder "/New Folder"
|
||||
And user "Alice" has uploaded file with content "ownCloud test text file 0" to "/New Folder/textfile.txt"
|
||||
And user "Alice" has uploaded file with content "updated ownCloud test text file" to "/New Folder/textfile.txt"
|
||||
And user "Alice" has uploaded file with content "OpenCloud test text file 0" to "/New Folder/textfile.txt"
|
||||
And user "Alice" has uploaded file with content "updated OpenCloud test text file" to "/New Folder/textfile.txt"
|
||||
When user "Alice" lists the activities of folder "New Folder" from space "Personal" with sort "asc" using the Graph API
|
||||
Then the HTTP status code should be "200"
|
||||
And the activities should be in the following order:
|
||||
@@ -3186,8 +3186,8 @@ Feature: check activities
|
||||
Scenario: check activities with limit and sort filters (asc/desc)
|
||||
Given user "Alice" has created folder "/New Folder"
|
||||
And user "Alice" has created folder "/New Folder/Sub Folder"
|
||||
And user "Alice" has uploaded file with content "ownCloud test text file 0" to "/New Folder/Sub Folder/textfile.txt"
|
||||
And user "Alice" has uploaded file with content "updated ownCloud test text file 0" to "/New Folder/Sub Folder/textfile.txt"
|
||||
And user "Alice" has uploaded file with content "OpenCloud test text file 0" to "/New Folder/Sub Folder/textfile.txt"
|
||||
And user "Alice" has uploaded file with content "updated OpenCloud test text file 0" to "/New Folder/Sub Folder/textfile.txt"
|
||||
When user "Alice" lists the activities of folder "New Folder" from space "Personal" with limit "2" and sort "asc" using the Graph API
|
||||
Then the HTTP status code should be "200"
|
||||
And the activities should be in the following order:
|
||||
@@ -3204,14 +3204,14 @@ Feature: check activities
|
||||
@issue-9860
|
||||
Scenario: user tries to check activities of another user's file
|
||||
Given user "Brian" has been created with default attributes
|
||||
And user "Alice" has uploaded file with content "ownCloud test text file" to "textfile.txt"
|
||||
And user "Alice" has uploaded file with content "updated ownCloud test text file" to "textfile.txt"
|
||||
And user "Alice" has uploaded file with content "OpenCloud test text file" to "textfile.txt"
|
||||
And user "Alice" has uploaded file with content "updated OpenCloud test text file" to "textfile.txt"
|
||||
When user "Brian" tries to list the activities of file "textfile.txt" from space "Personal" owned by user "Alice" using the Graph API
|
||||
Then the HTTP status code should be "403"
|
||||
|
||||
|
||||
Scenario: check activities of destination resources after copying a file
|
||||
Given user "Alice" has uploaded file with content "ownCloud test text file" to "textfile.txt"
|
||||
Given user "Alice" has uploaded file with content "OpenCloud test text file" to "textfile.txt"
|
||||
And user "Alice" has created folder "/FOLDER"
|
||||
And user "Alice" has copied file "textfile.txt" to "FOLDER/textfile.txt"
|
||||
When user "Alice" lists the activities of file "FOLDER/textfile.txt" from space "Personal" using the Graph API
|
||||
@@ -3433,7 +3433,7 @@ Feature: check activities
|
||||
|
||||
|
||||
Scenario: check activities of destination resources after copying a file by renaming the destination file
|
||||
Given user "Alice" has uploaded file with content "ownCloud test text file" to "textfile.txt"
|
||||
Given user "Alice" has uploaded file with content "OpenCloud test text file" to "textfile.txt"
|
||||
And user "Alice" has created folder "/FOLDER"
|
||||
And user "Alice" has copied file "textfile.txt" to "FOLDER/renamed.txt"
|
||||
When user "Alice" lists the activities of file "FOLDER/renamed.txt" from space "Personal" using the Graph API
|
||||
@@ -3656,7 +3656,7 @@ Feature: check activities
|
||||
|
||||
Scenario: check activities of destination resources after copying a file into same folder by renaming the destination file
|
||||
Given user "Alice" has created folder "/FOLDER"
|
||||
And user "Alice" has uploaded file with content "ownCloud test text file" to "FOLDER/textfile.txt"
|
||||
And user "Alice" has uploaded file with content "OpenCloud test text file" to "FOLDER/textfile.txt"
|
||||
And user "Alice" has copied file "FOLDER/textfile.txt" to "FOLDER/renamed.txt"
|
||||
When user "Alice" lists the activities of file "FOLDER/renamed.txt" from space "Personal" using the Graph API
|
||||
Then the HTTP status code should be "200"
|
||||
|
||||
@@ -9,7 +9,7 @@ Feature: check activities
|
||||
|
||||
|
||||
Scenario: check copy activity of destination resources
|
||||
Given user "Alice" has uploaded file with content "ownCloud test text file" to "textfile.txt"
|
||||
Given user "Alice" has uploaded file with content "OpenCloud test text file" to "textfile.txt"
|
||||
And we save it into "FILEID"
|
||||
And user "Alice" has created folder "newFolder"
|
||||
And user "Alice" has copied file with id "<<FILEID>>" as "textfile.txt" into folder "newFolder" inside space "Personal"
|
||||
@@ -232,7 +232,7 @@ Feature: check activities
|
||||
|
||||
|
||||
Scenario: check edit activity
|
||||
Given user "Alice" has uploaded file with content "ownCloud test text file" to "textfile.txt"
|
||||
Given user "Alice" has uploaded file with content "OpenCloud test text file" to "textfile.txt"
|
||||
And we save it into "FILEID"
|
||||
And user "Alice" has updated a file with content "updated content" using file-id "<<FILEID>>"
|
||||
When user "Alice" lists the activities of file "textfile.txt" from space "Personal" using the Graph API
|
||||
@@ -338,7 +338,7 @@ Feature: check activities
|
||||
|
||||
@issue-9744
|
||||
Scenario: check rename activity
|
||||
Given user "Alice" has uploaded file with content "ownCloud test text file" to "textfile.txt"
|
||||
Given user "Alice" has uploaded file with content "OpenCloud test text file" to "textfile.txt"
|
||||
And we save it into "FILEID"
|
||||
And user "Alice" has renamed file with id "<<FILEID>>" to "renamed.txt" inside space "Personal"
|
||||
When user "Alice" lists the activities of file "renamed.txt" from space "Personal" using the Graph API
|
||||
@@ -453,7 +453,7 @@ Feature: check activities
|
||||
|
||||
|
||||
Scenario: check activities of destination file and folder after moving a file using file-id
|
||||
Given user "Alice" has uploaded file with content "ownCloud test text file" to "textfile.txt"
|
||||
Given user "Alice" has uploaded file with content "OpenCloud test text file" to "textfile.txt"
|
||||
And we save it into "FILEID"
|
||||
And user "Alice" has created folder "New Folder"
|
||||
And user "Alice" has moved file with id "<<FILEID>>" as "textfile.txt" into folder "New Folder" inside space "Personal"
|
||||
@@ -906,7 +906,7 @@ Feature: check activities
|
||||
|
||||
|
||||
Scenario: check activities of destination file and folder after moving a file by renaming destination file using file-id
|
||||
Given user "Alice" has uploaded file with content "ownCloud test text file" to "textfile.txt"
|
||||
Given user "Alice" has uploaded file with content "OpenCloud test text file" to "textfile.txt"
|
||||
And we save it into "FILEID"
|
||||
And user "Alice" has created folder "/FOLDER"
|
||||
And user "Alice" has moved file with id "<<FILEID>>" as "renamed.txt" into folder "FOLDER" inside space "Personal"
|
||||
@@ -1380,7 +1380,7 @@ Feature: check activities
|
||||
|
||||
|
||||
Scenario: check activities of destination resources after copying a file by renaming the destination file
|
||||
Given user "Alice" has uploaded file with content "ownCloud test text file" to "textfile.txt"
|
||||
Given user "Alice" has uploaded file with content "OpenCloud test text file" to "textfile.txt"
|
||||
And we save it into "FILEID"
|
||||
And user "Alice" has created folder "newFolder"
|
||||
And user "Alice" has copied file with id "<<FILEID>>" as "renamed.txt" into folder "newFolder" inside space "Personal"
|
||||
@@ -1604,7 +1604,7 @@ Feature: check activities
|
||||
|
||||
Scenario: check activities of destination resources after copying file into same folder by renaming the destination file
|
||||
Given user "Alice" has created folder "/FOLDER"
|
||||
And user "Alice" has uploaded file with content "ownCloud test text file" to "FOLDER/textfile.txt"
|
||||
And user "Alice" has uploaded file with content "OpenCloud test text file" to "FOLDER/textfile.txt"
|
||||
And we save it into "FILEID"
|
||||
And user "Alice" has copied file with id "<<FILEID>>" as "renamed.txt" into folder "FOLDER" inside space "Personal"
|
||||
When user "Alice" lists the activities of file "FOLDER/renamed.txt" from space "Personal" using the Graph API
|
||||
|
||||
@@ -8,7 +8,7 @@ Feature: check share activity
|
||||
| username |
|
||||
| Alice |
|
||||
| Brian |
|
||||
And user "Alice" has uploaded file with content "ownCloud test text file" to "textfile.txt"
|
||||
And user "Alice" has uploaded file with content "OpenCloud test text file" to "textfile.txt"
|
||||
|
||||
|
||||
Scenario: check activities after adding share to a file
|
||||
@@ -1942,7 +1942,7 @@ Feature: check share activity
|
||||
|
||||
@issue-9860
|
||||
Scenario: sharee tries to check the activities of unshared file
|
||||
Given user "Alice" has uploaded file with content "another ownCloud test text file" to "anotherTextfile.txt"
|
||||
Given user "Alice" has uploaded file with content "another OpenCloud test text file" to "anotherTextfile.txt"
|
||||
And user "Alice" has sent the following resource share invitation:
|
||||
| resource | textfile.txt |
|
||||
| space | Personal |
|
||||
|
||||
@@ -1,4 +1,4 @@
|
||||
# NOTE: set env OC_CORS_ALLOW_ORIGINS=https://aphno.badal while running ocis server
|
||||
# NOTE: set env OC_CORS_ALLOW_ORIGINS=https://aphno.badal while running OpenCloud server
|
||||
@env-config
|
||||
Feature: CORS headers
|
||||
As a user
|
||||
|
||||
@@ -275,7 +275,7 @@ Feature: enforce password on public link
|
||||
| password | http-status-code | ocs-status-code | message |
|
||||
| 123 | 400 | 400 | Unfortunately, your password is commonly used. please pick a harder-to-guess password for your safety |
|
||||
| password | 400 | 400 | Unfortunately, your password is commonly used. please pick a harder-to-guess password for your safety |
|
||||
| ownCloud | 400 | 400 | Unfortunately, your password is commonly used. please pick a harder-to-guess password for your safety |
|
||||
| OpenCloud | 400 | 400 | Unfortunately, your password is commonly used. please pick a harder-to-guess password for your safety |
|
||||
|
||||
|
||||
Scenario Outline: create a public link with a password that is listed in the Banned-Password-List
|
||||
@@ -294,4 +294,4 @@ Feature: enforce password on public link
|
||||
| password | http-status-code | ocs-status-code | message |
|
||||
| 123 | 400 | 400 | Unfortunately, your password is commonly used. please pick a harder-to-guess password for your safety |
|
||||
| password | 400 | 400 | Unfortunately, your password is commonly used. please pick a harder-to-guess password for your safety |
|
||||
| ownCloud | 400 | 400 | Unfortunately, your password is commonly used. please pick a harder-to-guess password for your safety |
|
||||
| OpenCloud | 400 | 400 | Unfortunately, your password is commonly used. please pick a harder-to-guess password for your safety |
|
||||
|
||||
@@ -6,15 +6,14 @@ Feature: get applications
|
||||
Background:
|
||||
Given user "Alice" has been created with default attributes
|
||||
|
||||
|
||||
Scenario Outline: admin user lists all the groups
|
||||
Given the administrator has assigned the role "<user-role>" to user "Alice" using the Graph API
|
||||
When user "Alice" gets all applications using the Graph API
|
||||
Then the HTTP status code should be "200"
|
||||
And the user API response should contain the following application information:
|
||||
| key | value |
|
||||
| displayName | ownCloud Infinite Scale |
|
||||
| id | %uuid_v4% |
|
||||
| key | value |
|
||||
| displayName | OpenCloud |
|
||||
| id | %uuid_v4% |
|
||||
And the user API response should contain the following app roles:
|
||||
| Admin |
|
||||
| Space Admin |
|
||||
|
||||
@@ -92,7 +92,7 @@ Feature: create user
|
||||
And user "Brian" should exist
|
||||
|
||||
@env-config
|
||||
Scenario Outline: create user with setting OCIS no restriction on the user name
|
||||
Scenario Outline: create user with setting OpenCloud no restriction on the user name
|
||||
Given the config "GRAPH_USERNAME_MATCH" has been set to "none"
|
||||
And the administrator has assigned the role "Admin" to user "Alice" using the Graph API
|
||||
When the user "Alice" creates a new user with the following attributes using the Graph API:
|
||||
@@ -109,7 +109,7 @@ Feature: create user
|
||||
| (*:!;+-&$%)_alice | user names starts with the ASCII characters |
|
||||
|
||||
@env-config
|
||||
Scenario: create user with setting OCIS not to assign the default user role
|
||||
Scenario: create user with setting OpenCloud not to assign the default user role
|
||||
Given the config "GRAPH_ASSIGN_DEFAULT_USER_ROLE" has been set to "false"
|
||||
When the user "admin" creates a new user with the following attributes using the Graph API:
|
||||
| userName | sam |
|
||||
@@ -124,7 +124,7 @@ Feature: create user
|
||||
And the Graph API response should have no role
|
||||
|
||||
@env-config
|
||||
Scenario: create user with setting OCIS assign the default user role
|
||||
Scenario: create user with setting OpenCloud assign the default user role
|
||||
Given the config "GRAPH_ASSIGN_DEFAULT_USER_ROLE" has been set to "true"
|
||||
When the user "admin" creates a new user with the following attributes using the Graph API:
|
||||
| userName | sam |
|
||||
|
||||
@@ -1,7 +1,7 @@
|
||||
@ocm
|
||||
Feature: accepting invitation
|
||||
As a user
|
||||
I can accept invitations from users of other ocis instances
|
||||
I can accept invitations from users of other OpenCloud instances
|
||||
|
||||
Background:
|
||||
Given user "Alice" has been created with default attributes
|
||||
|
||||
@@ -32,7 +32,7 @@ Feature: ocm well-known URI
|
||||
"pattern": "^%base_url%/ocm"
|
||||
},
|
||||
"provider": {
|
||||
"const": "oCIS"
|
||||
"const": "OpenCloud"
|
||||
},
|
||||
"resourceTypes": {
|
||||
"type": "array",
|
||||
|
||||
@@ -1,7 +1,7 @@
|
||||
@ocm
|
||||
Feature: an user shares resources using ScienceMesh application
|
||||
As a user
|
||||
I want to share resources between different ocis instances
|
||||
I want to share resources between different OpenCloud instances
|
||||
|
||||
Background:
|
||||
Given user "Alice" has been created with default attributes
|
||||
|
||||
@@ -1,7 +1,7 @@
|
||||
Feature: re-share resources
|
||||
As a user
|
||||
I cannot to re-share resources
|
||||
This feature has been removed from ocis
|
||||
This feature has been removed from OpenCloud
|
||||
|
||||
Background:
|
||||
Given these users have been created with default attributes:
|
||||
|
||||
@@ -30,13 +30,13 @@ Feature: content search
|
||||
Scenario Outline: search files by different content types
|
||||
Given using <dav-path-version> DAV path
|
||||
And user "Alice" has uploaded file with content "Using k6, you can test the reliability and performance of your systems" to "wordWithNumber.md"
|
||||
And user "Alice" has uploaded file with content "see our web site https://owncloud.com/infinite-scale-4-0" to "findByWebSite.txt"
|
||||
And user "Alice" has uploaded file with content "see our web site https://opencloud.eu/en/contact-us" to "findByWebSite.txt"
|
||||
And user "Alice" has uploaded file with content "einstein@example.org want to say hello" to "findByEmail.docs"
|
||||
When user "Alice" searches for "Content:k6" using the WebDAV API
|
||||
Then the HTTP status code should be "207"
|
||||
And the search result of user "Alice" should contain only these files:
|
||||
| wordWithNumber.md |
|
||||
When user "Alice" searches for "Content:https://owncloud.com/" using the WebDAV API
|
||||
When user "Alice" searches for "Content:https://opencloud.eu/" using the WebDAV API
|
||||
Then the HTTP status code should be "207"
|
||||
And the search result of user "Alice" should contain only these files:
|
||||
| findByWebSite.txt |
|
||||
|
||||
@@ -28,7 +28,7 @@ Feature: settings api
|
||||
"type": "object",
|
||||
"required": [ "extension", "bundle", "setting"],
|
||||
"properties": {
|
||||
"extension": { "const": "ocis-accounts" },
|
||||
"extension": { "const": "opencloud-accounts" },
|
||||
"bundle": { "const": "profile" },
|
||||
"setting": { "const": "auto-accept-shares" }
|
||||
}
|
||||
@@ -128,7 +128,7 @@ Feature: settings api
|
||||
"type": "object",
|
||||
"required": [ "extension", "bundle", "setting"],
|
||||
"properties": {
|
||||
"extension": { "const": "ocis-accounts" },
|
||||
"extension": { "const": "opencloud-accounts" },
|
||||
"bundle": { "const": "profile" },
|
||||
"setting": { "const": "language" }
|
||||
}
|
||||
@@ -199,7 +199,7 @@ Feature: settings api
|
||||
"id": { "pattern": "^%user_id_pattern%$" },
|
||||
"name": { "const": "spaceadmin" },
|
||||
"type": { "const": "TYPE_ROLE" },
|
||||
"extension": { "const": "ocis-roles" },
|
||||
"extension": { "const": "opencloud-roles" },
|
||||
"displayName": { "const": "Space Admin" },
|
||||
"resource": {
|
||||
"type": "object",
|
||||
@@ -217,7 +217,7 @@ Feature: settings api
|
||||
"id": { "pattern": "^%user_id_pattern%$" },
|
||||
"name": { "const": "admin"},
|
||||
"type": { "const": "TYPE_ROLE" },
|
||||
"extension": { "const": "ocis-roles" },
|
||||
"extension": { "const": "opencloud-roles" },
|
||||
"displayName": { "const": "Admin" },
|
||||
"resource": {
|
||||
"type": "object",
|
||||
@@ -235,7 +235,7 @@ Feature: settings api
|
||||
"id": { "pattern": "^%user_id_pattern%$" },
|
||||
"name": { "const": "user-light" },
|
||||
"type": { "const": "TYPE_ROLE" },
|
||||
"extension": { "const": "ocis-roles" },
|
||||
"extension": { "const": "opencloud-roles" },
|
||||
"displayName": { "const": "User Light" },
|
||||
"resource": {
|
||||
"type": "object",
|
||||
@@ -253,7 +253,7 @@ Feature: settings api
|
||||
"id": { "pattern": "^%user_id_pattern%$" },
|
||||
"name": { "const": "user" },
|
||||
"type": { "const": "TYPE_ROLE" },
|
||||
"extension": { "const": "ocis-roles" },
|
||||
"extension": { "const": "opencloud-roles" },
|
||||
"displayName": { "const": "User" },
|
||||
"resource": {
|
||||
"type": "object",
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
Feature: List a sharing permissions
|
||||
https://owncloud.dev/libre-graph-api/#/drives.permissions/ListPermissions
|
||||
https://docs.opencloud.eu/libre-graph-api/#/drives.permissions/ListPermissions
|
||||
|
||||
Background:
|
||||
Given these users have been created with default attributes:
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
Feature: Remove access to a drive
|
||||
https://owncloud.dev/libre-graph-api/#/drives.root/DeletePermissionSpaceRoot
|
||||
https://docs.opencloud.eu/libre-graph-api/#/drives.root/DeletePermissionSpaceRoot
|
||||
|
||||
Background:
|
||||
Given these users have been created with default attributes:
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
Feature: Remove access to a drive item
|
||||
https://owncloud.dev/libre-graph-api/#/drives.permissions/DeletePermission
|
||||
https://docs.opencloud.eu/libre-graph-api/#/drives.permissions/DeletePermission
|
||||
|
||||
Background:
|
||||
Given these users have been created with default attributes:
|
||||
|
||||
@@ -3,7 +3,7 @@ Feature: resources shared by user
|
||||
I want to get resources shared by me
|
||||
So that I can know about what resources are shared with others
|
||||
|
||||
https://owncloud.dev/libre-graph-api/#/me.drive/ListSharedByMe
|
||||
https://docs.opencloud.eu/libre-graph-api/#/me.drive/ListSharedByMe
|
||||
|
||||
Background:
|
||||
Given these users have been created with default attributes:
|
||||
|
||||
@@ -3,7 +3,7 @@ Feature: an user gets the resources shared to them
|
||||
I want to get resources shared with me
|
||||
So that I can know about what resources I have access to
|
||||
|
||||
https://owncloud.dev/libre-graph-api/#/me.drive/ListSharedWithMe
|
||||
https://docs.opencloud.eu/libre-graph-api/#/me.drive/ListSharedWithMe
|
||||
|
||||
Background:
|
||||
Given these users have been created with default attributes:
|
||||
|
||||
@@ -3,7 +3,7 @@ Feature: listing sharedWithMe when auto-sync is disabled
|
||||
I want to get resources shared with me when auto-sync is disabled
|
||||
So that I can know about what resources I have access to
|
||||
|
||||
https://owncloud.dev/libre-graph-api/#/me.drive/ListSharedWithMe
|
||||
https://docs.opencloud.eu/libre-graph-api/#/me.drive/ListSharedWithMe
|
||||
|
||||
Background:
|
||||
Given these users have been created with default attributes:
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
Feature: Remove access to a drive item
|
||||
https://owncloud.dev/libre-graph-api/#/drives.permissions/DeletePermission
|
||||
https://docs.opencloud.eu/libre-graph-api/#/drives.permissions/DeletePermission
|
||||
|
||||
Background:
|
||||
Given these users have been created with default attributes:
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
Feature: Create a link share for a resource
|
||||
https://owncloud.dev/libre-graph-api/#/drives.permissions/CreateLink
|
||||
https://docs.opencloud.eu/libre-graph-api/#/drives.permissions/CreateLink
|
||||
|
||||
Background:
|
||||
Given these users have been created with default attributes:
|
||||
@@ -546,7 +546,7 @@ Feature: Create a link share for a resource
|
||||
| banned-password |
|
||||
| 123 |
|
||||
| password |
|
||||
| ownCloud |
|
||||
| OpenCloud |
|
||||
|
||||
@issue-7879
|
||||
Scenario Outline: create a link share of a folder inside project-space using permissions endpoint
|
||||
@@ -806,19 +806,19 @@ Feature: Create a link share for a resource
|
||||
| banned-password | permissions-role |
|
||||
| 123 | view |
|
||||
| password | view |
|
||||
| ownCloud | view |
|
||||
| OpenCloud | view |
|
||||
| 123 | edit |
|
||||
| password | edit |
|
||||
| ownCloud | edit |
|
||||
| OpenCloud | edit |
|
||||
| 123 | upload |
|
||||
| password | upload |
|
||||
| ownCloud | upload |
|
||||
| OpenCloud | upload |
|
||||
| 123 | createOnly |
|
||||
| password | createOnly |
|
||||
| ownCloud | createOnly |
|
||||
| OpenCloud | createOnly |
|
||||
| 123 | blocksDownload |
|
||||
| password | blocksDownload |
|
||||
| ownCloud | blocksDownload |
|
||||
| OpenCloud | blocksDownload |
|
||||
|
||||
@env-config @issue-7879
|
||||
Scenario Outline: create a link share of a file inside project-space without password using permissions endpoint
|
||||
@@ -1213,13 +1213,13 @@ Feature: Create a link share for a resource
|
||||
| banned-password | permissions-role |
|
||||
| 123 | view |
|
||||
| password | view |
|
||||
| ownCloud | view |
|
||||
| OpenCloud | view |
|
||||
| 123 | edit |
|
||||
| password | edit |
|
||||
| ownCloud | edit |
|
||||
| OpenCloud | edit |
|
||||
| 123 | blocksDownload |
|
||||
| password | blocksDownload |
|
||||
| ownCloud | blocksDownload |
|
||||
| OpenCloud | blocksDownload |
|
||||
|
||||
@env-config @issue-9724 @issue-10331
|
||||
Scenario: set password on a existing link share of a file inside project-space using permissions endpoint
|
||||
@@ -1673,19 +1673,19 @@ Feature: Create a link share for a resource
|
||||
| banned-password | permissions-role |
|
||||
| 123 | view |
|
||||
| password | view |
|
||||
| ownCloud | view |
|
||||
| OpenCloud | view |
|
||||
| 123 | edit |
|
||||
| password | edit |
|
||||
| ownCloud | edit |
|
||||
| OpenCloud | edit |
|
||||
| 123 | upload |
|
||||
| password | upload |
|
||||
| ownCloud | upload |
|
||||
| OpenCloud | upload |
|
||||
| 123 | createOnly |
|
||||
| password | createOnly |
|
||||
| ownCloud | createOnly |
|
||||
| OpenCloud | createOnly |
|
||||
| 123 | blocksDownload |
|
||||
| password | blocksDownload |
|
||||
| ownCloud | blocksDownload |
|
||||
| OpenCloud | blocksDownload |
|
||||
|
||||
|
||||
Scenario Outline: create a link share of a project-space without password using permissions endpoint
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
Feature: Update a link share for a resource
|
||||
https://owncloud.dev/libre-graph-api/#/drives.permissions/CreateLink
|
||||
https://docs.opencloud.eu/libre-graph-api/#/drives.permissions/CreateLink
|
||||
|
||||
Background:
|
||||
Given these users have been created with default attributes:
|
||||
@@ -281,7 +281,7 @@ Feature: Update a link share for a resource
|
||||
| banned-password |
|
||||
| 123 |
|
||||
| password |
|
||||
| ownCloud |
|
||||
| OpenCloud |
|
||||
|
||||
@env-config @issue-9724 @issue-10331
|
||||
Scenario: set password on a existing link share of a folder inside project-space using permissions endpoint
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
Feature: Create a link share for a resource
|
||||
https://owncloud.dev/libre-graph-api/#/drives.permissions/CreateLink
|
||||
https://docs.opencloud.eu/libre-graph-api/#/drives.permissions/CreateLink
|
||||
|
||||
Background:
|
||||
Given these users have been created with default attributes:
|
||||
@@ -393,19 +393,19 @@ Feature: Create a link share for a resource
|
||||
| banned-password | permissions-role |
|
||||
| 123 | view |
|
||||
| password | view |
|
||||
| ownCloud | view |
|
||||
| OpenCloud | view |
|
||||
| 123 | edit |
|
||||
| password | edit |
|
||||
| ownCloud | edit |
|
||||
| OpenCloud | edit |
|
||||
| 123 | upload |
|
||||
| password | upload |
|
||||
| ownCloud | upload |
|
||||
| OpenCloud | upload |
|
||||
| 123 | createOnly |
|
||||
| password | createOnly |
|
||||
| ownCloud | createOnly |
|
||||
| OpenCloud | createOnly |
|
||||
| 123 | blocksDownload |
|
||||
| password | blocksDownload |
|
||||
| ownCloud | blocksDownload |
|
||||
| OpenCloud | blocksDownload |
|
||||
|
||||
@env-config @issue-7879
|
||||
Scenario Outline: create a link share of a project-space drive without password using root endpoint
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
Feature: Update a link share for a resource
|
||||
https://owncloud.dev/libre-graph-api/#/drives.permissions/CreateLink
|
||||
https://docs.opencloud.eu/libre-graph-api/#/drives.permissions/CreateLink
|
||||
|
||||
Background:
|
||||
Given these users have been created with default attributes:
|
||||
|
||||
@@ -4,7 +4,7 @@ Feature: Send a sharing invitations
|
||||
I want to be able to send invitations to other users
|
||||
So that they can have access to it
|
||||
|
||||
https://owncloud.dev/libre-graph-api/#/drives.permissions/Invite
|
||||
https://docs.opencloud.eu/libre-graph-api/#/drives.permissions/Invite
|
||||
|
||||
Background:
|
||||
Given these users have been created with default attributes:
|
||||
|
||||
+1
-1
@@ -2,7 +2,7 @@ Feature: Update permission of a share
|
||||
As a user
|
||||
I want to update resources shared with me
|
||||
So that I can have more control over my shares and manage it
|
||||
https://owncloud.dev/libre-graph-api/#/drives.permissions/UpdatePermission
|
||||
https://docs.opencloud.eu/libre-graph-api/#/drives.permissions/UpdatePermission
|
||||
|
||||
Background:
|
||||
Given these users have been created with default attributes:
|
||||
|
||||
@@ -124,14 +124,14 @@ Feature: State of the quota
|
||||
| /filesForUpload/lorem-big.txt | /ocs/v2.php/cloud/users/%username% | 200 | 91.17 |
|
||||
|
||||
@env-config
|
||||
Scenario: upload a file by setting OCIS spaces max quota
|
||||
Scenario: upload a file by setting OpenCloud spaces max quota
|
||||
Given the config "OC_SPACES_MAX_QUOTA" has been set to "10"
|
||||
And user "Brian" has been created with default attributes
|
||||
When user "Brian" uploads file with content "more than 10 bytes content" to "lorem.txt" using the WebDAV API
|
||||
Then the HTTP status code should be "507"
|
||||
|
||||
@env-config
|
||||
Scenario: try to create a space with quota greater than OCIS spaces max quota
|
||||
Scenario: try to create a space with quota greater than OpenCloud spaces max quota
|
||||
Given the config "OC_SPACES_MAX_QUOTA" has been set to "50"
|
||||
And user "Brian" has been created with default attributes
|
||||
And the administrator has assigned the role "Space Admin" to user "Brian" using the Graph API
|
||||
|
||||
@@ -673,7 +673,7 @@ Feature: copy file
|
||||
| shareType | user |
|
||||
| permissionsRole | Viewer |
|
||||
And user "Alice" has a share "testshare" synced
|
||||
And user "Alice" has uploaded file with content "ownCloud test text file 0" to "/textfile0.txt"
|
||||
And user "Alice" has uploaded file with content "OpenCloud test text file 0" to "/textfile0.txt"
|
||||
When user "Alice" copies file "/textfile0.txt" from space "Personal" to "/testshare/textfile0.txt" inside space "Shares" using the WebDAV API
|
||||
Then the HTTP status code should be "403"
|
||||
And user "Alice" should not be able to download file "/testshare/textfile0.txt" from space "Shares"
|
||||
@@ -682,8 +682,8 @@ Feature: copy file
|
||||
Scenario: copying a file to overwrite a file into a folder with no permissions
|
||||
Given using spaces DAV path
|
||||
And user "Brian" has created folder "/testshare"
|
||||
And user "Brian" has uploaded file with content "ownCloud test text file 1" to "/testshare/overwritethis.txt"
|
||||
And user "Alice" has uploaded file with content "ownCloud test text file 0" to "/textfile0.txt"
|
||||
And user "Brian" has uploaded file with content "OpenCloud test text file 1" to "/testshare/overwritethis.txt"
|
||||
And user "Alice" has uploaded file with content "OpenCloud test text file 0" to "/textfile0.txt"
|
||||
And user "Brian" has sent the following resource share invitation:
|
||||
| resource | testshare |
|
||||
| space | Personal |
|
||||
@@ -693,12 +693,12 @@ Feature: copy file
|
||||
And user "Alice" has a share "testshare" synced
|
||||
When user "Alice" copies file "/textfile0.txt" from space "Personal" to "/testshare/overwritethis.txt" inside space "Shares" using the WebDAV API
|
||||
Then the HTTP status code should be "403"
|
||||
And for user "Alice" the content of the file "/testshare/overwritethis.txt" of the space "Shares" should be "ownCloud test text file 1"
|
||||
And for user "Alice" the content of the file "/testshare/overwritethis.txt" of the space "Shares" should be "OpenCloud test text file 1"
|
||||
|
||||
@issue-7208
|
||||
Scenario: copy a file over the top of an existing folder received as a user share
|
||||
Given using spaces DAV path
|
||||
And user "Alice" has uploaded file with content "ownCloud test text file 1" to "/textfile1.txt"
|
||||
And user "Alice" has uploaded file with content "OpenCloud test text file 1" to "/textfile1.txt"
|
||||
And user "Brian" has created folder "/BRIAN-Folder"
|
||||
And user "Brian" has created folder "BRIAN-Folder/sample-folder"
|
||||
And user "Brian" has sent the following resource share invitation:
|
||||
|
||||
@@ -20,7 +20,7 @@ Feature: make webdav request with special urls
|
||||
| /dav//files/%username%/PARENT/parent.txt |
|
||||
| /webdav//PARENT |
|
||||
| //dav/files/%username%//FOLDER |
|
||||
Then the HTTP status code of responses on each endpoint should be "200,200,204,204,200" on oCIS or "204,204,204,204,204" on reva
|
||||
Then the HTTP status code of responses on each endpoint should be "200,200,204,204,200" on OpenCloud or "204,204,204,204,204" on reva
|
||||
|
||||
|
||||
Scenario: send DELETE requests to webDav endpoints with 2 slashes using the spaces WebDAV API
|
||||
@@ -30,7 +30,7 @@ Feature: make webdav request with special urls
|
||||
| //dav//spaces/%spaceid%/PARENT/parent.txt |
|
||||
| /dav//spaces/%spaceid%/PARENT |
|
||||
| //dav/spaces/%spaceid%//FOLDER |
|
||||
Then the HTTP status code of responses on each endpoint should be "200,200,204,200" on oCIS or "204,204,204,204" on reva
|
||||
Then the HTTP status code of responses on each endpoint should be "200,200,204,200" on OpenCloud or "204,204,204,204" on reva
|
||||
|
||||
|
||||
Scenario: send GET requests to webDav endpoints with 2 slashes
|
||||
@@ -84,7 +84,7 @@ Feature: make webdav request with special urls
|
||||
| //dav//files/%username%/PARENT4 |
|
||||
| /dav/files/%username%//PARENT5 |
|
||||
| /dav//files/%username%/PARENT6 |
|
||||
Then the HTTP status code of responses on each endpoint should be "200,201,200,200,201,201" on oCIS or "201,201,201,201,201,201" on reva
|
||||
Then the HTTP status code of responses on each endpoint should be "200,201,200,200,201,201" on OpenCloud or "201,201,201,201,201,201" on reva
|
||||
|
||||
|
||||
Scenario: send MKCOL requests to webDav endpoints with 2 slashes using the spaces WebDAV API
|
||||
@@ -96,7 +96,7 @@ Feature: make webdav request with special urls
|
||||
| //dav/spaces//%spaceid%/PARENT4 |
|
||||
| /dav/spaces/%spaceid%//PARENT5 |
|
||||
| /dav//spaces/%spaceid%/PARENT6 |
|
||||
Then the HTTP status code of responses on each endpoint should be "200,201,200,200,201,201" on oCIS or "201,201,201,201,201,201" on reva
|
||||
Then the HTTP status code of responses on each endpoint should be "200,201,200,200,201,201" on OpenCloud or "201,201,201,201,201,201" on reva
|
||||
|
||||
|
||||
Scenario: send MOVE requests to webDav endpoints with 2 slashes
|
||||
@@ -107,7 +107,7 @@ Feature: make webdav request with special urls
|
||||
| /webdav//PARENT | /webdav/PARENT1 |
|
||||
| //dav/files//%username%//PARENT1 | /dav/files/%username%/PARENT2 |
|
||||
| /dav//files/%username%/PARENT2/parent.txt | /dav/files/%username%/PARENT2/parent1.txt |
|
||||
Then the HTTP status code of responses on each endpoint should be "200,201,201,200,404" on oCIS or "201,201,201,201,201" on reva
|
||||
Then the HTTP status code of responses on each endpoint should be "200,201,201,200,404" on OpenCloud or "201,201,201,201,201" on reva
|
||||
|
||||
|
||||
Scenario: send MOVE requests to webDav endpoints with 2 slashes using the spaces WebDAV API
|
||||
@@ -117,7 +117,7 @@ Feature: make webdav request with special urls
|
||||
| /dav/spaces/%spaceid%//PARENT | /dav/spaces/%spaceid%/PARENT1 |
|
||||
| //dav/spaces/%spaceid%//PARENT1 | /dav/spaces/%spaceid%/PARENT2 |
|
||||
| //dav/spaces/%spaceid%/PARENT2/parent.txt | /dav/spaces/%spaceid%/PARENT2/parent1.txt |
|
||||
Then the HTTP status code of responses on each endpoint should be "201,201,200,200" on oCIS or "201,201,201,201" on reva
|
||||
Then the HTTP status code of responses on each endpoint should be "201,201,200,200" on OpenCloud or "201,201,201,201" on reva
|
||||
|
||||
|
||||
Scenario: send POST requests to webDav endpoints with 2 slashes
|
||||
@@ -149,7 +149,7 @@ Feature: make webdav request with special urls
|
||||
| /dav//files/%username%/PARENT/parent.txt |
|
||||
| /webdav//PARENT |
|
||||
| //dav/files//%username%//FOLDER |
|
||||
Then the HTTP status code of responses on each endpoint should be "200,200,207,207,200" on oCIS or "207,207,207,207,207" on reva
|
||||
Then the HTTP status code of responses on each endpoint should be "200,200,207,207,200" on OpenCloud or "207,207,207,207,207" on reva
|
||||
|
||||
|
||||
Scenario: send PROPFIND requests to webDav endpoints with 2 slashes using the spaces WebDAV API
|
||||
@@ -159,7 +159,7 @@ Feature: make webdav request with special urls
|
||||
| /dav//spaces/%spaceid%/PARENT/parent.txt |
|
||||
| /dav//spaces/%spaceid%/PARENT |
|
||||
| //dav/spaces//%spaceid%//FOLDER |
|
||||
Then the HTTP status code of responses on each endpoint should be "200,207,207,200" on oCIS or "207,207,207,207" on reva
|
||||
Then the HTTP status code of responses on each endpoint should be "200,207,207,200" on OpenCloud or "207,207,207,207" on reva
|
||||
|
||||
|
||||
Scenario: send PROPPATCH requests to webDav endpoints with 2 slashes
|
||||
@@ -191,7 +191,7 @@ Feature: make webdav request with special urls
|
||||
| //dav//files/%username%/textfile1.txt |
|
||||
| /dav/files//%username%/textfile7.txt |
|
||||
| //dav//files/%username%/PARENT//parent.txt |
|
||||
Then the HTTP status code of responses on each endpoint should be "200,204,200,201,200" on oCIS or "204,204,204,201,204" on reva
|
||||
Then the HTTP status code of responses on each endpoint should be "200,204,200,201,200" on OpenCloud or "204,204,204,201,204" on reva
|
||||
|
||||
|
||||
Scenario: send PUT requests to webDav endpoints with 2 slashes using the spaces WebDAV API
|
||||
@@ -202,4 +202,4 @@ Feature: make webdav request with special urls
|
||||
| //dav//spaces/%spaceid%/textfile1.txt |
|
||||
| /dav/spaces//%spaceid%/textfile7.txt |
|
||||
| //dav/spaces//%spaceid%/PARENT//parent.txt |
|
||||
Then the HTTP status code of responses on each endpoint should be "200,204,200,201,200" on oCIS or "204,204,204,201,204" on reva
|
||||
Then the HTTP status code of responses on each endpoint should be "200,204,200,201,200" on OpenCloud or "204,204,204,201,204" on reva
|
||||
|
||||
@@ -8,7 +8,7 @@ Feature: default capabilities for normal user
|
||||
And user "Alice" has been created with default attributes
|
||||
|
||||
# adjust this scenario after fixing tagged issues as its just created to show difference
|
||||
# in the response items in different environment (core & ocis-reva)
|
||||
# in the response items in different environment (core & opencloud-reva)
|
||||
@issue-1285 @issue-1286
|
||||
Scenario: getting default capabilities with normal user
|
||||
When user "Alice" retrieves the capabilities using the capabilities API
|
||||
|
||||
@@ -276,11 +276,11 @@ Feature: checksums
|
||||
@skipOnStorage:ceph @skipOnStorage:scality @issue-1291
|
||||
Scenario Outline: uploading a file with invalid SHA1 checksum overwriting an existing file
|
||||
Given using <dav-path-version> DAV path
|
||||
And user "Alice" has uploaded file with content "ownCloud test text file 0" to "/textfile0.txt"
|
||||
And user "Alice" has uploaded file with content "OpenCloud test text file 0" to "/textfile0.txt"
|
||||
When user "Alice" uploads file "filesForUpload/textfile.txt" to "/textfile0.txt" with checksum "SHA1:f005ba11f005ba11f005ba11f005ba11f005ba11" using the WebDAV API
|
||||
Then the HTTP status code should be "400"
|
||||
And as user "Alice" the webdav checksum of "/textfile0.txt" via propfind should match "SHA1:2052377dec0724bda0d57aeab67fa819278b7f74 MD5:096e350e9ff1339a997a14145f9fc4b9 ADLER32:7d5a0921"
|
||||
And the content of file "/textfile0.txt" for user "Alice" should be "ownCloud test text file 0"
|
||||
And the content of file "/textfile0.txt" for user "Alice" should be "OpenCloud test text file 0"
|
||||
Examples:
|
||||
| dav-path-version |
|
||||
| old |
|
||||
|
||||
+17
-17
@@ -11,7 +11,7 @@ Feature: sharing
|
||||
Scenario Outline: creating a share of a file with a user, the default permissions are read(1)+update(2)
|
||||
Given using OCS API version "<ocs-api-version>"
|
||||
And user "Brian" has been created with default attributes
|
||||
And user "Alice" has uploaded file with content "ownCloud test text file 0" to "/textfile0.txt"
|
||||
And user "Alice" has uploaded file with content "OpenCloud test text file 0" to "/textfile0.txt"
|
||||
When user "Alice" shares file "textfile0.txt" with user "Brian" using the sharing API
|
||||
Then the OCS status code should be "<ocs-status-code>"
|
||||
And the HTTP status code should be "200"
|
||||
@@ -28,7 +28,7 @@ Feature: sharing
|
||||
| mimetype | text/plain |
|
||||
| storage_id | ANY_VALUE |
|
||||
| share_type | user |
|
||||
And the content of file "/Shares/textfile0.txt" for user "Brian" should be "ownCloud test text file 0"
|
||||
And the content of file "/Shares/textfile0.txt" for user "Brian" should be "OpenCloud test text file 0"
|
||||
Examples:
|
||||
| ocs-api-version | ocs-status-code |
|
||||
| 1 | 100 |
|
||||
@@ -64,7 +64,7 @@ Feature: sharing
|
||||
Scenario Outline: creating a share of a file with a user and asking for various permission combinations
|
||||
Given using OCS API version "<ocs-api-version>"
|
||||
And user "Brian" has been created with default attributes
|
||||
And user "Alice" has uploaded file with content "ownCloud test text file 0" to "/textfile0.txt"
|
||||
And user "Alice" has uploaded file with content "OpenCloud test text file 0" to "/textfile0.txt"
|
||||
When user "Alice" shares file "textfile0.txt" with user "Brian" with permissions <requested-permissions> using the sharing API
|
||||
Then the OCS status code should be "<ocs-status-code>"
|
||||
And the HTTP status code should be "200"
|
||||
@@ -156,7 +156,7 @@ Feature: sharing
|
||||
Scenario Outline: creating a share of a file with a group, the default permissions are read(1)+update(2)
|
||||
Given using OCS API version "<ocs-api-version>"
|
||||
And group "grp1" has been created
|
||||
And user "Alice" has uploaded file with content "ownCloud test text file 0" to "/textfile0.txt"
|
||||
And user "Alice" has uploaded file with content "OpenCloud test text file 0" to "/textfile0.txt"
|
||||
When user "Alice" shares file "/textfile0.txt" with group "grp1" using the sharing API
|
||||
Then the OCS status code should be "<ocs-status-code>"
|
||||
And the HTTP status code should be "200"
|
||||
@@ -255,7 +255,7 @@ Feature: sharing
|
||||
And group "grp1" has been created
|
||||
And user "Alice" has been added to group "grp1"
|
||||
And user "Brian" has been added to group "grp1"
|
||||
And user "Brian" has uploaded file with content "ownCloud test text file 0" to "/randomfile.txt"
|
||||
And user "Brian" has uploaded file with content "OpenCloud test text file 0" to "/randomfile.txt"
|
||||
And user "Brian" has sent the following resource share invitation:
|
||||
| resource | randomfile.txt |
|
||||
| space | Personal |
|
||||
@@ -322,7 +322,7 @@ Feature: sharing
|
||||
Scenario Outline: user shares a file with file name longer than 64 chars to another user
|
||||
Given using OCS API version "<ocs-api-version>"
|
||||
And user "Brian" has been created with default attributes
|
||||
And user "Alice" has uploaded file with content "ownCloud test text file 0" to "/textfile0.txt"
|
||||
And user "Alice" has uploaded file with content "OpenCloud test text file 0" to "/textfile0.txt"
|
||||
And user "Alice" has moved file "textfile0.txt" to "aquickbrownfoxjumpsoveraverylazydogaquickbrownfoxjumpsoveralazydog.txt"
|
||||
When user "Alice" shares file "aquickbrownfoxjumpsoveraverylazydogaquickbrownfoxjumpsoveralazydog.txt" with user "Brian" using the sharing API
|
||||
Then as "Brian" file "/Shares/aquickbrownfoxjumpsoveraverylazydogaquickbrownfoxjumpsoveralazydog.txt" should exist
|
||||
@@ -337,7 +337,7 @@ Feature: sharing
|
||||
And group "grp1" has been created
|
||||
And user "Brian" has been created with default attributes
|
||||
And user "Brian" has been added to group "grp1"
|
||||
And user "Alice" has uploaded file with content "ownCloud test text file 0" to "/textfile0.txt"
|
||||
And user "Alice" has uploaded file with content "OpenCloud test text file 0" to "/textfile0.txt"
|
||||
And user "Alice" has moved file "textfile0.txt" to "aquickbrownfoxjumpsoveraverylazydogaquickbrownfoxjumpsoveralazydog.txt"
|
||||
When user "Alice" shares file "aquickbrownfoxjumpsoveraverylazydogaquickbrownfoxjumpsoveralazydog.txt" with group "grp1" using the sharing API
|
||||
Then as "Brian" file "/Shares/aquickbrownfoxjumpsoveraverylazydogaquickbrownfoxjumpsoveralazydog.txt" should exist
|
||||
@@ -350,11 +350,11 @@ Feature: sharing
|
||||
Scenario Outline: user shares a folder with folder name longer than 64 chars to another user
|
||||
Given using OCS API version "<ocs-api-version>"
|
||||
And user "Brian" has been created with default attributes
|
||||
And user "Alice" has uploaded file with content "ownCloud test" to "/textfile0.txt"
|
||||
And user "Alice" has uploaded file with content "OpenCloud test" to "/textfile0.txt"
|
||||
And user "Alice" has created folder "/aquickbrownfoxjumpsoveraverylazydogaquickbrownfoxjumpsoveralazydog"
|
||||
And user "Alice" has moved file "textfile0.txt" to "aquickbrownfoxjumpsoveraverylazydogaquickbrownfoxjumpsoveralazydog/textfile0.txt"
|
||||
When user "Alice" shares folder "/aquickbrownfoxjumpsoveraverylazydogaquickbrownfoxjumpsoveralazydog" with user "Brian" using the sharing API
|
||||
Then the content of file "/Shares/aquickbrownfoxjumpsoveraverylazydogaquickbrownfoxjumpsoveralazydog/textfile0.txt" for user "Brian" should be "ownCloud test"
|
||||
Then the content of file "/Shares/aquickbrownfoxjumpsoveraverylazydogaquickbrownfoxjumpsoveralazydog/textfile0.txt" for user "Brian" should be "OpenCloud test"
|
||||
Examples:
|
||||
| ocs-api-version |
|
||||
| 1 |
|
||||
@@ -366,11 +366,11 @@ Feature: sharing
|
||||
And group "grp1" has been created
|
||||
And user "Brian" has been created with default attributes
|
||||
And user "Brian" has been added to group "grp1"
|
||||
And user "Alice" has uploaded file with content "ownCloud test" to "/textfile0.txt"
|
||||
And user "Alice" has uploaded file with content "OpenCloud test" to "/textfile0.txt"
|
||||
And user "Alice" has created folder "/aquickbrownfoxjumpsoveraverylazydogaquickbrownfoxjumpsoveralazydog"
|
||||
And user "Alice" has moved file "textfile0.txt" to "aquickbrownfoxjumpsoveraverylazydogaquickbrownfoxjumpsoveralazydog/textfile0.txt"
|
||||
When user "Alice" shares folder "/aquickbrownfoxjumpsoveraverylazydogaquickbrownfoxjumpsoveralazydog" with group "grp1" using the sharing API
|
||||
Then the content of file "/Shares/aquickbrownfoxjumpsoveraverylazydogaquickbrownfoxjumpsoveralazydog/textfile0.txt" for user "Brian" should be "ownCloud test"
|
||||
Then the content of file "/Shares/aquickbrownfoxjumpsoveraverylazydogaquickbrownfoxjumpsoveralazydog/textfile0.txt" for user "Brian" should be "OpenCloud test"
|
||||
Examples:
|
||||
| ocs-api-version |
|
||||
| 1 |
|
||||
@@ -474,7 +474,7 @@ Feature: sharing
|
||||
And group "grp1" has been created
|
||||
And user "Brian" has been added to group "grp1"
|
||||
And user "Carol" has been added to group "grp1"
|
||||
And user "Alice" has uploaded file with content "ownCloud test text file 0" to "/textfile0.txt"
|
||||
And user "Alice" has uploaded file with content "OpenCloud test text file 0" to "/textfile0.txt"
|
||||
And user "Alice" has sent the following resource share invitation:
|
||||
| resource | textfile0.txt |
|
||||
| space | Personal |
|
||||
@@ -516,7 +516,7 @@ Feature: sharing
|
||||
And user "Carol" has been added to group "grp1"
|
||||
And user "Alice" has created folder "/common"
|
||||
And user "Alice" has created folder "/common/sub"
|
||||
And user "Alice" has uploaded file with content "ownCloud" to "/textfile0.txt"
|
||||
And user "Alice" has uploaded file with content "OpenCloud" to "/textfile0.txt"
|
||||
And user "Alice" has sent the following resource share invitation:
|
||||
| resource | common |
|
||||
| space | Personal |
|
||||
@@ -552,7 +552,7 @@ Feature: sharing
|
||||
Scenario Outline: creating a share of a renamed file
|
||||
Given using OCS API version "<ocs-api-version>"
|
||||
And user "Brian" has been created with default attributes
|
||||
And user "Alice" has uploaded file with content "ownCloud test text file 0" to "/textfile0.txt"
|
||||
And user "Alice" has uploaded file with content "OpenCloud test text file 0" to "/textfile0.txt"
|
||||
And user "Alice" has moved file "/textfile0.txt" to "/renamed.txt"
|
||||
When user "Alice" shares file "renamed.txt" with user "Brian" using the sharing API
|
||||
Then the OCS status code should be "<ocs-status-code>"
|
||||
@@ -569,7 +569,7 @@ Feature: sharing
|
||||
| mimetype | text/plain |
|
||||
| storage_id | ANY_VALUE |
|
||||
| share_type | user |
|
||||
And the content of file "/Shares/renamed.txt" for user "Brian" should be "ownCloud test text file 0"
|
||||
And the content of file "/Shares/renamed.txt" for user "Brian" should be "OpenCloud test text file 0"
|
||||
Examples:
|
||||
| ocs-api-version | ocs-status-code |
|
||||
| 1 | 100 |
|
||||
@@ -582,7 +582,7 @@ Feature: sharing
|
||||
| username |
|
||||
| Brian |
|
||||
| Carol |
|
||||
And user "Alice" has uploaded file with content "ownCloud test text file 0" to "/textfile0.txt"
|
||||
And user "Alice" has uploaded file with content "OpenCloud test text file 0" to "/textfile0.txt"
|
||||
And user "Alice" has sent the following resource share invitation:
|
||||
| resource | textfile0.txt |
|
||||
| space | Personal |
|
||||
@@ -644,7 +644,7 @@ Feature: sharing
|
||||
Scenario Outline: sharing a same file twice to the same group is not possible
|
||||
Given using OCS API version "<ocs-api-version>"
|
||||
And group "grp1" has been created
|
||||
And user "Alice" has uploaded file with content "ownCloud test text file 0" to "/textfile0.txt"
|
||||
And user "Alice" has uploaded file with content "OpenCloud test text file 0" to "/textfile0.txt"
|
||||
And user "Alice" has sent the following resource share invitation:
|
||||
| resource | textfile0.txt |
|
||||
| space | Personal |
|
||||
|
||||
+8
-8
@@ -14,7 +14,7 @@ Feature: accept/decline shares coming from internal users to the Shares folder
|
||||
|
||||
|
||||
Scenario: accept an incoming file share
|
||||
Given user "Alice" has uploaded file with content "ownCloud test text file 0" to "textfile0.txt"
|
||||
Given user "Alice" has uploaded file with content "OpenCloud test text file 0" to "textfile0.txt"
|
||||
And user "Brian" has disabled auto-accepting
|
||||
And user "Alice" has sent the following resource share invitation:
|
||||
| resource | textfile0.txt |
|
||||
@@ -25,13 +25,13 @@ Feature: accept/decline shares coming from internal users to the Shares folder
|
||||
When user "Brian" accepts share "/textfile0.txt" offered by user "Alice" using the sharing API
|
||||
Then the OCS status code should be "100"
|
||||
And the HTTP status code should be "200"
|
||||
And the content of file "/Shares/textfile0.txt" for user "Brian" should be "ownCloud test text file 0"
|
||||
And the content of file "/Shares/textfile0.txt" for user "Brian" should be "OpenCloud test text file 0"
|
||||
|
||||
|
||||
Scenario: accept an incoming folder share
|
||||
Given user "Alice" has created folder "/PARENT"
|
||||
And user "Brian" has disabled auto-accepting
|
||||
And user "Alice" has uploaded file with content "ownCloud test text file parent" to "PARENT/parent.txt"
|
||||
And user "Alice" has uploaded file with content "OpenCloud test text file parent" to "PARENT/parent.txt"
|
||||
And user "Alice" has sent the following resource share invitation:
|
||||
| resource | PARENT |
|
||||
| space | Personal |
|
||||
@@ -39,11 +39,11 @@ Feature: accept/decline shares coming from internal users to the Shares folder
|
||||
| shareType | user |
|
||||
| permissionsRole | Viewer |
|
||||
When user "Brian" accepts share "/PARENT" offered by user "Alice" using the sharing API
|
||||
Then the content of file "/Shares/PARENT/parent.txt" for user "Brian" should be "ownCloud test text file parent"
|
||||
Then the content of file "/Shares/PARENT/parent.txt" for user "Brian" should be "OpenCloud test text file parent"
|
||||
|
||||
|
||||
Scenario: accept an incoming file share and check the response
|
||||
Given user "Alice" has uploaded file with content "ownCloud test text file 0" to "textfile0.txt"
|
||||
Given user "Alice" has uploaded file with content "OpenCloud test text file 0" to "textfile0.txt"
|
||||
And user "Brian" has disabled auto-accepting
|
||||
And user "Alice" has sent the following resource share invitation:
|
||||
| resource | textfile0.txt |
|
||||
@@ -66,13 +66,13 @@ Feature: accept/decline shares coming from internal users to the Shares folder
|
||||
| mimetype | text/plain |
|
||||
| storage_id | ANY_VALUE |
|
||||
| share_type | user |
|
||||
And the content of file "/Shares/textfile0.txt" for user "Brian" should be "ownCloud test text file 0"
|
||||
And the content of file "/Shares/textfile0.txt" for user "Brian" should be "OpenCloud test text file 0"
|
||||
|
||||
|
||||
Scenario: accept an incoming folder share and check the response
|
||||
Given user "Alice" has created folder "/PARENT"
|
||||
And user "Brian" has disabled auto-accepting
|
||||
And user "Alice" has uploaded file with content "ownCloud test text file parent" to "PARENT/parent.txt"
|
||||
And user "Alice" has uploaded file with content "OpenCloud test text file parent" to "PARENT/parent.txt"
|
||||
And user "Alice" has sent the following resource share invitation:
|
||||
| resource | PARENT |
|
||||
| space | Personal |
|
||||
@@ -94,4 +94,4 @@ Feature: accept/decline shares coming from internal users to the Shares folder
|
||||
| mimetype | httpd/unix-directory |
|
||||
| storage_id | ANY_VALUE |
|
||||
| share_type | user |
|
||||
And the content of file "/Shares/PARENT/parent.txt" for user "Brian" should be "ownCloud test text file parent"
|
||||
And the content of file "/Shares/PARENT/parent.txt" for user "Brian" should be "OpenCloud test text file parent"
|
||||
|
||||
@@ -13,7 +13,7 @@ Feature: share access by ID
|
||||
|
||||
Scenario Outline: get a share with a valid share ID
|
||||
Given using OCS API version "<ocs-api-version>"
|
||||
And user "Alice" has uploaded file with content "ownCloud test text file 0" to "/textfile0.txt"
|
||||
And user "Alice" has uploaded file with content "OpenCloud test text file 0" to "/textfile0.txt"
|
||||
When user "Alice" shares file "textfile0.txt" with user "Brian" using the sharing API
|
||||
And user "Alice" gets share with id "%last_share_id%" using the sharing API
|
||||
Then the OCS status code should be "<ocs-status-code>"
|
||||
@@ -30,7 +30,7 @@ Feature: share access by ID
|
||||
| mimetype | text/plain |
|
||||
| storage_id | ANY_VALUE |
|
||||
| share_type | user |
|
||||
And the content of file "/Shares/textfile0.txt" for user "Brian" should be "ownCloud test text file 0"
|
||||
And the content of file "/Shares/textfile0.txt" for user "Brian" should be "OpenCloud test text file 0"
|
||||
Examples:
|
||||
| ocs-api-version | ocs-status-code |
|
||||
| 1 | 100 |
|
||||
@@ -57,7 +57,7 @@ Feature: share access by ID
|
||||
|
||||
Scenario Outline: accept a share using the share Id
|
||||
Given using OCS API version "<ocs-api-version>"
|
||||
And user "Alice" has uploaded file with content "ownCloud test text file 0" to "/textfile0.txt"
|
||||
And user "Alice" has uploaded file with content "OpenCloud test text file 0" to "/textfile0.txt"
|
||||
When user "Alice" shares file "textfile0.txt" with user "Brian" using the sharing API
|
||||
Then the OCS status code should be "<ocs-status-code>"
|
||||
And the HTTP status code should be "200"
|
||||
@@ -102,7 +102,7 @@ Feature: share access by ID
|
||||
|
||||
Scenario Outline: decline a share using the share Id
|
||||
Given using OCS API version "<ocs-api-version>"
|
||||
And user "Alice" has uploaded file with content "ownCloud test text file 0" to "/textfile0.txt"
|
||||
And user "Alice" has uploaded file with content "OpenCloud test text file 0" to "/textfile0.txt"
|
||||
And user "Alice" has sent the following resource share invitation:
|
||||
| resource | textfile0.txt |
|
||||
| space | Personal |
|
||||
|
||||
@@ -3,7 +3,7 @@
|
||||
Feature: create a public link share
|
||||
As a user
|
||||
I want to create public links
|
||||
So that I can share resources to people who aren't owncloud users
|
||||
So that I can share resources to people who aren't OpenCloud users
|
||||
|
||||
Background:
|
||||
Given user "Alice" has been created with default attributes
|
||||
@@ -230,7 +230,7 @@ Feature: create a public link share
|
||||
| 2 | 200 |
|
||||
|
||||
|
||||
Scenario Outline: Do not allow public sharing of the root on OCIS when the default permission is read and access using the public WebDAV API
|
||||
Scenario Outline: Do not allow public sharing of the root on OpenCloud when the default permission is read and access using the public WebDAV API
|
||||
Given using OCS API version "<ocs-api-version>"
|
||||
When user "Alice" creates a public link share using the sharing API with settings
|
||||
| path | / |
|
||||
|
||||
+1
-1
@@ -1,7 +1,7 @@
|
||||
Feature: create a public link share when share_folder is set to Shares
|
||||
As a user
|
||||
I want to create public links
|
||||
So that I can share resources to people who aren't owncloud users
|
||||
So that I can share resources to people who aren't OpenCloud users
|
||||
|
||||
Background:
|
||||
Given user "Alice" has been created with default attributes
|
||||
|
||||
@@ -2,7 +2,7 @@
|
||||
Feature: restore deleted files/folders
|
||||
As a user
|
||||
I would like to restore files/folders
|
||||
So that I can recover accidentally deleted files/folders in ownCloud
|
||||
So that I can recover accidentally deleted files/folders in OpenCloud
|
||||
|
||||
Background:
|
||||
Given user "Alice" has been created with default attributes
|
||||
|
||||
@@ -11,12 +11,12 @@ Feature: move (rename) file
|
||||
Scenario Outline: moving a file
|
||||
Given using <dav-path-version> DAV path
|
||||
And user "Alice" has created folder "FOLDER"
|
||||
And user "Alice" has uploaded file with content "ownCloud test text file 0" to "textfile0.txt"
|
||||
And user "Alice" has uploaded file with content "OpenCloud test text file 0" to "textfile0.txt"
|
||||
When user "Alice" moves file "/textfile0.txt" to "/FOLDER/textfile0.txt" using the WebDAV API
|
||||
Then the HTTP status code should be "201"
|
||||
And the following headers should match these regular expressions for user "Alice"
|
||||
| ETag | /^"[a-f0-9:\.]{1,32}"$/ |
|
||||
And the content of file "/FOLDER/textfile0.txt" for user "Alice" should be "ownCloud test text file 0"
|
||||
And the content of file "/FOLDER/textfile0.txt" for user "Alice" should be "OpenCloud test text file 0"
|
||||
Examples:
|
||||
| dav-path-version |
|
||||
| old |
|
||||
@@ -26,15 +26,15 @@ Feature: move (rename) file
|
||||
@smokeTest
|
||||
Scenario Outline: moving and overwriting a file
|
||||
Given using <dav-path-version> DAV path
|
||||
And user "Alice" has uploaded file with content "ownCloud test text file 0 v1" to "textfile0.txt"
|
||||
And user "Alice" has uploaded file with content "ownCloud test text file 0 v2" to "textfile0.txt"
|
||||
And user "Alice" has uploaded file with content "ownCloud test text file 1" to "textfile1.txt"
|
||||
And user "Alice" has uploaded file with content "OpenCloud test text file 0 v1" to "textfile0.txt"
|
||||
And user "Alice" has uploaded file with content "OpenCloud test text file 0 v2" to "textfile0.txt"
|
||||
And user "Alice" has uploaded file with content "OpenCloud test text file 1" to "textfile1.txt"
|
||||
When user "Alice" moves file "/textfile0.txt" to "/textfile1.txt" using the WebDAV API
|
||||
Then the HTTP status code should be "204"
|
||||
And the following headers should match these regular expressions for user "Alice"
|
||||
| ETag | /^"[a-f0-9:\.]{1,32}"$/ |
|
||||
And the content of file "/textfile1.txt" for user "Alice" should be "ownCloud test text file 0 v2"
|
||||
And the content of version index "1" of file "/textfile1.txt" for user "Alice" should be "ownCloud test text file 0 v1"
|
||||
And the content of file "/textfile1.txt" for user "Alice" should be "OpenCloud test text file 0 v2"
|
||||
And the content of version index "1" of file "/textfile1.txt" for user "Alice" should be "OpenCloud test text file 0 v1"
|
||||
And as "Alice" file "/textfile0.txt" should not exist
|
||||
Examples:
|
||||
| dav-path-version |
|
||||
@@ -45,11 +45,11 @@ Feature: move (rename) file
|
||||
|
||||
Scenario Outline: moving (renaming) a file to be only different case
|
||||
Given using <dav-path-version> DAV path
|
||||
And user "Alice" has uploaded file with content "ownCloud test text file 0" to "textfile0.txt"
|
||||
And user "Alice" has uploaded file with content "OpenCloud test text file 0" to "textfile0.txt"
|
||||
When user "Alice" moves file "/textfile0.txt" to "/TextFile0.txt" using the WebDAV API
|
||||
Then the HTTP status code should be "201"
|
||||
And as "Alice" file "/textfile0.txt" should not exist
|
||||
And the content of file "/TextFile0.txt" for user "Alice" should be "ownCloud test text file 0"
|
||||
And the content of file "/TextFile0.txt" for user "Alice" should be "OpenCloud test text file 0"
|
||||
Examples:
|
||||
| dav-path-version |
|
||||
| old |
|
||||
@@ -59,12 +59,12 @@ Feature: move (rename) file
|
||||
@smokeTest
|
||||
Scenario Outline: moving (renaming) a file to a file with only different case to an existing file
|
||||
Given using <dav-path-version> DAV path
|
||||
And user "Alice" has uploaded file with content "ownCloud test text file 0" to "textfile0.txt"
|
||||
And user "Alice" has uploaded file with content "ownCloud test text file 1" to "textfile1.txt"
|
||||
And user "Alice" has uploaded file with content "OpenCloud test text file 0" to "textfile0.txt"
|
||||
And user "Alice" has uploaded file with content "OpenCloud test text file 1" to "textfile1.txt"
|
||||
When user "Alice" moves file "/textfile1.txt" to "/TextFile0.txt" using the WebDAV API
|
||||
Then the HTTP status code should be "201"
|
||||
And the content of file "/textfile0.txt" for user "Alice" should be "ownCloud test text file 0"
|
||||
And the content of file "/TextFile0.txt" for user "Alice" should be "ownCloud test text file 1"
|
||||
And the content of file "/textfile0.txt" for user "Alice" should be "OpenCloud test text file 0"
|
||||
And the content of file "/TextFile0.txt" for user "Alice" should be "OpenCloud test text file 1"
|
||||
Examples:
|
||||
| dav-path-version |
|
||||
| old |
|
||||
@@ -75,12 +75,12 @@ Feature: move (rename) file
|
||||
Scenario Outline: moving (renaming) a file to a file in a folder with only different case to an existing file
|
||||
Given using <dav-path-version> DAV path
|
||||
And user "Alice" has created folder "PARENT"
|
||||
And user "Alice" has uploaded file with content "ownCloud test text file parent" to "PARENT/parent.txt"
|
||||
And user "Alice" has uploaded file with content "ownCloud test text file 1" to "textfile1.txt"
|
||||
And user "Alice" has uploaded file with content "OpenCloud test text file parent" to "PARENT/parent.txt"
|
||||
And user "Alice" has uploaded file with content "OpenCloud test text file 1" to "textfile1.txt"
|
||||
When user "Alice" moves file "/textfile1.txt" to "/PARENT/Parent.txt" using the WebDAV API
|
||||
Then the HTTP status code should be "201"
|
||||
And the content of file "/PARENT/parent.txt" for user "Alice" should be "ownCloud test text file parent"
|
||||
And the content of file "/PARENT/Parent.txt" for user "Alice" should be "ownCloud test text file 1"
|
||||
And the content of file "/PARENT/parent.txt" for user "Alice" should be "OpenCloud test text file parent"
|
||||
And the content of file "/PARENT/Parent.txt" for user "Alice" should be "OpenCloud test text file 1"
|
||||
Examples:
|
||||
| dav-path-version |
|
||||
| old |
|
||||
@@ -90,11 +90,11 @@ Feature: move (rename) file
|
||||
@issue-1976
|
||||
Scenario Outline: try to move a file into same folder with same name
|
||||
Given using <dav-path-version> DAV path
|
||||
And user "Alice" has uploaded file with content "ownCloud test text file" to "testfile.txt"
|
||||
And user "Alice" has uploaded file with content "OpenCloud test text file" to "testfile.txt"
|
||||
When user "Alice" moves file "testfile.txt" to "testfile.txt" using the WebDAV API
|
||||
Then the HTTP status code should be "403"
|
||||
And as "Alice" the file with original path "testfile.txt" should not exist in the trashbin
|
||||
And the content of file "testfile.txt" for user "Alice" should be "ownCloud test text file"
|
||||
And the content of file "testfile.txt" for user "Alice" should be "OpenCloud test text file"
|
||||
Examples:
|
||||
| dav-path-version |
|
||||
| old |
|
||||
@@ -178,10 +178,10 @@ Feature: move (rename) file
|
||||
@sqliteDB
|
||||
Scenario Outline: renaming to a file with special characters
|
||||
Given using <dav-path-version> DAV path
|
||||
And user "Alice" has uploaded file with content "ownCloud test text file 0" to "textfile0.txt"
|
||||
And user "Alice" has uploaded file with content "ownCloud test text file 1" to "textfile1.txt"
|
||||
And user "Alice" has uploaded file with content "ownCloud test text file 2" to "textfile2.txt"
|
||||
And user "Alice" has uploaded file with content "ownCloud test text file 3" to "textfile3.txt"
|
||||
And user "Alice" has uploaded file with content "OpenCloud test text file 0" to "textfile0.txt"
|
||||
And user "Alice" has uploaded file with content "OpenCloud test text file 1" to "textfile1.txt"
|
||||
And user "Alice" has uploaded file with content "OpenCloud test text file 2" to "textfile2.txt"
|
||||
And user "Alice" has uploaded file with content "OpenCloud test text file 3" to "textfile3.txt"
|
||||
When user "Alice" moves the following file using the WebDAV API
|
||||
| source | destination |
|
||||
| /textfile0.txt | *a@b#c$e%f&g* |
|
||||
@@ -189,10 +189,10 @@ Feature: move (rename) file
|
||||
| /textfile2.txt | file[2] |
|
||||
| /textfile3.txt | file [ 3 ] |
|
||||
Then the HTTP status code of responses on all endpoints should be "201"
|
||||
And the content of file "*a@b#c$e%f&g*" for user "Alice" should be "ownCloud test text file 0"
|
||||
And the content of file "1 2 3##.##" for user "Alice" should be "ownCloud test text file 1"
|
||||
And the content of file "file[2]" for user "Alice" should be "ownCloud test text file 2"
|
||||
And the content of file "file [ 3 ]" for user "Alice" should be "ownCloud test text file 3"
|
||||
And the content of file "*a@b#c$e%f&g*" for user "Alice" should be "OpenCloud test text file 0"
|
||||
And the content of file "1 2 3##.##" for user "Alice" should be "OpenCloud test text file 1"
|
||||
And the content of file "file[2]" for user "Alice" should be "OpenCloud test text file 2"
|
||||
And the content of file "file [ 3 ]" for user "Alice" should be "OpenCloud test text file 3"
|
||||
Examples:
|
||||
| dav-path-version |
|
||||
| old |
|
||||
@@ -203,10 +203,10 @@ Feature: move (rename) file
|
||||
#after fixing the issues merge this Scenario into the one above
|
||||
Scenario Outline: renaming to a file with question mark in its name
|
||||
Given using <dav-path-version> DAV path
|
||||
And user "Alice" has uploaded file with content "ownCloud test text file 0" to "textfile0.txt"
|
||||
And user "Alice" has uploaded file with content "OpenCloud test text file 0" to "textfile0.txt"
|
||||
When user "Alice" moves file "/textfile0.txt" to "/#oc ab?cd=ef#" using the WebDAV API
|
||||
Then the HTTP status code should be "201"
|
||||
And the content of file "/#oc ab?cd=ef#" for user "Alice" should be "ownCloud test text file 0"
|
||||
And the content of file "/#oc ab?cd=ef#" for user "Alice" should be "OpenCloud test text file 0"
|
||||
Examples:
|
||||
| dav-path-version |
|
||||
| old |
|
||||
@@ -325,12 +325,12 @@ Feature: move (rename) file
|
||||
Given using <dav-path-version> DAV path
|
||||
And user "Alice" has created folder "<source-folder>"
|
||||
And user "Alice" has created folder "<destination-folder>"
|
||||
And user "Alice" has uploaded file with content "ownCloud test text file 0" to "/<source-folder>/<source-file>"
|
||||
And user "Alice" has uploaded file with content "OpenCloud test text file 0" to "/<source-folder>/<source-file>"
|
||||
When user "Alice" moves file "/<source-folder>/<source-file>" to "/<destination-folder>/<destination-file>" using the WebDAV API
|
||||
Then the HTTP status code should be "201"
|
||||
And the following headers should match these regular expressions for user "Alice"
|
||||
| ETag | /^"[a-f0-9:\.]{1,32}"$/ |
|
||||
And the content of file "/<destination-folder>/<destination-file>" for user "Alice" should be "ownCloud test text file 0"
|
||||
And the content of file "/<destination-folder>/<destination-file>" for user "Alice" should be "OpenCloud test text file 0"
|
||||
Examples:
|
||||
| dav-path-version | source-folder | source-file | destination-folder | destination-file |
|
||||
| old | text | file.txt | 0 | file.txt |
|
||||
@@ -362,12 +362,12 @@ Feature: move (rename) file
|
||||
Scenario Outline: moving a file from a folder to the root
|
||||
Given using <dav-path-version> DAV path
|
||||
And user "Alice" has created folder "<source-folder>"
|
||||
And user "Alice" has uploaded file with content "ownCloud test text file 0" to "/<source-folder>/<source-file>"
|
||||
And user "Alice" has uploaded file with content "OpenCloud test text file 0" to "/<source-folder>/<source-file>"
|
||||
When user "Alice" moves file "/<source-folder>/<source-file>" to "/<destination-file>" using the WebDAV API
|
||||
Then the HTTP status code should be "201"
|
||||
And the following headers should match these regular expressions for user "Alice"
|
||||
| ETag | /^"[a-f0-9:\.]{1,32}"$/ |
|
||||
And the content of file "/<destination-file>" for user "Alice" should be "ownCloud test text file 0"
|
||||
And the content of file "/<destination-file>" for user "Alice" should be "OpenCloud test text file 0"
|
||||
Examples:
|
||||
| dav-path-version | source-folder | source-file | destination-file |
|
||||
| old | 0 | file.txt | file.txt |
|
||||
@@ -492,7 +492,7 @@ Feature: move (rename) file
|
||||
|
||||
Scenario Outline: rename a file to .htaccess
|
||||
Given using <dav-path-version> DAV path
|
||||
And user "Alice" has uploaded file with content "ownCloud test text file 0" to "textfile0.txt"
|
||||
And user "Alice" has uploaded file with content "OpenCloud test text file 0" to "textfile0.txt"
|
||||
When user "Alice" moves file "/textfile0.txt" to "/.htaccess" using the WebDAV API
|
||||
Then the HTTP status code should be "201"
|
||||
And user "Alice" should see the following elements
|
||||
|
||||
@@ -5,7 +5,7 @@ Feature: download file
|
||||
|
||||
Background:
|
||||
Given user "Alice" has been created with default attributes
|
||||
And user "Alice" has uploaded file with content "ownCloud test text file 0" to "/textfile0.txt"
|
||||
And user "Alice" has uploaded file with content "OpenCloud test text file 0" to "/textfile0.txt"
|
||||
And user "Alice" has uploaded file with content "Welcome this is just an example file for developers." to "/welcome.txt"
|
||||
|
||||
@smokeTest
|
||||
@@ -13,7 +13,7 @@ Feature: download file
|
||||
Given using <dav-path-version> DAV path
|
||||
When user "Alice" downloads file "/textfile0.txt" using the WebDAV API
|
||||
Then the HTTP status code should be "200"
|
||||
And the downloaded content should be "ownCloud test text file 0"
|
||||
And the downloaded content should be "OpenCloud test text file 0"
|
||||
Examples:
|
||||
| dav-path-version |
|
||||
| old |
|
||||
@@ -219,7 +219,7 @@ Feature: download file
|
||||
And the following headers should be set
|
||||
| header | value |
|
||||
| Content-Disposition | attachment; filename*=UTF-8''<encoded-file-name>; filename="<file-name>" |
|
||||
| Content-Security-Policy | child-src 'self'; connect-src 'self' blob: https://raw.githubusercontent.com/owncloud/awesome-ocis/; default-src 'none'; font-src 'self'; frame-ancestors 'self'; frame-src 'self' blob: https://embed.diagrams.net/; img-src 'self' data: blob: https://raw.githubusercontent.com/owncloud/awesome-ocis/; manifest-src 'self'; media-src 'self'; object-src 'self' blob:; script-src 'self' 'unsafe-inline'; style-src 'self' 'unsafe-inline' |
|
||||
| Content-Security-Policy | child-src 'self'; connect-src 'self' blob: https://raw.githubusercontent.com/opencloud-eu/awesome-opencloud/; default-src 'none'; font-src 'self'; frame-ancestors 'self'; frame-src 'self' blob: https://embed.diagrams.net/; img-src 'self' data: blob: https://raw.githubusercontent.com/opencloud-eu/awesome-opencloud/; manifest-src 'self'; media-src 'self'; object-src 'self' blob:; script-src 'self' 'unsafe-inline'; style-src 'self' 'unsafe-inline' |
|
||||
| X-Content-Type-Options | nosniff |
|
||||
| X-Frame-Options | SAMEORIGIN |
|
||||
| X-Permitted-Cross-Domain-Policies | none |
|
||||
@@ -247,7 +247,7 @@ Feature: download file
|
||||
And the following headers should be set
|
||||
| header | value |
|
||||
| Content-Disposition | attachment; filename*=UTF-8''%22quote%22double%22.txt; filename=""quote"double".txt" |
|
||||
| Content-Security-Policy | child-src 'self'; connect-src 'self' blob: https://raw.githubusercontent.com/owncloud/awesome-ocis/; default-src 'none'; font-src 'self'; frame-ancestors 'self'; frame-src 'self' blob: https://embed.diagrams.net/; img-src 'self' data: blob: https://raw.githubusercontent.com/owncloud/awesome-ocis/; manifest-src 'self'; media-src 'self'; object-src 'self' blob:; script-src 'self' 'unsafe-inline'; style-src 'self' 'unsafe-inline' |
|
||||
| Content-Security-Policy | child-src 'self'; connect-src 'self' blob: https://raw.githubusercontent.com/opencloud-eu/awesome-opencloud/; default-src 'none'; font-src 'self'; frame-ancestors 'self'; frame-src 'self' blob: https://embed.diagrams.net/; img-src 'self' data: blob: https://raw.githubusercontent.com/opencloud-eu/awesome-opencloud/; manifest-src 'self'; media-src 'self'; object-src 'self' blob:; script-src 'self' 'unsafe-inline'; style-src 'self' 'unsafe-inline' |
|
||||
| X-Content-Type-Options | nosniff |
|
||||
| X-Frame-Options | SAMEORIGIN |
|
||||
| X-Permitted-Cross-Domain-Policies | none |
|
||||
|
||||
@@ -1,7 +1,7 @@
|
||||
Feature: list files
|
||||
As a user
|
||||
I want to be able to list my files and folders (resources)
|
||||
So that I can understand my file structure in owncloud
|
||||
So that I can understand my file structure in OpenCloud
|
||||
|
||||
Background:
|
||||
Given user "Alice" has been created with default attributes
|
||||
|
||||
@@ -6,8 +6,8 @@ Feature: copy file
|
||||
Background:
|
||||
Given using OCS API version "1"
|
||||
And user "Alice" has been created with default attributes
|
||||
And user "Alice" has uploaded file with content "ownCloud test text file 0" to "/textfile0.txt"
|
||||
And user "Alice" has uploaded file with content "ownCloud test text file 1" to "/textfile1.txt"
|
||||
And user "Alice" has uploaded file with content "OpenCloud test text file 0" to "/textfile0.txt"
|
||||
And user "Alice" has uploaded file with content "OpenCloud test text file 1" to "/textfile1.txt"
|
||||
And user "Alice" has created folder "/FOLDER"
|
||||
|
||||
@smokeTest
|
||||
@@ -15,7 +15,7 @@ Feature: copy file
|
||||
Given using <dav-path-version> DAV path
|
||||
When user "Alice" copies file "/textfile0.txt" to "/FOLDER/textfile0.txt" using the WebDAV API
|
||||
Then the HTTP status code should be "201"
|
||||
And the content of file "/FOLDER/textfile0.txt" for user "Alice" should be "ownCloud test text file 0"
|
||||
And the content of file "/FOLDER/textfile0.txt" for user "Alice" should be "OpenCloud test text file 0"
|
||||
Examples:
|
||||
| dav-path-version |
|
||||
| old |
|
||||
@@ -27,7 +27,7 @@ Feature: copy file
|
||||
Given using <dav-path-version> DAV path
|
||||
When user "Alice" copies file "/textfile0.txt" to "/textfile1.txt" using the WebDAV API
|
||||
Then the HTTP status code should be "204"
|
||||
And the content of file "/textfile1.txt" for user "Alice" should be "ownCloud test text file 0"
|
||||
And the content of file "/textfile1.txt" for user "Alice" should be "OpenCloud test text file 0"
|
||||
Examples:
|
||||
| dav-path-version |
|
||||
| old |
|
||||
@@ -40,8 +40,8 @@ Feature: copy file
|
||||
# "/textfile1.txt" already exists in the skeleton, make another with only case differences in the file name
|
||||
When user "Alice" copies file "/textfile0.txt" to "/TextFile1.txt" using the WebDAV API
|
||||
Then the HTTP status code should be "201"
|
||||
And the content of file "/textfile1.txt" for user "Alice" should be "ownCloud test text file 1"
|
||||
And the content of file "/TextFile1.txt" for user "Alice" should be "ownCloud test text file 0"
|
||||
And the content of file "/textfile1.txt" for user "Alice" should be "OpenCloud test text file 1"
|
||||
And the content of file "/TextFile1.txt" for user "Alice" should be "OpenCloud test text file 0"
|
||||
Examples:
|
||||
| dav-path-version |
|
||||
| old |
|
||||
@@ -78,7 +78,7 @@ Feature: copy file
|
||||
Given using <dav-path-version> DAV path
|
||||
And user "Brian" has been created with default attributes
|
||||
And user "Brian" has created folder "/testshare"
|
||||
And user "Brian" has uploaded file with content "ownCloud test text file 1" to "textfile1.txt"
|
||||
And user "Brian" has uploaded file with content "OpenCloud test text file 1" to "textfile1.txt"
|
||||
And user "Brian" has sent the following resource share invitation:
|
||||
| resource | testshare |
|
||||
| space | Personal |
|
||||
@@ -89,7 +89,7 @@ Feature: copy file
|
||||
And user "Brian" has copied file "textfile1.txt" to "/testshare/overwritethis.txt"
|
||||
When user "Alice" copies file "/textfile0.txt" to "/Shares/testshare/overwritethis.txt" using the WebDAV API
|
||||
Then the HTTP status code should be "403"
|
||||
And the content of file "/Shares/testshare/overwritethis.txt" for user "Alice" should be "ownCloud test text file 1"
|
||||
And the content of file "/Shares/testshare/overwritethis.txt" for user "Alice" should be "OpenCloud test text file 1"
|
||||
Examples:
|
||||
| dav-path-version |
|
||||
| old |
|
||||
@@ -116,7 +116,7 @@ Feature: copy file
|
||||
And user "Alice" has created folder "FOLDER/sample-folder"
|
||||
When user "Alice" copies file "/textfile1.txt" to "/FOLDER" using the WebDAV API
|
||||
Then the HTTP status code should be "204"
|
||||
And the content of file "/FOLDER" for user "Alice" should be "ownCloud test text file 1"
|
||||
And the content of file "/FOLDER" for user "Alice" should be "OpenCloud test text file 1"
|
||||
And as "Alice" folder "/FOLDER/sample-folder" should not exist
|
||||
And as "Alice" file "/textfile1.txt" should exist
|
||||
Examples:
|
||||
@@ -700,8 +700,8 @@ Feature: copy file
|
||||
And user "Alice" has a share "testshare" synced
|
||||
When user "Alice" copies file "/textfile0.txt" to "/Shares/testshare/textfile0.txt" using the WebDAV API
|
||||
Then the HTTP status code should be "201"
|
||||
And the content of file "/Shares/testshare/textfile0.txt" for user "Alice" should be "ownCloud test text file 0"
|
||||
And the content of file "/testshare/textfile0.txt" for user "Brian" should be "ownCloud test text file 0"
|
||||
And the content of file "/Shares/testshare/textfile0.txt" for user "Alice" should be "OpenCloud test text file 0"
|
||||
And the content of file "/testshare/textfile0.txt" for user "Brian" should be "OpenCloud test text file 0"
|
||||
Examples:
|
||||
| dav-path-version |
|
||||
| old |
|
||||
@@ -720,11 +720,11 @@ Feature: copy file
|
||||
| shareType | user |
|
||||
| permissionsRole | Editor |
|
||||
And user "Alice" has a share "testshare" synced
|
||||
And user "Brian" has uploaded file with content "ownCloud test text file 0" to "/textfile0.txt"
|
||||
And user "Brian" has uploaded file with content "OpenCloud test text file 0" to "/textfile0.txt"
|
||||
When user "Brian" copies file "/textfile0.txt" to "/testshare/textfile0.txt" using the WebDAV API
|
||||
Then the HTTP status code should be "201"
|
||||
And the content of file "/Shares/testshare/textfile0.txt" for user "Alice" should be "ownCloud test text file 0"
|
||||
And the content of file "/testshare/textfile0.txt" for user "Brian" should be "ownCloud test text file 0"
|
||||
And the content of file "/Shares/testshare/textfile0.txt" for user "Alice" should be "OpenCloud test text file 0"
|
||||
And the content of file "/testshare/textfile0.txt" for user "Brian" should be "OpenCloud test text file 0"
|
||||
Examples:
|
||||
| dav-path-version |
|
||||
| old |
|
||||
@@ -743,12 +743,12 @@ Feature: copy file
|
||||
| shareType | user |
|
||||
| permissionsRole | Editor |
|
||||
And user "Alice" has a share "testshare" synced
|
||||
And user "Alice" has uploaded file with content "ownCloud test text file inside share" to "/Shares/testshare/fileInsideShare.txt"
|
||||
And user "Alice" has uploaded file with content "OpenCloud test text file inside share" to "/Shares/testshare/fileInsideShare.txt"
|
||||
When user "Alice" copies file "/Shares/testshare/fileInsideShare.txt" to "/fileInsideShare.txt" using the WebDAV API
|
||||
Then the HTTP status code should be "201"
|
||||
And as "Alice" file "/fileInsideShare.txt" should exist
|
||||
And the content of file "/fileInsideShare.txt" for user "Alice" should be "ownCloud test text file inside share"
|
||||
And the content of file "/testshare/fileInsideShare.txt" for user "Brian" should be "ownCloud test text file inside share"
|
||||
And the content of file "/fileInsideShare.txt" for user "Alice" should be "OpenCloud test text file inside share"
|
||||
And the content of file "/testshare/fileInsideShare.txt" for user "Brian" should be "OpenCloud test text file inside share"
|
||||
Examples:
|
||||
| dav-path-version |
|
||||
| old |
|
||||
@@ -805,7 +805,7 @@ Feature: copy file
|
||||
Given using <dav-path-version> DAV path
|
||||
And user "Brian" has been created with default attributes
|
||||
And user "Brian" has created folder "/testshare"
|
||||
And user "Brian" has uploaded file with content "ownCloud test text file inside share" to "/testshare/fileInsideShare.txt"
|
||||
And user "Brian" has uploaded file with content "OpenCloud test text file inside share" to "/testshare/fileInsideShare.txt"
|
||||
And user "Brian" has sent the following resource share invitation:
|
||||
| resource | testshare |
|
||||
| space | Personal |
|
||||
@@ -816,8 +816,8 @@ Feature: copy file
|
||||
When user "Brian" copies file "testshare/fileInsideShare.txt" to "/fileInsideShare.txt" using the WebDAV API
|
||||
Then the HTTP status code should be "201"
|
||||
And as "Brian" file "/fileInsideShare.txt" should exist
|
||||
And the content of file "/Shares/testshare/fileInsideShare.txt" for user "Alice" should be "ownCloud test text file inside share"
|
||||
And the content of file "/fileInsideShare.txt" for user "Brian" should be "ownCloud test text file inside share"
|
||||
And the content of file "/Shares/testshare/fileInsideShare.txt" for user "Alice" should be "OpenCloud test text file inside share"
|
||||
And the content of file "/fileInsideShare.txt" for user "Brian" should be "OpenCloud test text file inside share"
|
||||
Examples:
|
||||
| dav-path-version |
|
||||
| old |
|
||||
@@ -986,8 +986,8 @@ Feature: copy file
|
||||
Then the HTTP status code should be "201"
|
||||
And as "Brian" file "/Shares/testshare/textfile0.txt" should exist
|
||||
And as "Carol" file "/Shares/testshare/textfile0.txt" should exist
|
||||
And the content of file "/Shares/testshare/textfile0.txt" for user "Brian" should be "ownCloud test text file 0"
|
||||
And the content of file "/Shares/testshare/textfile0.txt" for user "Carol" should be "ownCloud test text file 0"
|
||||
And the content of file "/Shares/testshare/textfile0.txt" for user "Brian" should be "OpenCloud test text file 0"
|
||||
And the content of file "/Shares/testshare/textfile0.txt" for user "Carol" should be "OpenCloud test text file 0"
|
||||
Examples:
|
||||
| dav-path-version |
|
||||
| old |
|
||||
|
||||
Reference in New Issue
Block a user