Fixed line numbers in expected failure

This commit is contained in:
Prarup Gurung
2023-02-21 15:13:24 +05:45
parent 8b6df0d729
commit 5a46a19f99
4 changed files with 55 additions and 304 deletions
@@ -18,96 +18,6 @@ Feature: Exclude groups from receiving shares
And user "Brian" has been added to group "grp1"
And user "David" has been added to group "grp2"
@skipOnOcis
Scenario Outline: user cannot share with a group that is excluded from receiving shares but can share with other groups
Given using OCS API version "<ocs_api_version>"
And user "Alice" has created folder "PARENT"
And user "Alice" has uploaded file "filesForUpload/textfile.txt" to "fileToShare.txt"
And the administrator has added group "grp1" to the exclude groups from receiving shares list
When user "Alice" shares file "fileToShare.txt" with group "grp1" using the sharing API
Then the OCS status code should be "403"
And the HTTP status code should be "<http_status_code>"
And the OCS status message should be "The group is blacklisted for sharing"
And the sharing API should report to user "Brian" that no shares are in the pending state
When user "Alice" shares folder "PARENT" with group "grp1" using the sharing API
Then the OCS status code should be "403"
And the HTTP status code should be "<http_status_code>"
And the OCS status message should be "The group is blacklisted for sharing"
And the sharing API should report to user "Brian" that no shares are in the pending state
When user "Alice" shares file "fileToShare.txt" with group "grp2" using the sharing API
And user "Alice" shares folder "PARENT" with group "grp2" using the sharing API
And user "David" accepts share "/fileToShare.txt" offered by user "Alice" using the sharing API
And user "David" accepts share "/PARENT" offered by user "Alice" using the sharing API
Then as "David" file "/Shares/fileToShare.txt" should exist
And as "David" folder "/Shares/PARENT" should exist
Examples:
| ocs_api_version | http_status_code |
| 1 | 200 |
| 2 | 403 |
@skipOnOcis
Scenario Outline: exclude multiple groups from receiving shares stops the user to share with any of them
Given using OCS API version "<ocs_api_version>"
And group "grp3" has been created
And user "Brian" has been added to group "grp3"
And the administrator has added group "grp1, grp2, grp3" to the exclude group from sharing list
And user "Alice" has created folder "PARENT"
And user "Alice" has created folder "PARENT/CHILD"
And user "Alice" has uploaded file "filesForUpload/textfile.txt" to "fileToShare.txt"
And the administrator has added group "grp1" to the exclude groups from receiving shares list
And the administrator has added group "grp2" to the exclude groups from receiving shares list
And the administrator has added group "grp3" to the exclude groups from receiving shares list
When user "Alice" shares file "fileToShare.txt" with group "grp1" using the sharing API
Then the OCS status code should be "403"
And the HTTP status code should be "<http_status_code>"
And the OCS status message should be "The group is blacklisted for sharing"
And the sharing API should report to user "Brian" that no shares are in the pending state
When user "Alice" shares folder "PARENT" with group "grp2" using the sharing API
Then the OCS status code should be "403"
And the HTTP status code should be "<http_status_code>"
And the OCS status message should be "The group is blacklisted for sharing"
And the sharing API should report to user "David" that no shares are in the pending state
When user "Alice" shares folder "PARENT/CHILD" with group "grp3" using the sharing API
Then the OCS status code should be "403"
And the HTTP status code should be "<http_status_code>"
And the OCS status message should be "The group is blacklisted for sharing"
And the sharing API should report to user "Brian" that no shares are in the pending state
Examples:
| ocs_api_version | http_status_code |
| 1 | 200 |
| 2 | 403 |
@skipOnOcis
Scenario Outline: user cannot reshare a received share with a group that is excluded from receiving shares but can share with other groups
Given using OCS API version "<ocs_api_version>"
And user "Carol" has created folder "PARENT"
And user "Carol" has uploaded file "filesForUpload/textfile.txt" to "textfile0.txt"
And user "Carol" has shared file "textfile0.txt" with user "Alice"
And user "Alice" has accepted share "/textfile0.txt" offered by user "Carol"
And user "Carol" has shared folder "PARENT" with user "Alice"
And user "Alice" has accepted share "/PARENT" offered by user "Carol"
And the administrator has added group "grp1" to the exclude groups from receiving shares list
When user "Alice" shares file "/Shares/textfile0.txt" with group "grp1" using the sharing API
Then the OCS status code should be "403"
And the HTTP status code should be "<http_status_code>"
And the OCS status message should be "The group is blacklisted for sharing"
And the sharing API should report to user "Brian" that no shares are in the pending state
When user "Alice" shares folder "/Shares/PARENT" with group "grp1" using the sharing API
Then the OCS status code should be "403"
And the HTTP status code should be "<http_status_code>"
And the OCS status message should be "The group is blacklisted for sharing"
And the sharing API should report to user "Brian" that no shares are in the pending state
When user "Alice" shares file "/Shares/textfile0.txt" with group "grp2" using the sharing API
And user "Alice" shares folder "/Shares/PARENT" with group "grp2" using the sharing API
And user "David" accepts share "/textfile0.txt" offered by user "Alice" using the sharing API
And user "David" accepts share "/PARENT" offered by user "Alice" using the sharing API
Then as "David" file "/Shares/textfile0.txt" should exist
And as "David" folder "/Shares/PARENT" should exist
Examples:
| ocs_api_version | http_status_code |
| 1 | 200 |
| 2 | 403 |
Scenario Outline: sharing with a user that is part of a group that is excluded from receiving shares still works
Given using OCS API version "<ocs_api_version>"