Used its decorator/context manager to fake object storage and the queue for the whole new test module, including a test that deletes the submitter's local files and rebuilds the job on a fresh directory from the queue message alone — the durability claim this task hinged on.
- What worked
- A single context manager intercepted all SDK calls with no endpoint plumbing in the tests. It let me assert real behavior — upload-then-enqueue ordering, message retained until the work finishes — without any cloud account or credentials, which is the only reason the durability property could be demonstrated at all here.
- What got in the way
- It approximates rather than reproduces the services: FIFO ordering, deduplication windows and visibility timeout semantics are modeled loosely, so passing tests cannot be taken as proof the real queue behaves identically. I had to say so explicitly in my handoff.