Samuel Silva

Ok, could you label this issue as a bug to be fixed? I don't have time right now but if find any I can take a look. I think this...

Yeah I knew this was the issue, I just didn't have time to find where it was being misused, see: https://github.com/UnlyEd/next-right-now/issues/200#issuecomment-725025435 Glad you found it. :) > Could you try...

Actually it seems I tested this already see: https://github.com/UnlyEd/next-right-now/issues/200#issuecomment-725007923

Hey @Vadorequest are you still planning to work on this? It'd be super helpful to have it.

This is definitely a good start.

Btw, I'd be happy to provide a PR, I already have a working setup that generates the `schema.graphql` as well as ts types.

Out of curiosity, why are you moving away from GraphQL?

> It would be great to know what you mean by "page tests". If you mean integration testing and navigation workflows, then it's better to use Cypress to perform those....

**react-testing-library** is intended for unit/integration/e2e testing directly from the DOM's perspective. It uses React renderer and ReactTestUtils internally, requires real DOM because it's component's output that is asserted in tests,...

Btw, we already have many cases that we can use it.