skip new behavior tests for reva-master

This commit is contained in:
Saw-jan
2023-07-31 12:57:00 +05:45
parent a2ee62bde1
commit 57c78b0a19
10 changed files with 24 additions and 24 deletions
@@ -54,7 +54,7 @@ Feature: Resharing
And user "Carol" should be included in the response And user "Carol" should be included in the response
And user "Damian" should be included in the response And user "Damian" should be included in the response
@skipOnRevaMaster
Scenario: user can't share with more permissions than they have Scenario: user can't share with more permissions than they have
When user "Damian" shares folder "Shares/folder" with user "Ember" with permissions "31" using the sharing API When user "Damian" shares folder "Shares/folder" with user "Ember" with permissions "31" using the sharing API
Then the OCS status code should be "403" Then the OCS status code should be "403"
@@ -88,7 +88,7 @@ Feature: Resharing
| Brian | 998 | should exist | | Brian | 998 | should exist |
| Carol | 100 | should not exist | | Carol | 100 | should not exist |
@skipOnRevaMaster
Scenario Outline: resharing folder with different permissions Scenario Outline: resharing folder with different permissions
When user "<user>" shares folder "Shares/folder" with user "Ember" with permissions "<permissions>" using the sharing API When user "<user>" shares folder "Shares/folder" with user "Ember" with permissions "<permissions>" using the sharing API
Then the OCS status code should be "<code>" Then the OCS status code should be "<code>"
@@ -100,7 +100,7 @@ Feature: Resharing
| Damian | 27 | 403 | | Damian | 27 | 403 |
| Damian | 31 | 403 | | Damian | 31 | 403 |
@skipOnRevaMaster
Scenario Outline: Resharing files with different permissions Scenario Outline: Resharing files with different permissions
Given user "Alice" has uploaded file with content "Random data" to "/file.txt" Given user "Alice" has uploaded file with content "Random data" to "/file.txt"
And user "Alice" has shared file "/file.txt" with user "Brian" with permissions "<shareepermissions>" And user "Alice" has shared file "/file.txt" with user "Brian" with permissions "<shareepermissions>"
@@ -131,7 +131,7 @@ Feature: Share spaces
| editor | | editor |
| viewer | | viewer |
@skipOnRevaMaster
Scenario Outline: user with editor or viewer role cannot share a space to another user Scenario Outline: user with editor or viewer role cannot share a space to another user
Given user "Alice" has shared a space "share space" with settings: Given user "Alice" has shared a space "share space" with settings:
| shareWith | Brian | | shareWith | Brian |
@@ -172,7 +172,7 @@ Feature: Share spaces
| manager | editor | | manager | editor |
| manager | viewer | | manager | viewer |
@skipOnRevaMaster
Scenario Outline: user without manager role cannot change the role of space members Scenario Outline: user without manager role cannot change the role of space members
Given user "Alice" has shared a space "share space" with settings: Given user "Alice" has shared a space "share space" with settings:
| shareWith | Brian | | shareWith | Brian |
@@ -70,7 +70,7 @@ Feature: Share spaces via link
And for user "Alice" the space "share space" should contain these entries: And for user "Alice" the space "share space" should contain these entries:
| lorem.txt | | lorem.txt |
@skipOnRevaMaster
Scenario Outline: user without manager role cannot share a space to public via link Scenario Outline: user without manager role cannot share a space to public via link
Given user "Alice" has shared a space "share space" with settings: Given user "Alice" has shared a space "share space" with settings:
| shareWith | Brian | | shareWith | Brian |
@@ -65,7 +65,7 @@ Feature: Share a file or folder that is inside a space
| file.txt | file | viewer | 2042-03-25T23:59:59+0100 | 2042-03-25 | | file.txt | file | viewer | 2042-03-25T23:59:59+0100 | 2042-03-25 |
| file.txt | file | editor | | | | file.txt | file | editor | | |
@skipOnRevaMaster
Scenario Outline: user participant of the project space without space manager role cannot share an entity to another user Scenario Outline: user participant of the project space without space manager role cannot share an entity to another user
Given user "Alice" has shared a space "share sub-item" with settings: Given user "Alice" has shared a space "share sub-item" with settings:
| shareWith | Brian | | shareWith | Brian |
@@ -96,7 +96,7 @@ Feature: Share a file or folder that is inside a space via public link
| folder | /folder | folder | httpd/unix-directory | | folder | /folder | folder | httpd/unix-directory |
| folder/file.txt | /file.txt | file | text/plain | | folder/file.txt | /file.txt | file | text/plain |
@skipOnRevaMaster
Scenario Outline: user participant of the project space without space manager role cannot share an entity inside project space via public link Scenario Outline: user participant of the project space without space manager role cannot share an entity inside project space via public link
Given user "Alice" has shared a space "share sub-item" with settings: Given user "Alice" has shared a space "share sub-item" with settings:
| shareWith | Brian | | shareWith | Brian |
@@ -10,7 +10,7 @@ Feature: reshare as public link
| Alice | | Alice |
| Brian | | Brian |
@skipOnRevaMaster
Scenario Outline: creating a public link from a share with read permission only is not allowed Scenario Outline: creating a public link from a share with read permission only is not allowed
Given using OCS API version "<ocs_api_version>" Given using OCS API version "<ocs_api_version>"
And user "Alice" has created folder "/test" And user "Alice" has created folder "/test"
@@ -46,7 +46,7 @@ Feature: reshare as public link
| 1 | 100 | | 1 | 100 |
| 2 | 200 | | 2 | 200 |
@skipOnRevaMaster
Scenario Outline: creating an upload public link from a share with share+read only permissions is not allowed Scenario Outline: creating an upload public link from a share with share+read only permissions is not allowed
Given using OCS API version "<ocs_api_version>" Given using OCS API version "<ocs_api_version>"
And user "Alice" has created folder "/test" And user "Alice" has created folder "/test"
@@ -63,7 +63,7 @@ Feature: reshare as public link
| 1 | 200 | | 1 | 200 |
| 2 | 403 | | 2 | 403 |
@skipOnRevaMaster
Scenario Outline: creating a public link from a share with read+write permissions only is not allowed Scenario Outline: creating a public link from a share with read+write permissions only is not allowed
Given using OCS API version "<ocs_api_version>" Given using OCS API version "<ocs_api_version>"
And user "Alice" has created folder "/test" And user "Alice" has created folder "/test"
@@ -120,7 +120,7 @@ Feature: reshare as public link
| 1 | 100 | | 1 | 100 |
| 2 | 200 | | 2 | 200 |
@skipOnRevaMaster
Scenario Outline: creating an upload public link from a sub-folder of a share with share+read only permissions is not allowed Scenario Outline: creating an upload public link from a sub-folder of a share with share+read only permissions is not allowed
Given using OCS API version "<ocs_api_version>" Given using OCS API version "<ocs_api_version>"
And user "Alice" has created folder "/test" And user "Alice" has created folder "/test"
@@ -138,7 +138,7 @@ Feature: reshare as public link
| 1 | 200 | | 1 | 200 |
| 2 | 403 | | 2 | 403 |
@skipOnRevaMaster
Scenario Outline: increasing permissions of a public link of a share with share+read only permissions is not allowed Scenario Outline: increasing permissions of a public link of a share with share+read only permissions is not allowed
Given using OCS API version "<ocs_api_version>" Given using OCS API version "<ocs_api_version>"
And user "Alice" has created folder "/test" And user "Alice" has created folder "/test"
@@ -159,7 +159,7 @@ Feature: reshare as public link
| 1 | 200 | | 1 | 200 |
| 2 | 403 | | 2 | 403 |
@skipOnRevaMaster
Scenario Outline: increasing permissions of a public link from a sub-folder of a share with share+read only permissions is not allowed Scenario Outline: increasing permissions of a public link from a sub-folder of a share with share+read only permissions is not allowed
Given using OCS API version "<ocs_api_version>" Given using OCS API version "<ocs_api_version>"
And user "Alice" has created folder "/test" And user "Alice" has created folder "/test"
@@ -246,7 +246,7 @@ Feature: update a public link share
| 1 | 100 | | 1 | 100 |
| 2 | 200 | | 2 | 200 |
@skipOnRevaMaster
Scenario Outline: adding public upload to a read only shared folder as recipient is not allowed using the public API Scenario Outline: adding public upload to a read only shared folder as recipient is not allowed using the public API
Given using OCS API version "<ocs_api_version>" Given using OCS API version "<ocs_api_version>"
And user "Brian" has been created with default attributes and without skeleton files And user "Brian" has been created with default attributes and without skeleton files
@@ -288,7 +288,7 @@ Feature: update a public link share
| 1 | 100 | | 1 | 100 |
| 2 | 200 | | 2 | 200 |
@skipOnRevaMaster
Scenario Outline: adding public link with all permissions to a read only shared folder as recipient is not allowed using the public API Scenario Outline: adding public link with all permissions to a read only shared folder as recipient is not allowed using the public API
Given using OCS API version "<ocs_api_version>" Given using OCS API version "<ocs_api_version>"
And user "Brian" has been created with default attributes and without skeleton files And user "Brian" has been created with default attributes and without skeleton files
@@ -11,7 +11,7 @@ Feature: sharing
| Brian | | Brian |
| Carol | | Carol |
@smokeTest @smokeTest @skipOnRevaMaster
Scenario Outline: user is not allowed to reshare file when reshare permission is not given Scenario Outline: user is not allowed to reshare file when reshare permission is not given
Given using OCS API version "<ocs_api_version>" Given using OCS API version "<ocs_api_version>"
And user "Alice" has uploaded file "filesForUpload/textfile.txt" to "/textfile0.txt" And user "Alice" has uploaded file "filesForUpload/textfile.txt" to "/textfile0.txt"
@@ -28,7 +28,7 @@ Feature: sharing
| 1 | 200 | | 1 | 200 |
| 2 | 403 | | 2 | 403 |
@skipOnRevaMaster
Scenario Outline: user is not allowed to reshare folder when reshare permission is not given Scenario Outline: user is not allowed to reshare folder when reshare permission is not given
Given using OCS API version "<ocs_api_version>" Given using OCS API version "<ocs_api_version>"
And user "Alice" has created folder "/FOLDER" And user "Alice" has created folder "/FOLDER"
@@ -109,7 +109,7 @@ Feature: sharing
| 1 | 100 | | 1 | 100 |
| 2 | 200 | | 2 | 200 |
@skipOnRevaMaster
Scenario Outline: user is not allowed to reshare file and set more permissions bits Scenario Outline: user is not allowed to reshare file and set more permissions bits
Given using OCS API version "<ocs_api_version>" Given using OCS API version "<ocs_api_version>"
And user "Alice" has uploaded file "filesForUpload/textfile.txt" to "/textfile0.txt" And user "Alice" has uploaded file "filesForUpload/textfile.txt" to "/textfile0.txt"
@@ -179,7 +179,7 @@ Feature: sharing
| 1 | 100 | 17 | 9 | 1 | | 1 | 100 | 17 | 9 | 1 |
| 2 | 200 | 17 | 9 | 1 | | 2 | 200 | 17 | 9 | 1 |
@skipOnRevaMaster
Scenario Outline: user is not allowed to reshare folder and set more permissions bits Scenario Outline: user is not allowed to reshare folder and set more permissions bits
Given using OCS API version "<ocs_api_version>" Given using OCS API version "<ocs_api_version>"
And user "Alice" has created folder "/PARENT" And user "Alice" has created folder "/PARENT"
@@ -220,7 +220,7 @@ Feature: sharing
| 1 | 200 | 19 | 15 | | 1 | 200 | 19 | 15 |
| 2 | 403 | 19 | 15 | | 2 | 403 | 19 | 15 |
@skipOnRevaMaster
Scenario Outline: user is not allowed to reshare folder and add delete permission bit (8) Scenario Outline: user is not allowed to reshare folder and add delete permission bit (8)
Given using OCS API version "<ocs_api_version>" Given using OCS API version "<ocs_api_version>"
And user "Alice" has created folder "/PARENT" And user "Alice" has created folder "/PARENT"
@@ -29,7 +29,7 @@ Feature: a subfolder of a received share can be reshared
| 1 | 100 | | 1 | 100 |
| 2 | 200 | | 2 | 200 |
@skipOnRevaMaster
Scenario Outline: user is not allowed to reshare a sub-folder with more permissions Scenario Outline: user is not allowed to reshare a sub-folder with more permissions
Given using OCS API version "<ocs_api_version>" Given using OCS API version "<ocs_api_version>"
And user "Alice" has shared folder "/TMP" with user "Brian" with permissions <received_permissions> And user "Alice" has shared folder "/TMP" with user "Brian" with permissions <received_permissions>
@@ -123,7 +123,7 @@ Feature: a subfolder of a received share can be reshared
| 1 | 100 | | 1 | 100 |
| 2 | 200 | | 2 | 200 |
@issue-2214 @issue-2214 @skipOnRevaMaster
Scenario Outline: user is not allowed to update reshare of a sub-folder with more permissions Scenario Outline: user is not allowed to update reshare of a sub-folder with more permissions
Given using OCS API version "<ocs_api_version>" Given using OCS API version "<ocs_api_version>"
And user "Alice" has shared folder "/TMP" with user "Brian" with permissions "share,read" And user "Alice" has shared folder "/TMP" with user "Brian" with permissions "share,read"
@@ -46,7 +46,7 @@ Feature: sharing
| 1 | 100 | | 1 | 100 |
| 2 | 200 | | 2 | 200 |
@skipOnRevaMaster
Scenario Outline: do not allow update of reshare to exceed permissions Scenario Outline: do not allow update of reshare to exceed permissions
Given using OCS API version "<ocs_api_version>" Given using OCS API version "<ocs_api_version>"
And user "Alice" has shared folder "/TMP" with user "Brian" with permissions "share,read" And user "Alice" has shared folder "/TMP" with user "Brian" with permissions "share,read"