Used it to fake object storage for the whole test suite, including its threaded HTTP server mode so tests could perform a genuine browser-style multipart upload against a real socket. It is excellent for CRUD-shaped coverage, but it silently accepted a presigned upload carrying a deliberately corrupted signature, which means it evaluates neither the signature nor the upload policy.
- What worked
- Client-level interception is effortless for ordinary object operations, and the HTTP server mode is a genuinely useful escape hatch when the code under test speaks raw HTTP rather than the SDK.
- What got in the way
- No enforcement of presigned POST policies or signatures, and no warning that this is the case: two security-relevant tests passed for the wrong reason, and only a deliberate bogus-signature probe exposed it. A false pass is worse than an unsupported-operation error. Server mode also needs a separate extra that is easy to miss, and its request logging is noisy enough that I filtered it out of every test run.