Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[Tests-Only] Test that changes are correctly seen at both ends when federated sharer/receiver moves the location of share #37102

Merged
merged 1 commit into from
Mar 11, 2020
Merged

[Tests-Only] Test that changes are correctly seen at both ends when federated sharer/receiver moves the location of share #37102

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
45 changes: 45 additions & 0 deletions tests/acceptance/features/apiFederation/federated.feature
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -819,6 +819,51 @@ Feature: federated
And using server "REMOTE"
Then as "user0" file "/RandomFolder/file-to-share" should not exist
And as "user0" folder "/RandomFolder" should not exist
Examples:
| ocs-api-version |
| 1 |
| 2 |

Scenario Outline: federated share receiver can move the location of the received share and changes are correctly seen at both ends
Given user "user1" has created folder "/PARENT/RandomFolder"
And user "user1" has uploaded file with content "thisContentIsVisible" to "PARENT/RandomFolder/file-to-share"
And user "user1" from server "LOCAL" has shared "/PARENT/RandomFolder" with user "user0" from server "REMOTE"
And user "user0" from server "REMOTE" has accepted the last pending share
And using OCS API version "<ocs-api-version>"
And using server "REMOTE"
When user "user0" creates folder "/CHILD" using the WebDAV API
And user "user0" creates folder "/CHILD/newRandomFolder" using the WebDAV API
And user "user0" moves folder "/RandomFolder" to "/CHILD/newRandomFolder/RandomFolder" using the WebDAV API
Then as "user0" file "/CHILD/newRandomFolder/RandomFolder/file-to-share" should exist
When using server "LOCAL"
Then as "user1" file "/PARENT/RandomFolder/file-to-share" should exist
When user "user1" uploads file with content "thisIsTheContentOfNewFile" to "/PARENT/RandomFolder/newFile" using the WebDAV API
And user "user1" uploads file with content "theContentIsChanged" to "/PARENT/RandomFolder/file-to-share" using the WebDAV API
And using server "REMOTE"
Then as "user0" file "/CHILD/newRandomFolder/RandomFolder/newFile" should exist
And the content of file "/CHILD/newRandomFolder/RandomFolder/file-to-share" for user "user0" should be "theContentIsChanged"
Examples:
| ocs-api-version |
| 1 |
| 2 |

Scenario Outline: federated sharer can move the location of the received share and changes are correctly seen at both ends
Given user "user1" has created folder "/PARENT/RandomFolder"
And user "user1" has uploaded file with content "thisContentIsVisible" to "PARENT/RandomFolder/file-to-share"
And user "user1" from server "LOCAL" has shared "/PARENT/RandomFolder" with user "user0" from server "REMOTE"
And user "user0" from server "REMOTE" has accepted the last pending share
And using OCS API version "<ocs-api-version>"
When user "user1" creates folder "/CHILD" using the WebDAV API
And user "user1" creates folder "/CHILD/newRandomFolder" using the WebDAV API
And user "user1" moves folder "PARENT/RandomFolder" to "/CHILD/newRandomFolder/RandomFolder" using the WebDAV API
Then as "user1" file "/CHILD/newRandomFolder/RandomFolder/file-to-share" should exist
When using server "REMOTE"
Then as "user0" file "/RandomFolder/file-to-share" should exist
When user "user0" uploads file with content "thisIsTheContentOfNewFile" to "/RandomFolder/newFile" using the WebDAV API
And user "user0" uploads file with content "theContentIsChanged" to "/RandomFolder/file-to-share" using the WebDAV API
And using server "LOCAL"
Then as "user1" file "/CHILD/newRandomFolder/RandomFolder/newFile" should exist
And the content of file "/CHILD/newRandomFolder/RandomFolder/file-to-share" for user "user1" should be "theContentIsChanged"
Examples:
| ocs-api-version |
| 1 |
Expand Down