webtau

webtau copied to clipboard

GraphQL DSL - wrap execution in a step

4

Similar to how http execution is wrapped in a step.

tsiq-karold

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...

tsiq-karold

GraphQL DSL - configurability

2

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...

tsiq-karold

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...

tsiq-karold

GraphQL DSL - override request and response command line rendering

2

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...

tsiq-karold

We should provide a way to specify a query other than by passing in a string.

tsiq-karold

Similar to status code checks in HTTP, we should check that errors is null if users haven't performed any error assertions explicitly.

tsiq-karold

We probably should add additional ready to copy&paste output of actual array in case of a failure. Right now we list only mismatches and missing/extra values.

MykolaGolubyev

Want to experiment with a single screen console output during test runs via command line. The idea is to have a layout where you can see all the tests on...

MykolaGolubyev

Implement a caching auth provider

3

We have a couple of auth provider implementations now which basically do the same thing when asked for a token: - check local cache file and its validity (in terms...

tsiq-karold