Karol Dudzinski
Karol Dudzinski
If one is asserting that a field is null and makes a typo in the field name then the test will always pass even if the field comes back non-null....
If one is asserting that a field is null and makes a typo in the field name then the test will always pass even if the field comes back non-null....
Right now the introspection call does not appear in stdout or the report which is not ideal.
Similar to how http execution is wrapped in a step.
This needs a bit more thought but in addition to the http doc captures, we might want to consider some graphql specific stuff, e.g.: * request.query.graphql * request.graphql.variables.json * response.graphql.data.json...
1. url - in theory it's possible someone may serve at root for example, rather than graphql. It's debatable whether we should do this at all or just force users...
A few things we probably want to do: * display coverage and timing data per operation like we do for openapi * another tab similar to http calls which shows...
Currently a response looks like this: ``` > executing HTTP POST http://127.0.0.1:52641/graphql request (application/json): { "query": " query { allTasks(uncompletedOnly: false) { id description } } " } ``` We...
We should provide a way to specify a query other than by passing in a string.
Similar to status code checks in HTTP, we should check that errors is null if users haven't performed any error assertions explicitly.