Testing the client

[getcandy]

Testing the client

[alecritson]

Hey @tooshay

Sure, so you can set up the client like:

CandyClient::fake();
CandyClient::init(config('app.url'));

Then you can create a mock response like:

$response = new GetCandy\Client\Testing\Response(200, ['some' => 'data']);
CandyClient::next($response);

If your service class makes two GetCandy api requests under the hood, you can queue them up:

$firstResponse =  new GetCandy\Client\Testing\Response(200, ['some' => 'data']);
$secondResponse = new GetCandy\Client\Testing\Response(200, ['more' => 'data']);

Then just call

CandyClient::queue([$firstResponse, $secondResponse]);

---

It's probably worth mentioning that I realise you have to do the responses manually at the moment, but I do want to implement stubs to this so you will only need to call CandyClient::fake(); and it will automatically mock the response depending on the endpoint and give a response back with a data structure you'd expect from the live api without you having to define that yourself.

[tooshay]

@alecritson This is great, thanks.

I do have some functional tests that require writing to the DB, however, and while the parts of our application that do this write to the test DB when the test runs, CanyAPI still writes to the regular DB. How can I get the API to write to the test one when tests are run?