Skip autocompletion tests on LDAP - they rely on a complex user and g… #31750
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
…roup list
Signed-off-by: Phil Davis [email protected]
Description
Skip sharing auto-complete test scenarios on LDAP (older scenarios were already skipped).
Because they rely on having a more complex mix of users and groups than are set up in the LDAP tests at the moment.
Related Issue
#31747
Motivation and Context
New sharing autocomplete tests were added to better check the autocomplete matches under a mix of user ids, group ids and user display names. PR #31714 and backport #31729
Those tests require a suitable mix of users, display names and groups to exist. But
user_ldap
acceptance tests currently have a fixed list of users and groups.So skip these scenarios on LDAP test runs.
We can add some more simple scenarios to the LDAP tests to check the autocomplete behavior there.
How Has This Been Tested?
CI knows
Types of changes
Checklist: