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] Acceptance test to assert sharer can change files or folders in the federated share #37081

Merged
merged 1 commit into from
Mar 6, 2020
Merged

[Tests-Only] Acceptance test to assert sharer can change files or folders in the federated share #37081

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
74 changes: 74 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 @@ -609,6 +609,80 @@ Feature: federated
And using OCS API version "<ocs-api-version>"
When using server "LOCAL"
Then the content of file "/file-to-share" for user "user1" should be "thisContentIsVisible"
Examples:
| ocs-api-version |
| 1 |
| 2 |

Scenario Outline: sharer modifies the share which was shared to the federated share receiver
Given using server "REMOTE"
And user "user0" has created folder "/PARENT/RandomFolder"
And user "user0" has uploaded file with content "thisContentShouldBeChanged" to "/PARENT/RandomFolder/file-to-share"
And user "user0" from server "REMOTE" has shared "/PARENT/RandomFolder/file-to-share" with user "user1" from server "LOCAL"
And user "user1" from server "LOCAL" has accepted the last pending share
And using OCS API version "<ocs-api-version>"
jasson99 marked this conversation as resolved.
Show resolved Hide resolved
When user "user0" uploads file with content "thisContentIsFinal" to "/PARENT/RandomFolder/file-to-share" using the WebDAV API
And using server "LOCAL"
Then the content of file "/file-to-share" for user "user1" should be "thisContentIsFinal"
Examples:
| ocs-api-version |
| 1 |
| 2 |

Scenario Outline: sharer adds files/folders in the share which was shared to the federated share receiver
Given using server "REMOTE"
And user "user0" has created folder "/PARENT/RandomFolder"
And user "user0" has uploaded file with content "thisContentShouldBeVisible" to "/PARENT/RandomFolder/file-to-share"
And user "user0" from server "REMOTE" has shared "/PARENT/RandomFolder" with user "user1" from server "LOCAL"
And user "user1" from server "LOCAL" has accepted the last pending share
And using OCS API version "<ocs-api-version>"
When user "user0" uploads file with content "thisContentIsFinal" to "/PARENT/RandomFolder/new-file" using the WebDAV API
And user "user0" creates folder "/PARENT/RandomFolder/sub-folder" using the WebDAV API
And using server "LOCAL"
Then as "user1" file "/RandomFolder/new-file" should exist
And as "user1" file "/RandomFolder/file-to-share" should exist
And as "user1" folder "/RandomFolder/sub-folder" should exist
And the content of file "/RandomFolder/new-file" for user "user1" should be "thisContentIsFinal"
Examples:
| ocs-api-version |
| 1 |
| 2 |

Scenario Outline: sharer deletes files/folders of the share which was shared to the federated share receiver
Given using server "REMOTE"
And user "user0" has created folder "/PARENT/RandomFolder"
And user "user0" has created folder "/PARENT/RandomFolder/sub-folder"
And user "user0" has uploaded file with content "thisContentShouldBeVisible" to "/PARENT/RandomFolder/file-to-share"
And user "user0" from server "REMOTE" has shared "/PARENT/RandomFolder" with user "user1" from server "LOCAL"
And user "user1" from server "LOCAL" has accepted the last pending share
And using OCS API version "<ocs-api-version>"
When user "user0" deletes folder "/PARENT/RandomFolder/sub-folder" using the WebDAV API
And user "user0" deletes file "/PARENT/RandomFolder/file-to-share" using the WebDAV API
And using server "LOCAL"
Then as "user1" file "/RandomFolder/file-to-share" should not exist
And as "user1" folder "/RandomFolder/sub-folder" should not exist
But as "user1" folder "/RandomFolder" should exist
Examples:
| ocs-api-version |
| 1 |
| 2 |

Scenario Outline: sharer renames files/folders of the share which was shared to the federated share receiver
Given using server "REMOTE"
And user "user0" has created folder "/PARENT/RandomFolder"
And user "user0" has created folder "/PARENT/RandomFolder/sub-folder"
And user "user0" has uploaded file with content "thisContentShouldBeVisible" to "/PARENT/RandomFolder/file-to-share"
And user "user0" from server "REMOTE" has shared "/PARENT/RandomFolder" with user "user1" from server "LOCAL"
And user "user1" from server "LOCAL" has accepted the last pending share
And using OCS API version "<ocs-api-version>"
When user "user0" moves folder "/PARENT/RandomFolder/sub-folder" to "/PARENT/RandomFolder/renamed-sub-folder" using the WebDAV API
And user "user0" moves file "/PARENT/RandomFolder/file-to-share" to "/PARENT/RandomFolder/renamedFile" using the WebDAV API
And using server "LOCAL"
Then as "user1" file "/RandomFolder/file-to-share" should not exist
But as "user1" file "/RandomFolder/renamedFile" should exist
And the content of file "/RandomFolder/renamedFile" for user "user1" should be "thisContentShouldBeVisible"
And as "user1" folder "/RandomFolder/sub-folder" should not exist
But as "user1" folder "/RandomFolder/renamed-sub-folder" should exist
Examples:
| ocs-api-version |
| 1 |
Expand Down