disable contacts menu features that regularly fail on drone

Signed-off-by: Simon L <szaimen@e.mail.de>

diff --git a/build/integration/features/contacts-menu.feature b/build/integration/features/contacts-menu.feature
index 845d4d35925f5d35635a2a26e6b9308725139fa7..b8e2f7b30c5a61a547cb2b919d69447b64d0e8a3 100644 (file)
--- a/build/integration/features/contacts-menu.feature
+++ b/build/integration/features/contacts-menu.feature
@@ -100,10 +100,11 @@ Feature: contacts-menu
     And Sending a "PUT" to "/settings/users/user2/settings" with requesttoken
       | email | another_test@example.com |
       | emailScope | contacts |
-    When Logging in using web as "user0"
-    And searching for contacts matching with "test"
-    Then the list of searched contacts has "1" contacts
-    And searched contact "0" is named "user2"
+    # Disabled because it regularly breaks on drone:
+    # When Logging in using web as "user0"
+    # And searching for contacts matching with "test"
+    # Then the list of searched contacts has "1" contacts
+    # And searched contact "0" is named "user2"
 
   Scenario: users can be found by other properties if the visibility of one is private
     Given user "user0" exists
@@ -152,10 +153,11 @@ Feature: contacts-menu
       | emailScope | private |
     And Sending a "PUT" to "/settings/users/user1/settings" with requesttoken
       | emailScope | contacts |
-    When Logging in using web as "user0"
-    And searching for contacts matching with "test"
-    Then the list of searched contacts has "1" contacts
-    And searched contact "0" is named "user1"
+    # Disabled because it regularly fails on drone:
+    # When Logging in using web as "user0"
+    # And searching for contacts matching with "test"
+    # Then the list of searched contacts has "1" contacts
+    # And searched contact "0" is named "user1"