5 ms·
Interesting! Staying lightweight and zero-dependency is certainly a good argument. Out of curiosity - which programming language(s) are you / your team developi
by whummer 5y ago
Interesting! Staying lightweight and zero-dependency is certainly a good argument. Out of curiosity - which programming language(s) are you / your team developing in? Do you have a notion of how much (%) of your time, approximately, goes into maintaining the mocks - does it scale / pay off over time?
- qaq 5y agoWell if they use https://github.com/spulec/moto https://github.com/spulec/moto they don't have to maintain the mocks
- deleted 5y ago[deleted]
- surfer7837 5y agoWe use Typescript and jest for the mocks. Probably about 10%, they’re very simple mocks, all they do is return success and in a few unit tests we make them return failure and then test how our app responds. I can’t really say if it pays off but it has caught some issues, would like to expand them more and implement more logic in then to check arguments etc but haven’t been able to yet. This article is similar to what we’ve done https://dev.to/elthrasher/mocking-aws-with-jest-and-typescript-199i https://dev.to/elthrasher/mocking-aws-with-jest-and-typescri... We also have a pipeline that does e2 work tests and canary releases to hopefully limit the blast radius. If we encounter >10 errors in a 1 minute period we roll back and the team are alerted