Support for graphql in e2e testing

[t-zander]

Current behavior:

As far as I know there is no out of the box solution for stubbing graphQL requests.

With common api we can just do route('GET', 'someurl', dataToReturn)

Its really great and easy.

However, I can't find any clear, simple and documented solution to do something like this for graphQL. I understand that it may be a problem because it works differently.

But it could be great to have an ability to stub requests to graphQL.

Thank you

Desired behavior:

Want to have an easy and clear handling of graphQL stubbing.

[jennifer-shehane]

There is a very large thread discussing workarounds here: cypress-io/cypress-documentation#122

But yes, we actually did not have a specific issue requesting support for GraphQL specifically. It's definitely on our Roadmap!

[the-ult]

@jennifer-shehane any news on the roadmap about when/if graphql support will be integrated?

Is https://github.com/tgriesser/cypress-graphql-mock the way to go?

The problem (for me at least) is that the cypress-graphql-mock does not work with Apollo-angular (XHR) requests.

@tgriesser are you planning on integration apollo-angular (XHR) support as well? Your solutions seems promising, but I can't get it to work with Angular

[Jeff-Duke]

Just wanted to check the status/roadmap on this. is https://github.com/tgriesser/cypress-graphql-mock still being maintained? comments in cypress-io/cypress-documentation#122 seem to indicate others are not getting responses on that solution and are now forking and modifying the code to their needs. Is there a timeline for native GQL support in Cypress?

[tgriesser]

We have a solution we've been iterating on internally for our own GraphQL development that we're hoping to open source sometime soon.

No specific timeline we can commit to, but it's something I personally would like to get released, especially since the cypress-graphql-mock linked has quite a few issues we've identified in our own usage.

[jrnail23]

@tgriesser, I'm of the aforementioned folks who have forked and modified your cypress-graphql-mock code, and I'd really like to hear more about the issues you've identified.
Also, I know you can't commit to anything specific, but can you provide a loose ballpark forecast (i.e., weeks, months, next year)?

I'm currently in the middle of adapting this stuff for our internal test tooling, but I'd hate to invest much more effort in this if it's about to change dramatically, or if we're building on top of something that might be fundamentally flawed.

Thanks!