Update tags on group tests

owncloud · Nov 18, 2020 · 09f07a4 · 09f07a4
1 parent 3be9a87
commit 09f07a4
Show file tree

Hide file tree

Showing 10 changed files with 37 additions and 37 deletions.
diff --git 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 "<group_id>" 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 "<group_id>" using the provisioning API

diff --git 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 "<group_id>" has been created
     When the administrator deletes group "<group_id>" using the provisioning API

diff --git 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    |
+
+  @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    |
diff --git 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
@@ -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 "<group_id>" 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 "<group_id1>" 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 "<group_id>" using the provisioning API

diff --git 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 "<group_id1>" has been created
     And group "<group_id2>" 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 "<group_id>" has been created
     When the administrator deletes group "<group_id>" using the provisioning API

diff --git 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 "<group_id1>" has been created
     When the administrator gets all the members of group "<group_id2>" using the provisioning API

diff --git 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
@@ -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
@@ -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 "<group_id>" 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 "<group_id1>" 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 "<group_id>" has been created