sevenhill/QSfera
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

[full-ci] Bump reva (#7675)

Browse Source 
* Bump reva

* Adapt expected failures

* update MOVE files between shares tests

---------

Co-authored-by: Saw-jan <saw.jan.grg3e@gmail.com>
This commit is contained in:
Andre Duffeck
2023-11-09 15:26:16 +01:00
committed by GitHub
co-authored by Saw-jan
parent ebadf53d58
commit 7bb67d7e41
12 changed files with 27 additions and 184 deletions
Download Patch File Download Diff File Expand all files Collapse all files
tests/acceptance/features/apiSpacesShares/etagPropagation.feature
-46
View File
@@ -136,29 +136,6 @@ Feature: check etag propagation after different file alterations
| Brian | /dst | Shares |
Scenario: share receiver moving a file from one folder to an other changes the etags of both folders for all collaborators
Given user "Alice" has created folder "/dst"
And user "Alice" has uploaded file with content "uploaded content" to "/upload/file.txt"
And user "Alice" has shared folder "/upload" with user "Brian"
And user "Alice" has shared folder "/dst" with user "Brian"
And user "Alice" has stored etag of element "/" inside space "Personal"
And user "Alice" has stored etag of element "/upload" inside space "Personal"
And user "Alice" has stored etag of element "/dst" inside space "Personal"
And user "Brian" has stored etag of element "/" inside space "Shares"
And user "Brian" has stored etag of element "/upload" inside space "Shares"
And user "Brian" has stored etag of element "/dst" inside space "Shares"
When user "Brian" moves file "/upload/file.txt" to "/dst/file.txt" in space "Shares" using the WebDAV API
Then the HTTP status code should be "201"
And these etags should have changed
| user | path | space |
| Alice | / | Personal |
| Alice | /upload | Personal |
| Alice | /dst | Personal |
| Brian | / | Shares |
| Brian | /upload | Shares |
| Brian | /dst | Shares |
Scenario: sharer moving a folder from one folder to an other changes the etags of both folders for all collaborators
Given user "Alice" has created folder "/dst"
And user "Alice" has created folder "/upload/toMove"
@@ -182,29 +159,6 @@ Feature: check etag propagation after different file alterations
| Brian | /dst | Shares |
Scenario: share receiver moving a folder from one folder to an other changes the etags of both folders for all collaborators
Given user "Alice" has created folder "/dst"
And user "Alice" has created folder "/upload/toMove"
And user "Alice" has shared folder "/upload" with user "Brian"
And user "Alice" has shared folder "/dst" with user "Brian"
And user "Alice" has stored etag of element "/" inside space "Personal"
And user "Alice" has stored etag of element "/upload" inside space "Personal"
And user "Alice" has stored etag of element "/dst" inside space "Personal"
And user "Brian" has stored etag of element "/" inside space "Shares"
And user "Brian" has stored etag of element "/upload" inside space "Shares"
And user "Brian" has stored etag of element "/dst" inside space "Shares"
When user "Brian" moves file "/upload/toMove" to "/dst/toMove" in space "Shares" using the WebDAV API
Then the HTTP status code should be "201"
And these etags should have changed
| user | path | space |
| Alice | / | Personal |
| Alice | /upload | Personal |
| Alice | /dst | Personal |
| Brian | / | Shares |
| Brian | /upload | Shares |
| Brian | /dst | Shares |
Scenario: share receiver creating a folder inside a folder received as a share changes its etag for all collaborators
Given user "Alice" has shared folder "/upload" with user "Brian"
And user "Alice" has stored etag of element "/" inside space "Personal"
tests/acceptance/features/apiSpacesShares/moveSpaces.feature
+9 -32
View File
@@ -208,12 +208,10 @@ Feature: move (rename) file
And user "Brian" has shared folder "/testshare1" with user "Alice" with permissions "31"
And user "Brian" has shared folder "/testshare2" with user "Alice" with permissions "31"
When user "Alice" moves file "/testshare1/testshare1.txt" from space "Shares" to "/testshare2/testshare1.txt" inside space "Shares" using the WebDAV API
Then the HTTP status code should be "201"
And for user "Alice" folder "testshare2" of the space "Shares" should contain these entries:
Then the HTTP status code should be "502"
And for user "Alice" folder "testshare1" of the space "Shares" should contain these entries:
| testshare1.txt |
And for user "Brian" folder "testshare2" of the space "Personal" should contain these entries:
| testshare1.txt |
But for user "Alice" folder "testshare1" of the space "Shares" should not contain these entries:
But for user "Alice" folder "testshare2" of the space "Shares" should not contain these entries:
| testshare1.txt |
@@ -224,10 +222,10 @@ Feature: move (rename) file
And user "Brian" has shared folder "/testshare1" with user "Alice" with permissions "31"
And user "Brian" has shared folder "/testshare2" with user "Alice" with permissions "17"
When user "Alice" moves file "/testshare1/testshare1.txt" from space "Shares" to "/testshare2/testshare1.txt" inside space "Shares" using the WebDAV API
Then the HTTP status code should be "403"
And for user "Alice" folder "testshare2" of the space "Shares" should not contain these entries:
Then the HTTP status code should be "502"
And for user "Alice" folder "testshare1" of the space "Shares" should contain these entries:
| testshare1.txt |
And for user "Brian" folder "testshare2" of the space "Personal" should not contain these entries:
But for user "Alice" folder "testshare2" of the space "Shares" should not contain these entries:
| testshare1.txt |
@@ -238,34 +236,13 @@ Feature: move (rename) file
And user "Brian" has shared folder "/testshare1" with user "Alice" with permissions "17"
And user "Brian" has shared folder "/testshare2" with user "Alice" with permissions "31"
When user "Alice" moves file "/testshare1/testshare1.txt" from space "Shares" to "/testshare2/testshare1.txt" inside space "Shares" using the WebDAV API
Then the HTTP status code should be "403"
And for user "Alice" folder "testshare2" of the space "Shares" should not contain these entries:
Then the HTTP status code should be "502"
And for user "Alice" folder "testshare1" of the space "Shares" should contain these entries:
| testshare1.txt |
And for user "Brian" folder "testshare2" of the space "Personal" should not contain these entries:
But for user "Alice" folder "testshare2" of the space "Shares" should not contain these entries:
| testshare1.txt |
Scenario: checking file id after a move between received shares
Given user "Alice" has created the following folders
| path |
| /folderA |
| /folderB |
And user "Alice" has shared folder "/folderA" with user "Brian"
And user "Alice" has shared folder "/folderB" with user "Brian"
And user "Brian" has created a folder "/folderA/ONE" in space "Shares"
And user "Brian" has created a folder "/folderA/ONE/TWO" in space "Shares"
And user "Brian" has stored id of folder "/folderA/ONE" of the space "Shares"
When user "Brian" moves folder "/folderA/ONE" from space "Shares" to "/folderB/ONE" inside space "Shares" using the WebDAV API
Then the HTTP status code should be "201"
And for user "Brian" the space "Shares" should contain these entries:
| /folderA |
And for user "Brian" folder "folderB" of the space "Shares" should contain these entries:
| /ONE |
And for user "Brian" folder "folderA" of the space "Shares" should not contain these entries:
| /ONE |
And user "Brian" folder "/folderB/ONE" of the space "Shares" should have the previously stored id
Scenario: moving a file out of a shared folder as a sharer
Given user "Brian" has created folder "/testshare"
And user "Brian" has uploaded file with content "test data" to "/testshare/testfile.txt"