From 528862c3db1efb5d1f5061d47bccc4b862c207c3 Mon Sep 17 00:00:00 2001 From: amrita Date: Fri, 17 Mar 2023 15:00:51 +0545 Subject: [PATCH] Remove unwanted scenario --- ...ected-failures-localAPI-on-OCIS-storage.md | 5 +--- .../features/apiGraph/addUserToGroup.feature | 6 ++--- .../features/apiGraph/createGroup.feature | 27 +------------------ .../features/apiGraph/deleteGroup.feature | 2 +- .../features/apiGraph/editGroup.feature | 14 +--------- .../features/apiGraph/getGroup.feature | 8 +++--- .../apiGraph/removeUserFromGroup.feature | 2 +- 7 files changed, 12 insertions(+), 52 deletions(-) diff --git a/tests/acceptance/expected-failures-localAPI-on-OCIS-storage.md b/tests/acceptance/expected-failures-localAPI-on-OCIS-storage.md index 3142ba87b2a..08f3ff3ab41 100644 --- a/tests/acceptance/expected-failures-localAPI-on-OCIS-storage.md +++ b/tests/acceptance/expected-failures-localAPI-on-OCIS-storage.md @@ -44,7 +44,7 @@ The expected failures in this file are from features in the owncloud/ocis repo. - [apiSpacesShares/copySpaces.feature:793](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/apiSpacesShares/copySpaces.feature#L793) ### [Creating group with empty name returns status code 200](https://github.com/owncloud/ocis/issues/5050) -- [apiGraph/createGroup.feature:60](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/apiGraph/createGroup.feature#L60) +- [apiGraph/createGroup.feature:46](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/apiGraph/createGroup.feature#L46) ### [Settings service user can list other peoples assignments](https://github.com/owncloud/ocis/issues/5032) - [apiAccountsHashDifficulty/assignRole.feature:27](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/apiAccountsHashDifficulty/assignRole.feature#L27) @@ -69,9 +69,6 @@ The expected failures in this file are from features in the owncloud/ocis repo. - [apiGraph/editGroup.feature:24](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/apiGraph/editGroup.feature#L24) - [apiGraph/editGroup.feature:25](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/apiGraph/editGroup.feature#L25) - [apiGraph/editGroup.feature:40](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/apiGraph/editGroup.feature#L40) -- [apiGraph/editGroup.feature:53](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/apiGraph/editGroup.feature#L53) -- [apiGraph/editGroup.feature:54](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/apiGraph/editGroup.feature#L54) -- [apiGraph/editGroup.feature:55](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/apiGraph/editGroup.feature#L55) #### [CORS headers are not identical with oC10 headers](https://github.com/owncloud/ocis/issues/5195) - [apiCors/cors.feature:25](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/apiCors/cors.feature#L25) diff --git a/tests/acceptance/features/apiGraph/addUserToGroup.feature b/tests/acceptance/features/apiGraph/addUserToGroup.feature index 976d43f50c4..0cb0314a680 100644 --- a/tests/acceptance/features/apiGraph/addUserToGroup.feature +++ b/tests/acceptance/features/apiGraph/addUserToGroup.feature @@ -120,7 +120,7 @@ Feature: add users to group | Alice | var/../etc | - Scenario Outline: normal user tries to add himself to a group + Scenario Outline: user other than the admin tries to add himself to a group Given the administrator has given "Alice" the role "" using the settings api And group "groupA" has been created When user "Alice" tries to add himself to group "groupA" using the Graph API @@ -133,7 +133,7 @@ Feature: add users to group | Guest | - Scenario Outline: normal user tries to add other user to a group + Scenario Outline: other than the admin tries to add other user to a group Given user "Brian" has been created with default attributes and without skeleton files And the administrator has given "Brian" the role "" using the settings api And group "groupA" has been created @@ -152,7 +152,7 @@ Feature: add users to group Then the HTTP status code should be "404" - Scenario Outline: normal user tries to add user to a non-existing group + Scenario Outline: other than the admin tries to add user to a nonexistent group Given the administrator has given "Alice" the role "" using the settings api When the administrator tries to add user "Alice" to a nonexistent group using the Graph API Then the HTTP status code should be "404" diff --git a/tests/acceptance/features/apiGraph/createGroup.feature b/tests/acceptance/features/apiGraph/createGroup.feature index 08058f97d87..2102592dc9d 100644 --- a/tests/acceptance/features/apiGraph/createGroup.feature +++ b/tests/acceptance/features/apiGraph/createGroup.feature @@ -30,7 +30,7 @@ Feature: create group And group "mygroup" should exist - Scenario Outline: normal user tries to create a group + Scenario Outline: user other than the admin can't create a group Given user "Brian" has been created with default attributes and without skeleton files And the administrator has given "Brian" the role "" using the settings api When user "Brian" tries to create a group "mygroup" using the Graph API @@ -42,32 +42,7 @@ Feature: create group | User | | Guest | - - Scenario Outline: normal user tries to create a group that already exists - Given group "mygroup" has been created - And user "Brian" has been created with default attributes and without skeleton files - And the administrator has given "Brian" the role "" using the settings api - When user "Brian" tries to create a group "mygroup" using the Graph API - And the HTTP status code should be "401" - And group "mygroup" should exist - Examples: - | userRole | - | Space Admin | - | User | - | Guest | - @issue-5050 Scenario: admin user tries to create a group that is the empty string When user "Alice" tries to create a group "" using the Graph API Then the HTTP status code should be "400" - - - Scenario Outline: normal user tries to create a group that is the empty string - Given the administrator has given "Alice" the role "" using the settings api - When user "Alice" tries to create a group "" using the Graph API - Then the HTTP status code should be "401" - Examples: - | userRole | - | Space Admin | - | User | - | Guest | diff --git a/tests/acceptance/features/apiGraph/deleteGroup.feature b/tests/acceptance/features/apiGraph/deleteGroup.feature index 22d105e411f..e5a5c799187 100644 --- a/tests/acceptance/features/apiGraph/deleteGroup.feature +++ b/tests/acceptance/features/apiGraph/deleteGroup.feature @@ -51,7 +51,7 @@ Feature: delete groups | 50%2Fix | %2F literal looks like an escaped slash | - Scenario Outline: normal user tries to delete a group + Scenario Outline: user other than the admin can't delete a group Given user "Brian" has been created with default attributes and without skeleton files And the administrator has given "Brian" the role "" using the settings api And group "new-group" has been created diff --git a/tests/acceptance/features/apiGraph/editGroup.feature b/tests/acceptance/features/apiGraph/editGroup.feature index fda831a6c9b..94fe319f854 100644 --- a/tests/acceptance/features/apiGraph/editGroup.feature +++ b/tests/acceptance/features/apiGraph/editGroup.feature @@ -25,7 +25,7 @@ Feature: edit group name | grp1 | 50%pass | - Scenario Outline: normal user tries to rename a group + Scenario Outline: user other than the admin can't rename a group Given the administrator has given "Alice" the role "" using the settings api And group "grp1" has been created When user "Alice" tries to rename group "grp1" to "grp101" using the Graph API @@ -41,15 +41,3 @@ Feature: edit group name When user "Alice" tries to rename non-existent group to "grp1" using the Graph API Then the HTTP status code should be "404" And group "grp1" should not exist - - - Scenario Outline: normal user tries to rename non-existent group - Given the administrator has given "Alice" the role "" using the settings api - When user "Alice" tries to rename non-existent group to "grp1" using the Graph API - Then the HTTP status code should be "404" - And group "grp1" should not exist - Examples: - | role | - | Space Admin | - | User | - | Guest | diff --git a/tests/acceptance/features/apiGraph/getGroup.feature b/tests/acceptance/features/apiGraph/getGroup.feature index bee018d72ee..eee39d949fe 100644 --- a/tests/acceptance/features/apiGraph/getGroup.feature +++ b/tests/acceptance/features/apiGraph/getGroup.feature @@ -21,7 +21,7 @@ Feature: get groups and their members | h2o-lover | - Scenario Outline: normal user cannot get the groups list + Scenario Outline: user other than the admin shouldn't get the groups list Given user "Brian" has been created with default attributes and without skeleton files And the administrator has given "Brian" the role "" using the settings api And group "tea-lover" has been created @@ -52,7 +52,7 @@ Feature: get groups and their members | Carol | - Scenario Outline: normal user tries to get users of a group + Scenario Outline: user other than the admin shouldn't get users of a group Given user "Brian" has been created with default attributes and without skeleton files And the administrator has given "Brian" the role "" using the settings api And group "tea-lover" has been created @@ -87,7 +87,7 @@ Feature: get groups and their members | Carol King | %uuid_v4% | carol@example.org | Carol | - Scenario Outline: normal user gets all groups along with their members information + Scenario Outline: user other than the admin shouldn't gets all groups along with their members information Given user "Brian" has been created with default attributes and without skeleton files And the administrator has given "Brian" the role "" using the settings api And group "tea-lover" has been created @@ -116,7 +116,7 @@ Feature: get groups and their members | Brian Murphy | %uuid_v4% | brian@example.org | Brian | @issue-5604 - Scenario Outline: normal user gets a group along with their members information + Scenario Outline: user other than the admin gets a group along with their members information Given user "Brian" has been created with default attributes and without skeleton files And the administrator has given "Brian" the role "" using the settings api And group "tea-lover" has been created diff --git a/tests/acceptance/features/apiGraph/removeUserFromGroup.feature b/tests/acceptance/features/apiGraph/removeUserFromGroup.feature index 5e7d42bbbaa..c623460dd40 100644 --- a/tests/acceptance/features/apiGraph/removeUserFromGroup.feature +++ b/tests/acceptance/features/apiGraph/removeUserFromGroup.feature @@ -157,7 +157,7 @@ Feature: remove a user from a group Then the HTTP status code should be "404" - Scenario Outline: normal user tries to remove a user in their group + Scenario Outline: user other than the admin can't remove a user from their group Given user "Brian" has been created with default attributes and without skeleton files And the administrator has given "Brian" the role "" using the settings api And group "grp1" has been created