possibility to have different fixtures for same endpoint about php-http-fixture-client

[bbrala]

This is a valid point, we'll look into possible solutions. For now you could the fixtures by success/fail and load a different fixtures path until we have a working solution.

[JaZo]

@Fivell, I think it is hard to determine which response should be returned at which time if the uri is the same. Do you have an idea for a possible implementation?

You can use different fixture paths as suggested by @bbrala. Besides, this client extends php-http/mock-client. This allows you to add custom responses (or exceptions) that ignore the fixtures.

$client = new \Swis\Http\Fixture\Client(...);
$response = $this->createMock('Psr\Http\Message\ResponseInterface');
$client->addResponse($response);

$client->sendRequest(new Request(...)); // uses above response from queue
$client->sendRequest(new Request(...)); // uses fixture file

N.B. You can't use a default response for the mock client because this client uses that to set the response from the fixture.

[JaZo]

I have added a note about the underlying mock-client to the readme: https://github.com/swisnl/php-http-fixture-client/blob/master/README.md#mocks-advanced

[Fivell]

@JaZo

I think it is hard to determine which response should be returned at which time if the uri is the same. Do you have an idea for a possible implementation?

I didn't dig into implementation of current library (i even not a php guy for ages) but for sure the only way is to also take request body into a account not only method/path, also we finally succeed with php-vcr library (which stores yaml files with both requests and responses in fuxtures) when test our api client.

Feel free to close this issue since you find a way to do it ignoring fixtures and we find more complex library for our needs

[JaZo]

I'm closing this issue because alternatives exist and this can't be fixed using the current matching strategy i.e. mapping a request (body) to a static file.