From 45444a08580933744d26cb774f922ab34b1764fd Mon Sep 17 00:00:00 2001 From: Roshan Lamichhane Date: Tue, 24 Jan 2023 11:14:24 +0545 Subject: [PATCH] Removed @toImplementOnOCIS tags from feature files --- .../features/apiProvisioningGroups-v1/addGroup.feature | 6 +++--- .../features/apiProvisioningGroups-v1/addToGroup.feature | 6 +++--- .../features/apiProvisioningGroups-v1/deleteGroup.feature | 6 +++--- .../features/apiProvisioningGroups-v1/getGroup.feature | 2 +- .../apiProvisioningGroups-v1/removeFromGroup.feature | 6 +++--- .../features/apiProvisioningGroups-v2/addGroup.feature | 6 +++--- .../features/apiProvisioningGroups-v2/addToGroup.feature | 6 +++--- .../features/apiProvisioningGroups-v2/deleteGroup.feature | 6 +++--- .../features/apiProvisioningGroups-v2/getGroup.feature | 2 +- .../apiProvisioningGroups-v2/removeFromGroup.feature | 6 +++--- 10 files changed, 26 insertions(+), 26 deletions(-) diff --git a/tests/acceptance/features/apiProvisioningGroups-v1/addGroup.feature b/tests/acceptance/features/apiProvisioningGroups-v1/addGroup.feature index 69f824f3a341..47cd954422d2 100644 --- a/tests/acceptance/features/apiProvisioningGroups-v1/addGroup.feature +++ b/tests/acceptance/features/apiProvisioningGroups-v1/addGroup.feature @@ -57,7 +57,7 @@ Feature: add groups | [group1] | | group [ 2 ] | - @toImplementOnOCIS @issue-product-284 + @issue-product-284 Scenario: admin creates a group with % and # in name When the administrator sends a group creation request for the following groups using the provisioning API | groupname | comment | @@ -78,7 +78,7 @@ Feature: add groups | 50%2Eagle | | staff?group | - @toImplementOnOCIS + Scenario: group names are case-sensitive, multiple groups can exist with different upper and lower case names When the administrator sends a group creation request for the following groups using the provisioning API | groupname | @@ -104,7 +104,7 @@ Feature: add groups | case-sensitive-group2 | | Case-Sensitive-Group3 | - @issue-31015 @skipOnOcV10 @toImplementOnOCIS @issue-product-284 + @issue-31015 @skipOnOcV10 @issue-product-284 Scenario: admin creates a group with a forward-slash in the group name When the administrator sends a group creation request for the following groups using the provisioning API | groupname | comment | diff --git a/tests/acceptance/features/apiProvisioningGroups-v1/addToGroup.feature b/tests/acceptance/features/apiProvisioningGroups-v1/addToGroup.feature index 702631efe7ad..bf6364a3736b 100644 --- a/tests/acceptance/features/apiProvisioningGroups-v1/addToGroup.feature +++ b/tests/acceptance/features/apiProvisioningGroups-v1/addToGroup.feature @@ -54,7 +54,7 @@ Feature: add users to group And the HTTP status code of responses on all endpoints should be "200" # once the issue is fixed merge with scenario above - @skipOnLDAP @toImplementOnOCIS @issue-product-284 + @skipOnLDAP @issue-product-284 Scenario: adding a user to a group with % and # in its name Given user "brand-new-user" has been created with default attributes and without skeleton files And these groups have been created: @@ -103,7 +103,7 @@ Feature: add users to group | Mgmt//NSW/Sydney | | priv/subadmins/1 | - @skipOnLDAP @toImplementOnOCIS + @skipOnLDAP Scenario: 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 without skeleton files And these groups have been created: @@ -216,7 +216,7 @@ Feature: add users to group And user "brand-new-user" should belong to group "brand-new-group" # merge this with scenario on line 62 once the issue is fixed - @issue-31015 @skipOnLDAP @toImplementOnOCIS @issue-product-284 + @issue-31015 @skipOnLDAP @issue-product-284 Scenario Outline: adding a user to a group that has a forward-slash and dot in the group name Given user "brand-new-user" has been created with default attributes and without 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 861084817342..609d24c13f61 100644 --- a/tests/acceptance/features/apiProvisioningGroups-v1/deleteGroup.feature +++ b/tests/acceptance/features/apiProvisioningGroups-v1/deleteGroup.feature @@ -41,7 +41,7 @@ Feature: delete groups | Mgmt\Middle | Backslash | | 😁 😂 | emoji | - @toImplementOnOCIS + Scenario Outline: admin deletes a group Given group "" has been created When the administrator deletes group "" using the provisioning API @@ -57,7 +57,7 @@ Feature: delete groups | 50%2Fix | %2F literal looks like an escaped slash | | staff?group | Question mark | - @toImplementOnOCIS + 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 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-v1/getGroup.feature b/tests/acceptance/features/apiProvisioningGroups-v1/getGroup.feature index ffda9e60e6af..961f7eeb6e84 100644 --- a/tests/acceptance/features/apiProvisioningGroups-v1/getGroup.feature +++ b/tests/acceptance/features/apiProvisioningGroups-v1/getGroup.feature @@ -38,7 +38,7 @@ Feature: get group Then the OCS status code should be "998" And the HTTP status code should be "200" - @toImplementOnOCIS + 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-v1/removeFromGroup.feature b/tests/acceptance/features/apiProvisioningGroups-v1/removeFromGroup.feature index e735b9a0d7c0..569aa5ab91f5 100644 --- a/tests/acceptance/features/apiProvisioningGroups-v1/removeFromGroup.feature +++ b/tests/acceptance/features/apiProvisioningGroups-v1/removeFromGroup.feature @@ -91,7 +91,7 @@ Feature: remove a user from a group | brand-new-user | Mgmt\Middle | | brand-new-user | 😁 😂 | - @toImplementOnOCIS + Scenario: admin removes a user from a group with % and # in their names Given user "brand-new-user" has been created with default attributes and without skeleton files And these groups have been created: @@ -155,7 +155,7 @@ Feature: remove a user from a group | brand-new-user | Mgmt//NSW/Sydney | | brand-new-user | priv/subadmins/1 | - @toImplementOnOCIS + 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 without skeleton files And group "" has been created @@ -229,7 +229,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 Scenario Outline: admin removes a user from a group that has a forward-slash and dot in the group name Given user "brand-new-user" has been created with default attributes and without skeleton files And group "" has been created diff --git a/tests/acceptance/features/apiProvisioningGroups-v2/addGroup.feature b/tests/acceptance/features/apiProvisioningGroups-v2/addGroup.feature index df0109291c89..9a5c9a3fdb74 100644 --- a/tests/acceptance/features/apiProvisioningGroups-v2/addGroup.feature +++ b/tests/acceptance/features/apiProvisioningGroups-v2/addGroup.feature @@ -53,7 +53,7 @@ Feature: add groups | Mgmt\Middle | | 😅 😆 | - @toImplementOnOCIS @issue-product-284 + @issue-product-284 Scenario: admin creates a group with % in name When the administrator sends a group creation request for the following groups using the provisioning API | groupname | comment | @@ -74,7 +74,7 @@ Feature: add groups | 50%2Eagle | | staff?group | - @toImplementOnOCIS + Scenario: group names are case-sensitive, multiple groups can exist with different upper and lower case names When the administrator sends a group creation request for the following groups using the provisioning API | groupname | @@ -100,7 +100,7 @@ Feature: add groups | case-sensitive-group2 | | Case-Sensitive-Group3 | - @issue-31015 @skipOnOcV10 @toImplementOnOCIS + @issue-31015 @skipOnOcV10 Scenario: admin creates a group with a forward-slash in the group name When the administrator sends a group creation request for the following groups using the provisioning API | groupname | comment | diff --git a/tests/acceptance/features/apiProvisioningGroups-v2/addToGroup.feature b/tests/acceptance/features/apiProvisioningGroups-v2/addToGroup.feature index 4d8426f0262b..2b98e4892903 100644 --- a/tests/acceptance/features/apiProvisioningGroups-v2/addToGroup.feature +++ b/tests/acceptance/features/apiProvisioningGroups-v2/addToGroup.feature @@ -54,7 +54,7 @@ Feature: add users to group And the HTTP status code of responses on all endpoints should be "200" # once the issue is fixed merge with scenario above - @skipOnLDAP @toImplementOnOCIS @issue-product-284 + @skipOnLDAP @issue-product-284 Scenario: adding a user to a group with % and # in its name Given user "brand-new-user" has been created with default attributes and without skeleton files And these groups have been created: @@ -94,7 +94,7 @@ Feature: add users to group Then the OCS status code of responses on all endpoints should be "200" And the HTTP status code of responses on all endpoints should be "200" - @skipOnLDAP @toImplementOnOCIS @issue-product-283 + @skipOnLDAP @issue-product-283 Scenario: 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 without skeleton files And these groups have been created: @@ -207,7 +207,7 @@ Feature: add users to group And user "brand-new-user" should belong to group "brand-new-group" # merge this with scenario on line 62 once the issue is fixed - @issue-31015 @skipOnLDAP @toImplementOnOCIS @issue-product-284 + @issue-31015 @skipOnLDAP @issue-product-284 Scenario Outline: adding a user to a group that has a forward-slash and dot in the group name Given user "brand-new-user" has been created with default attributes and without 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 18082a0a35c1..69223e81c890 100644 --- a/tests/acceptance/features/apiProvisioningGroups-v2/deleteGroup.feature +++ b/tests/acceptance/features/apiProvisioningGroups-v2/deleteGroup.feature @@ -41,7 +41,7 @@ Feature: delete groups | Mgmt\Middle | Backslash | | 😁 😂 | emoji | - @toImplementOnOCIS + Scenario Outline: admin deletes a group Given group "" has been created When the administrator deletes group "" using the provisioning API @@ -57,7 +57,7 @@ Feature: delete groups | 50%2Fix | %2F literal looks like an escaped slash | | staff?group | Question mark | - @toImplementOnOCIS @issue-product-283 + @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-product-284 + @issue-31015 @skipOnOcV10 @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 c2fdffeb7bd8..6ba2575f0ad2 100644 --- a/tests/acceptance/features/apiProvisioningGroups-v2/getGroup.feature +++ b/tests/acceptance/features/apiProvisioningGroups-v2/getGroup.feature @@ -38,7 +38,7 @@ Feature: get group Then the OCS status code should be "404" And the HTTP status code should be "404" - @toImplementOnOCIS @issue-product-283 + @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/removeFromGroup.feature b/tests/acceptance/features/apiProvisioningGroups-v2/removeFromGroup.feature index d499f6e8faaf..477ec05cc512 100644 --- a/tests/acceptance/features/apiProvisioningGroups-v2/removeFromGroup.feature +++ b/tests/acceptance/features/apiProvisioningGroups-v2/removeFromGroup.feature @@ -91,7 +91,7 @@ Feature: remove a user from a group | brand-new-user | Mgmt\Middle | | brand-new-user | 😁 😂 | - @toImplementOnOCIS @issue-product-284 + @issue-product-284 Scenario: admin removes a user from a group with % and # in their names Given user "brand-new-user" has been created with default attributes and without skeleton files And these groups have been created: @@ -155,7 +155,7 @@ Feature: remove a user from a group | brand-new-user | Mgmt//NSW/Sydney | | brand-new-user | priv/subadmins/1 | - @toImplementOnOCIS @issue-product-283 + @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 without skeleton files And group "" has been created @@ -229,7 +229,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-product-284 + @issue-31015 @skipOnOcV10 @issue-product-284 Scenario Outline: admin removes a user from a group that has a forward-slash and dot in the group name Given user "brand-new-user" has been created with default attributes and without skeleton files And group "" has been created