automatic-api

Issue split from hasura/graphql-engine#6951

our pytest output has a pretty low signal:noise ratio, and it's often difficult to understand the cause of a test failure, if there is one. [Example: a 8600-line log for what turned out to be a flaky test that passed on a second run](https://app.circleci.com/pipelines/github/hasura/graphql-engine-mono/10008/workflows/5e17c7

Hello Maurits,
This is more of a request than it is an actual issue, but I think the value in this request is really high (for newcomers, especially - but not limited to).
Could you please add a COMPLETE application example of using the API (with user authentication, maybe even with the user-creation SQL script, table authorization, etc).
This would be really really helpful as a quickstart /

What would you like to be added:

It would be amazing to have a "Deploy with Heroku" button. Someone please help and build this.

https://devcenter.heroku.com/articles/heroku-button

Why is this needed:

Problem

The test cases are using Django client which is much suited for emulating a browser, so the default request body is priority content type is multipart instead of json which is what we are using mostly on the frontend

Proposed solution

DRF test client should be used instead of django client in order to emulate an API cal