Skip to content

Commit

Permalink
Given steps changed to when
Browse files Browse the repository at this point in the history
  • Loading branch information
jasson99 committed Mar 6, 2020
1 parent d3647f1 commit 3738e09
Showing 1 changed file with 13 additions and 12 deletions.
25 changes: 13 additions & 12 deletions tests/acceptance/features/apiFederation/federated.feature
Original file line number Diff line number Diff line change
Expand Up @@ -593,9 +593,9 @@ Feature: federated
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 user "user0" has uploaded file with content "thisContentIsFinal" to "/PARENT/RandomFolder/file-to-share"
And using OCS API version "<ocs-api-version>"
When using server "LOCAL"
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 |
Expand All @@ -608,10 +608,10 @@ Feature: federated
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 user "user0" has uploaded file with content "thisContentIsFinal" to "/PARENT/RandomFolder/new-file"
And user "user0" has created folder "/PARENT/RandomFolder/sub-folder"
And using OCS API version "<ocs-api-version>"
When using server "LOCAL"
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
Expand All @@ -628,12 +628,13 @@ Feature: federated
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 user "user0" has deleted folder "/PARENT/RandomFolder/sub-folder"
And user "user0" has deleted file "/PARENT/RandomFolder/file-to-share"
And using OCS API version "<ocs-api-version>"
When using server "LOCAL"
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 |
Expand All @@ -646,13 +647,13 @@ Feature: federated
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 user "user0" has moved folder "/PARENT/RandomFolder/sub-folder" to "/PARENT/RandomFolder/renamed-sub-folder"
And user "user0" has moved file "/PARENT/RandomFolder/file-to-share" to "/PARENT/RandomFolder/renamedFile"
And using OCS API version "<ocs-api-version>"
When using server "LOCAL"
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" should be "thisContentShouldBeVisible"
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:
Expand Down

0 comments on commit 3738e09

Please sign in to comment.