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.

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

[Tests-Only] Add scenario outline for scenario in which sharer unshares the federated share and receiver no longer sees the share #37099

Merged
merged 1 commit into from
Mar 10, 2020
Merged
Changes from all commits
Commits
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
10 changes: 7 additions & 3 deletions tests/acceptance/features/apiFederation/federated.feature
Original file line number Diff line number Diff line change
Expand Up @@ -809,13 +809,17 @@ Feature: federated
| 1 |
| 2 |

Scenario: sharer unshares the federated share and the receiver no longer sees the files/folders
Scenario Outline: sharer unshares the federated share and the receiver no longer sees the files/folders
Given user "user1" has created folder "/PARENT/RandomFolder"
And user "user1" has uploaded file with content "thisContentShouldBeVisible" 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 "1"
And using OCS API version "<ocs-api-version>"
When user "user1" deletes the last share using the sharing API
And using server "REMOTE"
Then as "user0" file "/RandomFolder/file-to-share" should not exist
And as "user0" folder "/RandomFolder" should not exist
And as "user0" folder "/RandomFolder" should not exist
Examples:
| ocs-api-version |
| 1 |
| 2 |