3 ms·
My concern with relying on things like these for testing is they're not supported by AWS, so behaviours can easily diverge without you realising. I think we've
by djhworld 10y ago
My concern with relying on things like these for testing is they're not supported by AWS, so behaviours can easily diverge without you realising.
I think we've got a lot of mileage in the past out of just mocking request/responses when testing AWS interactions. The only time we've ever used a pseudo-service was when testing against the dynamoDB JAR they provide with the SDK.
- ascendantlogic 10y agoThat is my first concern as well but testing and bug counts are not an all-or-nothing thing. If something like this can reduce bug counts in a complicated distributed system while reducing costs vs testing against "the real thing" it still may very well be worth it.
- fadzlan 10y agoYup. There's nothing to stop some to have a lot of local iterations for speed, and then later when you are satisfied, have the test run on real AWS. Would save some money too.