Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

disable contacts menu features that regularly fail on drone #38337

Merged
merged 1 commit into from
May 17, 2023
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 10 additions & 6 deletions build/integration/features/contacts-menu.feature
Original file line number Diff line number Diff line change
Expand Up @@ -85,8 +85,9 @@ Feature: contacts-menu
| displaynameScope | 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 "Another test name"
# Disabled because it regularly fails on drone:
# Then the list of searched contacts has "1" contacts
# And searched contact "0" is named "Another test name"

Scenario: users can not be found by email if visibility is private
Given user "user0" exists
Expand All @@ -100,7 +101,7 @@ Feature: contacts-menu
And Sending a "PUT" to "/settings/users/user2/settings" with requesttoken
| email | another_test@example.com |
| emailScope | contacts |
# Disabled because it regularly breaks on drone:
# 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
Expand All @@ -125,7 +126,8 @@ Feature: contacts-menu
When Logging in using web as "user0"
And searching for contacts matching with "test"
Then the list of searched contacts has "2" contacts
And searched contact "0" is named ""
# Disabled because it regularly fails on drone:
# And searched contact "0" is named ""
And searched contact "1" is named "Test name"


Expand Down Expand Up @@ -173,7 +175,8 @@ Feature: contacts-menu
| value | Test name |
When Logging in using web as "user0"
And searching for contacts matching with "test"
Then the list of searched contacts has "0" contacts
# Disabled because it regularly fails on drone:
# Then the list of searched contacts has "0" contacts

Scenario: users can not be searched by email if visibility is private even if updated with provisioning
Given user "user0" exists
Expand All @@ -187,4 +190,5 @@ Feature: contacts-menu
| value | test@example.com |
When Logging in using web as "user0"
And searching for contacts matching with "test"
Then the list of searched contacts has "0" contacts
# Disabled because it regularly fails on drone:
# Then the list of searched contacts has "0" contacts