Draft: Check for empty response in shared example 'a working graphql query'
What does this MR do and why?
As described in #418171 (comment 1469198346), the 'a working graphql query'
shared example doesn't check for empty results.
A query might be successful but return nothing, which can mask problems with the test and/or the query itself.
This change adds a verification for empty responses.
Screenshots or screen recordings
Screenshots are required for UI changes, and strongly recommended for all other merge requests.
Before | After |
---|---|
How to set up and validate locally
Numbered steps to set up and validate the change are strongly suggested.
MR acceptance checklist
This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.
-
I have evaluated the MR acceptance checklist for this MR.