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
Writing tests for Apollo is gruesome due to this unintuitive error. Whenever one mocks a query or mutation, if the mock isn't exactly the same as the real one, the error 'No more mocked responses for the query' is thrown.
The issue is that this error doesn't state what the discrepancy is between the mock and the real query, which leads to a lot of time being spent double-checking mocks and queries. For complex queries this can be a real time sink.
This error should point out what exactly is not matching. This would save testers a ton of time.
The text was updated successfully, but these errors were encountered:
Writing tests for Apollo is gruesome due to this unintuitive error. Whenever one mocks a query or mutation, if the mock isn't exactly the same as the real one, the error 'No more mocked responses for the query' is thrown.
The issue is that this error doesn't state what the discrepancy is between the mock and the real query, which leads to a lot of time being spent double-checking mocks and queries. For complex queries this can be a real time sink.
This error should point out what exactly is not matching. This would save testers a ton of time.
The text was updated successfully, but these errors were encountered: