hypothesis-graphql VS microservice-apis

To create your own test cases, I recommend you use hypothesis-graphql in combination with hypothesis. hypothesis is a property-based testing library. Property-based testing is an approach to testing in which you make assertions about the result of a test given certain conditions and parameters. For example, if you have a mutation that requires a boolean parameter, you can assert that the client will receive an error if it sends a different type. hypothesis-graphql is a GraphQL testing library that knows how to use hypothesis strategies to generate query documents.

The code for the book is freely available on GitHub. Feel free to check out the code, raise issues if something isn’t clear, and contribute new code. It’d be cool if this becomes a reference for Python developers interested in microservices and APIs.

Hi u/Kranke you can see an example of how to implement a fully decoupled service layer in chapter 7 of my book Microservice APIs, which you can download for free from this link. The code for the book is also freely available and you can check it out in this repo. Decoupling is desirable for the reasons explained in this part of the video.

There's not a whole lot of documentation and tutorials on how to use these tools, but I've written something about them in my upcoming book Microservice APIs. To see a practical example on how to use hypothesis-graphql, check out this file from the book's GitHub repository. For an explanation of the code, check out section 12.5.2 of chapter 12 of the book. Note: that section will go away in the next release of the chapter so make sure you check that specific link. You don't need to buy the book to read the section - Manning allows you to read a few fragments for free every day. To learn to generate hypothesis strategies, check out section 12.3 of chapter 12.