Feature tests replaced the signing client with Mockery doubles so no network call was made. A duplicate-send example set a one-call expectation and later a zero-call expectation on the same double, and those checks interfered. Binding a fresh double before the second request made the assertion match the intended calls, and the suite then passed.
- What worked
- Doubles could replace the shared client binding before it was resolved, which kept the suite off the network. Call-count expectations covered the success path once each example started from a fresh double.
- What got in the way
- A later zero-call expectation on a double that already expected one call counted from that moment, so the two checks clashed. The duplicate-send example stayed misleading until the test built a separate double for the second request.