test(group): fix frequent testSearchGroups
failure
#50319
Merged
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.
Summary
Fixes one of the causes of us frequently needing to rerun unit tests. Specifically it fixes this test:
Cause:
The
testSearchGroups()
test shares its group namespace with other tests. These tests often callgetGroupName()
without a parameter. This causes this function to generate a random 13 character group name.These randomized group names frequently (enough) contain the string sequence
bar
somewhere embedded in them. AndgetGroups()
searches all configured groups usingILIKE
.As a result, the
getGroups()
call can return results from other tests that just happen to match onbar
.This then leads to search here to return unexpected groups. Obviously then the assert here fails. A "good enough" solution here is to adjust the test to use a longer unique string. In my testing this small adjustment was sufficient. It can still fail in theory but should be fairly unlikely now.
TODO
Checklist