4 ms·
As someone who's about to assist a frontend team to implement testing against a backend I've developed (my first time doing something like this), I can see that
by mulmboy 5y ago
As someone who's about to assist a frontend team to implement testing against a backend I've developed (my first time doing something like this), I can see that mocking backend APIs is inherently tedious and error-prone. And I'm not confident that we have the resources to keep the mocked endpoints consistent with the real backend given the pressure to develop the "real product".
What are the downsides of of using a real API (e.g. dev environment) for automated testing?
- lhnz 5y ago> What are the downsides of of using a real API (e.g. dev > environment) for automated testing? It can be difficult to recreate the situations required to produce particular responses, and if you are using this development environment to deploy backend fixes, downtimes or bugs will sometimes block the engineering work of your UI team.
- jarofgreen 5y ago> What are the downsides of of using a real API (e.g. dev environment) for automated testing? Slower, harder to set up state the tests need. Front end teams should also be testing their code against a broken back end; eg http 500 responses.