FQM-318: Standard prefetch expressions test#120
Merged
Conversation
c846b45 to
92d9855
Compare
92d9855 to
bfc5fab
Compare
Jammjammjamm
approved these changes
Jun 29, 2026
arscan
approved these changes
Jun 30, 2026
karlnaden
approved these changes
Jul 6, 2026
This file contains hidden or 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
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.
Summary
This adds a test for
found-29. It checks whether the server's advertised prefetch queries match the standard queries, and emits warnings when they don't.The IG's language around this requirement is a bit vague, so please check my interpretation.
The actual requirement:
Since the server is allowed to have more or fewer prefetch expressions than the standard set, I conclude that whether or not a mismatched prefetch expression violates the requirement depends on the intent of the expression, which is impossible for Inferno to know, and therefore up to the tester's judgement. I also took the wording of the requirement to mean that Inferno should not enforce specific expression key names (e.g. 'pat' versus 'patient').
Testing Guidance
Anticipated Provider-side Test Impact
None