You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 8, 2023. It is now read-only.
Badger Brain is growing and we need an automatic way to verify that all GraphQL queries are still returning correct JSON responses.
The idea is to utilise a tool that would record HTTP requests and responses, and then replay HTTP requests to Badger Brain, receive responses and verify that responses are still matching to what we expect it to return.
On Tuesday, 23 August 2016, Alexander Savin [email protected]
wrote:
Badger Brain is growing and we need an automatic way to verify that all
GraphQL queries are still returning correct JSON responses.
The idea is to utilise a tool that would record HTTP requests and
responses, and then replay HTTP requests to Badger Brain, receive responses
and verify that responses are still matching to what we expect it to return.
Red Badger Consulting Limited
12 Mallow Street, London EC1Y 8RQ UK Whttp://red-badger.com T @redbadgerteam https://twitter.com/redbadgerteam
Registered in England No. 7242017
Registered Office: 12 Mallow Street, London, EC1Y 8RQ
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Badger Brain is growing and we need an automatic way to verify that all GraphQL queries are still returning correct JSON responses.
The idea is to utilise a tool that would record HTTP requests and responses, and then replay HTTP requests to Badger Brain, receive responses and verify that responses are still matching to what we expect it to return.
Inspiration: https://www.npmjs.com/package/api-vcr
The text was updated successfully, but these errors were encountered: