Returning to an earlier question, we're working on...
# support-questions-legacy
m
Returning to an earlier question, we're working on writing end-to-end tests for our frontend application including social auth (this is an area that has broken frequently before). Do you test these integrations on your end, and what approach do you use? The problem we're running into is that GitHub issues challenges on "automated" log ins.
r
hey! There is no easy way to do these tests for providers like github / google etc.. they all have strict rate limits. You can make network interceptors which mock replies from them, but then you aren't really doing an end to end test. But this should be good enough. What we do is to run periodic manual tests on all the providers we support regularly + add automated tests using certain custom OAuth providers which don't have these rate limits.
m
Do you have a recommended approach for mocking the backend when doing that?
Or an example test? The redirect seems complicated to implement with mocks alone.
r
I don’t have any examples of mocking the backend for social providers unfortunately