This doc proposes an abstraction to set fixture expectations for mock clients during a test run.
The goal is to treat fixtures management as first class citizen and maintain clean fixture semantics. Fixtures that belong to a specific client should reside in a centralized place associated with that client. It should be recognized that the mock client and its affinitivie fixtures together can become one functional unit. With this realization, the action of setting input/output expectations for a mock client method becomes implementation details and can be abstracted away by defining a method with the same expectation semantic on the combined functional unit. For example, instead of writing
import store "import/path/to/store/fixture"
// ad-hoc fixtures
userHeader := map[string]string{
"x-client-version": "1.1.2",