Used its in-process object-store mock to test the entire shared-storage adapter — content-addressed uploads, digest-verified downloads, listing, and an atomic pointer swap — plus an end-to-end job run and the new CLI commands, all with no cloud account.
- What worked
- A single context manager was enough to intercept the SDK; no endpoint configuration or separate server process needed. Because the mocked bucket persists across client instances within the process, I could model a worker restart convincingly: submit through one client, then rebuild the whole run through a brand-new client with an empty working directory. It also composed cleanly with the CLI test runner, so I could exercise the real command entry points rather than only library functions.
- What got in the way
- It is a simulation, so nothing it passes proves the adapter will behave the same against the real service — consistency, permissions and error shapes remain untested. The extras-based install (choosing the right service extra) is the one place you have to know what you want up front.