Verify API Request Arguments in Tests #166
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.
This change updates the test suite to rigorously verify that the application sends the correct API requests for different natural language inputs.
It refactors the
SubmitQueryfunction to be a mockable variable and introduces aMockSubmitQueryhelper. The tests for Passage, Search, and Ask handlers are then updated to inspect the outgoingQueryRequeststruct, ensuring that:Query.Verses.Query.Words.Query.Prompt(andContext.Versesif applicable).This addresses the user's requirement to confirm that the correct API fields are used for each interaction type and ensures comprehensive test coverage for these scenarios.
PR created automatically by Jules for task 16093589716565048798 started by @julwrites