From 09f07a45224a3168d089261a6bdd275fb6f5acbb Mon Sep 17 00:00:00 2001 From: Dipak Acharya Date: Wed, 18 Nov 2020 09:35:42 +0545 Subject: [PATCH] Update tags on group tests --- .../addToGroup.feature | 4 +- .../deleteGroup.feature | 2 +- .../getGroups.feature | 42 +++++++++---------- .../getUserGroups.feature | 2 +- .../addToGroup.feature | 6 +-- .../deleteGroup.feature | 4 +- .../apiProvisioningGroups-v2/getGroup.feature | 2 +- .../getGroups.feature | 2 +- .../getUserGroups.feature | 4 +- .../removeFromGroup.feature | 6 +-- 10 files changed, 37 insertions(+), 37 deletions(-) diff --git a/tests/acceptance/features/apiProvisioningGroups-v1/addToGroup.feature b/tests/acceptance/features/apiProvisioningGroups-v1/addToGroup.feature index d8e34e36ed5d..5fb1a0a63cb2 100644 --- a/tests/acceptance/features/apiProvisioningGroups-v1/addToGroup.feature +++ b/tests/acceptance/features/apiProvisioningGroups-v1/addToGroup.feature @@ -41,7 +41,7 @@ Feature: add users to group | admin:Pokhara@Nepal | Colon and @ | # once the issue is fixed merge with scenario above - @skipOnLDAP @toImplementOnOCIS + @skipOnLDAP @toImplementOnOCIS @issue-product-284 Scenario Outline: adding a user to a group Given user "brand-new-user" has been created with default attributes and skeleton files And group "" has been created @@ -157,7 +157,7 @@ Feature: add users to group And user "brand-new-user" should not belong to group "brand-new-group" # merge this with scenario on line 62 once the issue is fixed - @issue-31015 @skipOnLDAP @toImplementOnOCIS + @issue-31015 @skipOnLDAP @toImplementOnOCIS @issue-product-284 Scenario Outline: adding a user to a group that has a forward-slash in the group name Given user "brand-new-user" has been created with default attributes and skeleton files And the administrator sends a group creation request for group "" using the provisioning API diff --git a/tests/acceptance/features/apiProvisioningGroups-v1/deleteGroup.feature b/tests/acceptance/features/apiProvisioningGroups-v1/deleteGroup.feature index a89e863d60ce..95f52a349cbd 100644 --- a/tests/acceptance/features/apiProvisioningGroups-v1/deleteGroup.feature +++ b/tests/acceptance/features/apiProvisioningGroups-v1/deleteGroup.feature @@ -40,7 +40,7 @@ Feature: delete groups | Mgmt\Middle | Backslash | | 😁 😂 | emoji | - @notToImplementOnOCIS + @toImplementOnOCIS Scenario Outline: admin deletes a group Given group "" has been created When the administrator deletes group "" using the provisioning API diff --git a/tests/acceptance/features/apiProvisioningGroups-v1/getGroups.feature b/tests/acceptance/features/apiProvisioningGroups-v1/getGroups.feature index e5cf78128e6c..e6ce189f48f8 100644 --- a/tests/acceptance/features/apiProvisioningGroups-v1/getGroups.feature +++ b/tests/acceptance/features/apiProvisioningGroups-v1/getGroups.feature @@ -19,7 +19,7 @@ Feature: get groups | brand-new-group | | 0 | - @skipOnLdap @issue-ldap-499 @toImplementOnOCIS + @skipOnLdap @issue-ldap-499 @notToImplementOnOCIS Scenario: admin gets all the groups, including groups with mixed case Given group "case-sensitive-group" has been created And group "Case-Sensitive-Group" has been created @@ -50,23 +50,23 @@ Feature: get groups | users | | sysusers | | sailing-lovers | -# -# @smokeTest @skipOnOcV10 -# Scenario: admin gets all the groups, including groups with mixed case -# Given group "case-sensitive-group" has been created -# And group "Case-Sensitive-Group" has been created -# And group "CASE-SENSITIVE-GROUP" has been created -# When the administrator gets all the groups using the provisioning API -# Then the groups returned by the API should be -# | case-sensitive-group | -# | Case-Sensitive-Group | -# | CASE-SENSITIVE-GROUP | -# | philosophy-haters | -# | physics-lovers | -# | polonium-lovers | -# | quantum-lovers | -# | radium-lovers | -# | violin-haters | -# | users | -# | sysusers | -# | sailing-lovers | \ No newline at end of file + + @smokeTest @skipOnOcV10 @toImplementOnOCIS + Scenario: admin gets all the groups, including groups with mixed case + Given group "case-sensitive-group" has been created + And group "Case-Sensitive-Group" has been created + And group "CASE-SENSITIVE-GROUP" has been created + When the administrator gets all the groups using the provisioning API + Then the groups returned by the API should be + | case-sensitive-group | + | Case-Sensitive-Group | + | CASE-SENSITIVE-GROUP | + | philosophy-haters | + | physics-lovers | + | polonium-lovers | + | quantum-lovers | + | radium-lovers | + | violin-haters | + | users | + | sysusers | + | sailing-lovers | \ No newline at end of file diff --git a/tests/acceptance/features/apiProvisioningGroups-v1/getUserGroups.feature b/tests/acceptance/features/apiProvisioningGroups-v1/getUserGroups.feature index d23ca4218423..d84f178952ac 100644 --- a/tests/acceptance/features/apiProvisioningGroups-v1/getUserGroups.feature +++ b/tests/acceptance/features/apiProvisioningGroups-v1/getUserGroups.feature @@ -118,7 +118,7 @@ Feature: get user groups And the OCS status code should be "100" And the HTTP status code should be "200" - @notToImplementOnOCIS @skipOnOcV10 + @skipOnOcV10 Scenario: admin gets groups of an user who is not in any groups Given user "brand-new-user" has been created with default attributes and skeleton files And group "unused-group" has been created diff --git a/tests/acceptance/features/apiProvisioningGroups-v2/addToGroup.feature b/tests/acceptance/features/apiProvisioningGroups-v2/addToGroup.feature index d42f09890b14..cb8602f4c126 100644 --- a/tests/acceptance/features/apiProvisioningGroups-v2/addToGroup.feature +++ b/tests/acceptance/features/apiProvisioningGroups-v2/addToGroup.feature @@ -41,7 +41,7 @@ Feature: add users to group | admin:Pokhara@Nepal | Colon and @ | # once the issue is fixed merge with scenario above - @skipOnLDAP @toImplementOnOCIS + @skipOnLDAP @toImplementOnOCIS @issue-product-284 Scenario Outline: adding a user to a group Given user "brand-new-user" has been created with default attributes and skeleton files And group "" has been created @@ -72,7 +72,7 @@ Feature: add users to group | priv/subadmins/1 | Subadmins mentioned not at the end | - @skipOnLDAP @toImplementOnOCIS + @skipOnLDAP @toImplementOnOCIS @issue-product-283 Scenario Outline: adding a user to a group using mixes of upper and lower case in user and group names Given user "mixed-case-user" has been created with default attributes and skeleton files And group "" has been created @@ -152,7 +152,7 @@ Feature: add users to group And user "brand-new-user" should not belong to group "brand-new-group" # merge this with scenario on line 62 once the issue is fixed - @issue-31015 @skipOnLDAP @toImplementOnOCIS + @issue-31015 @skipOnLDAP @toImplementOnOCIS @issue-product-284 Scenario Outline: adding a user to a group that has a forward-slash in the group name Given user "brand-new-user" has been created with default attributes and skeleton files And the administrator sends a group creation request for group "" using the provisioning API diff --git a/tests/acceptance/features/apiProvisioningGroups-v2/deleteGroup.feature b/tests/acceptance/features/apiProvisioningGroups-v2/deleteGroup.feature index 5adc30b5f460..ffab2e108a27 100644 --- a/tests/acceptance/features/apiProvisioningGroups-v2/deleteGroup.feature +++ b/tests/acceptance/features/apiProvisioningGroups-v2/deleteGroup.feature @@ -56,7 +56,7 @@ Feature: delete groups | 50%2Fix | %2F literal looks like an escaped slash | | staff?group | Question mark | - @toImplementOnOCIS + @toImplementOnOCIS @issue-product-283 Scenario Outline: group names are case-sensitive, the correct group is deleted Given group "" has been created And group "" has been created @@ -107,7 +107,7 @@ Feature: delete groups And the HTTP status code should be "401" And group "brand-new-group" should exist - @issue-31015 @skipOnOcV10 @toImplementOnOCIS + @issue-31015 @skipOnOcV10 @toImplementOnOCIS @issue-product-284 Scenario Outline: admin deletes a group that has a forward-slash in the group name Given group "" has been created When the administrator deletes group "" using the provisioning API diff --git a/tests/acceptance/features/apiProvisioningGroups-v2/getGroup.feature b/tests/acceptance/features/apiProvisioningGroups-v2/getGroup.feature index de940a82fc56..34548c497503 100644 --- a/tests/acceptance/features/apiProvisioningGroups-v2/getGroup.feature +++ b/tests/acceptance/features/apiProvisioningGroups-v2/getGroup.feature @@ -36,7 +36,7 @@ Feature: get group Then the OCS status code should be "404" And the HTTP status code should be "404" - @toImplementOnOCIS + @toImplementOnOCIS @issue-product-283 Scenario Outline: admin tries to get users in a group but using wrong case of the group name Given group "" has been created When the administrator gets all the members of group "" using the provisioning API diff --git a/tests/acceptance/features/apiProvisioningGroups-v2/getGroups.feature b/tests/acceptance/features/apiProvisioningGroups-v2/getGroups.feature index 27116d23a1d9..53b2be87d34a 100644 --- a/tests/acceptance/features/apiProvisioningGroups-v2/getGroups.feature +++ b/tests/acceptance/features/apiProvisioningGroups-v2/getGroups.feature @@ -51,7 +51,7 @@ Feature: get groups | sysusers | | sailing-lovers | - @smokeTest @skipOnOcV10 @toImplementOnOCIS + @smokeTest @skipOnOcV10 @toImplementOnOCIS @issue-product-283 Scenario: admin gets all the groups, including groups with mixed case Given group "case-sensitive-group" has been created And group "Case-Sensitive-Group" has been created diff --git a/tests/acceptance/features/apiProvisioningGroups-v2/getUserGroups.feature b/tests/acceptance/features/apiProvisioningGroups-v2/getUserGroups.feature index ebf259b0df84..effa5f0f832c 100644 --- a/tests/acceptance/features/apiProvisioningGroups-v2/getUserGroups.feature +++ b/tests/acceptance/features/apiProvisioningGroups-v2/getUserGroups.feature @@ -7,7 +7,7 @@ Feature: get user groups Background: Given using OCS API version "2" - @smokeTest @toImplementOnOCIS + @smokeTest @notToImplementOnOCIS Scenario: admin gets groups of an user Given user "brand-new-user" has been created with default attributes and skeleton files And group "unused-group" has been created @@ -119,7 +119,7 @@ Feature: get user groups And the OCS status code should be "200" And the HTTP status code should be "200" - @notToImplementOnOCIS @skipOnOcV10 + @skipOnOcV10 Scenario: admin gets groups of an user who is not in any groups Given user "brand-new-user" has been created with default attributes and skeleton files And group "unused-group" has been created diff --git a/tests/acceptance/features/apiProvisioningGroups-v2/removeFromGroup.feature b/tests/acceptance/features/apiProvisioningGroups-v2/removeFromGroup.feature index 9243e19c0456..78f5728074d7 100644 --- a/tests/acceptance/features/apiProvisioningGroups-v2/removeFromGroup.feature +++ b/tests/acceptance/features/apiProvisioningGroups-v2/removeFromGroup.feature @@ -44,7 +44,7 @@ Feature: remove a user from a group | Mgmt\Middle | Backslash | | 😁 😂 | emoji | - @toImplementOnOCIS + @toImplementOnOCIS @issue-product-284 Scenario Outline: admin removes a user from a group Given user "brand-new-user" has been created with default attributes and skeleton files And group "" has been created @@ -77,7 +77,7 @@ Feature: remove a user from a group | Mgmt//NSW/Sydney | Multiple slash | | priv/subadmins/1 | Subadmins mentioned not at the end | - @toImplementOnOCIS + @toImplementOnOCIS @issue-product-283 Scenario Outline: remove a user from a group using mixes of upper and lower case in user and group names Given user "brand-new-user" has been created with default attributes and skeleton files And group "" has been created @@ -149,7 +149,7 @@ Feature: remove a user from a group And user "another-new-user" should belong to group "brand-new-group" # merge this with scenario on line 62 once the issue is fixed - @issue-31015 @skipOnOcV10 @toImplementOnOCIS + @issue-31015 @skipOnOcV10 @toImplementOnOCIS @issue-product-284 Scenario Outline: admin removes a user from a group that has a forward-slash in the group name Given user "brand-new-user" has been created with default attributes and skeleton files And group "" has been created