upstream/nextcloud
1
0
Fork 0
mirror of https://github.com/nextcloud/server.git synced 2026-06-09 08:44:07 -04:00
Code Issues Projects Releases Packages Wiki Activity Actions 11

Merge pull request #38019 from nextcloud/enh/noid/disable-contactsmenu-tests

Browse source 
disable contacts menu features that regularly fail on drone
This commit is contained in:
Simon L 2023-05-02 13:42:10 +02:00 committed by GitHub
commit 40b6ce86f8
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 10 additions and 8 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

18
build/integration/features/contacts-menu.feature
View file

@ -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"