Add utility to assert hit terms #2761
Open
+973
−504
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Expected hit terms can be required or optional Expected hit term sets can be 'all of' or 'any of' HitTermAssertions now throws an error if unexpected hit terms are returned
…estLimitReturnedGroupsToHitTermGroups Migrate more variables out of method parameters and into class level variables with appropriate setters. Refactor 'runTestQuery' to be more modular. Add expected hit terms to test, update HitTermAssertions to expect no hit terms in certain cases
avgAGB
approved these changes
Feb 18, 2025
FineAndDandy
approved these changes
Feb 19, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Added a utility to assert hit terms and migrated one of the hit term tests over to the new utility. This allows developers to describe the expected hit terms for most basic boolean logic expressions.