Hi,

Great package :)

I'm using guzzler package in one of my Laravel applications (first time).

And my test looks like this:

$this->guzzler->expects($this->exactly(1))
    ->get("/customerrssss")
    ->willRespond(
        new Response(
            201,
            [],
            '{ "test": "test" }'
        ));

$client = $this->guzzler->getClient([
    "base_uri" => "https://api.mollie.com/v2/"
]);

$apiClient = new MollieApiClient($client);

$apiClient->setApiKey('test_dHar4XY7LxsDOtmnkVtjNVWXLSlXsM');

Mollie::shouldReceive('api')
    ->once()
    ->andReturn(new MollieApiWrapper($this->app['config'], $apiClient));

$response = $this->post('/api/register', [
    'city' => 'Den Bosch',
]);

dd($response);

The response is '{ "test": "test" }'. But I don't use the url /customerrssss but /customers in my controller.

So it looks like it doesn't matter what url I provide I always get that response. What could I be doing wrong here ?

Thanks!

Hi, thank you so much for this awesome package!!

Running on PHPUnit 8.2.1 the following error is thrown:

[Error] Class 'PHPUnit\Framework\MockObject\Invocation\ObjectInvocation' not found
#1  /home/johan/Code/pascal/vendor/blastcloud/guzzler/src/Expectation.php:141
#2  /home/johan/Code/pascal/vendor/blastcloud/guzzler/src/Guzzler.php:43
...

The PHPUnit\Framework\MockObject\Invocation namespace was removed on version v8.2 but remains on v8.1.6.

#12

Unfortunately, I could not make the correct name of the method due to the peculiarities of filter connecting mechanism.

Example of error output:

Expectation: 
-----------------------------
JSON-RPC 2.0: (POST /rpc) {
    "id": "123",
    "jsonrpc": "2.0",
    "method": "test-method",
    "params": {
        "a": 1,
        "b": 2
    }
}

Hello, just discovered this package and it looks incredible. However I am having some issues, can't seem to locate the issue.

Sample code:

$this->guzzler->expects($this->once())
            ->get('/v2/balance')
            ->willRespond(new Response(401, [], '{}'));

Error:

Error: Cannot instantiate interface PHPUnit\Framework\MockObject\Invocation

/Users/anton/Projects/project/project/vendor/blastcloud/chassis/src/Expectation.php:119
/Users/anton/Projects/project/project/vendor/blastcloud/chassis/src/Chassis.php:33
/Users/anton/Projects/project/project/vendor/blastcloud/guzzler/src/UsesGuzzler.php:37
/Users/anton/Projects/project/project/vendor/blastcloud/guzzler/src/UsesGuzzler.php:3

PHPUnit Version: 9.5.1 Guzzle Version: 7.2 Guzzler Version: 2.0.1 PHP Version: 7.4

Any ideas?

Quite often we need to mock RPC requests.

We can easily create a macro:

Expectation::macro('withJsonRpc', function (Expectation $e, $endpoint, $method, $params, $id = null) {

    $json = [
        'jsonrpc' => "2.0",
        'method' => $method,
        'params' => $params,
    ];

    if ($id) {
        $json['id'] = $id;
    }

    return $e
        ->post($endpoint)
        ->withJson($json);
});

But, unfortunately, if we get an exception, then we cannot understand that it was exactly a call of withJsonRpc()

How about creating a separate filter with own error message? Something like

JSON-RPC
Endpoint: /rpc
Method:   POST
Body: {
    "id": 123,
    "jsonrpc": "2.0",
    "method": "test-method",
    "params": {
        "a": 1,
        "b": 2
    }
}

Please either leave a thumbs up, thumbs down, or any other reaction, or respond with a comment.

For the next phase of Guzzler, I'd really appreciate feedback from anyone interested in the project. For a full description of an upcoming project Road Test, please see the related page on the documentation site; Road Test

This idea is very strongly based on PHPUnit's coverage report. However, instead of keeping track of lines of code executed in a test, it would keep track of endpoints hit and response codes returned from those endpoints. By doing so, a report can be generated afterwards that your code is in fact accounting for each endpoint you intent to, and any error status codes you want to ensure are accounted for. For example, you can verify your code handles responses for 200, 500, and any other status code from the endpoint /example/api/v2/companies/14968.

This project would need to come after Drive is completed enough to handle recording of endpoints and statuses. If Drive can be thought of as a mechanism to do contract testing, then Road Test is the result and proof that all corners are covered that were wanted.

Again, please leave a reaction or any thoughts on this issue. Feedback is helpful.

Please either leave a thumbs up, thumbs down, or any other reaction, or respond with a comment.

For the next phase of Guzzler, I'd really appreciate feedback from anyone interested in the project. For a full description of the next project Drive, please see the related page on the documentation site; Drive

The basic idea is a response factory system for a your tests based on either a Swagger/OpenAPI, RAML, or Blueprint API spec doc provided by any service you want to interact with. For example, you might want to integrate with an invoicing service. If so, you may want to specify what your code expects back from a GET endpoint for querying an invoice.

You may build out something like the following:

use function BlastCloud/Drive/drive;

class SomeTest extends TestCase
{
// ...

    $this->guzzler->expects($this->once())
        ->get('/v3/company/{$this->companyId}/invoice/{$this->itemId}')
        ->willRespond( drive('invoice-fountain.invoices.get', 200) );

By default, any data specified in the spec would auto-fill to the same structure with data provided by Faker. You could also fill anything specific you'd like returned, much like Laravel's Model Factories.

//...

$this->guzzler->expects($this->once())
    ->get('/v3/company/{$this->companyId}/invoice/{$this->itemId}')
    ->willRespond( 
        drive('invoice-fountain.invoice.get', 200)
            ->json([
                'data' => drive('invoice-fountain.invoice', [
                    'customer_id' => 42,
                    'date_issued' => $faker->dateThisYear()
                ])
            ])
    );

Again, please leave a reaction or any thoughts on this issue. Feedback is helpful.

Currently, the API for withCallback() accepts one argument, the closure to filter the history items. A second one should be added so that the user can pass a more helpful message for what their closure is actually checking.

// Before
$expectation->withCallback(function ($history) { 
   /* something */ 
   return bool;
});

// After
$expectation->withCallback(function ($history) {
    return bool;
}, "Failed asserting that the Rhinos are just overweight unicorns.");

• [ ] Lookup GraphQL Spec
• [ ] Figure out what can be easily supported from a filter perspective
  • [ ] Some of the internal functions could make for an unfriendly API on the Guzzler side
  • [ ] If it can be done just off of the final query string, it should be fine, but will need some work on the API friendliness.
• [ ] Create a WithGraphQL filter file.
• [ ] Build out class and tests.
• [ ] May require the most complex __toString() method thus far.

Include:

• [x] Make outline to fill out

• [x] Idea for Drive

  • [x] For working with OpenAPI and others docs
  • [x] Response factories modeled after Laravel model factories
  • [x] validate() method on expectations.
  • [x] Possible syntaxes

• [x] Idea for MPG

  • [x] Show PHPUnit coverage report as example
  • [x] Show possible idea for report
  • [x] Mention new coverage standard that would be needed.

• [x] Simple get request(s) : Google Maps
• [x] Asynchronous / Promise based code : Google Street view
• [ ] Working with forms (both URL encoded and multipart) : Stripe
• [ ] Uploading Files : S3
• [x] Handling failure scenarios

Hi!

I've seen this issue being closed while there are still quite a few places in the docs that do not have examples https://github.com/blastcloud/guzzler/issues/3

Do you plan to add those ?

Particularly, I took quite a while to figure out how to test multi-part forms that contains file, as I was trying to use the withBody method combined with a MultipartStream object.

My final solution here is the following, if anyone have the same needs:

$filepath = dirname(__FILE__) . '/../assets/asset1.jpg';
$this->guzzler
    ->expects($this->once())
    ->post('/assets/')
    ->withHeader('Authorization', 'Bearer ' . $this->fakeToken)
    ->withForm([
          'my_field_1' => 1,
          'my_field_2' => 'my_value',
     ])
     ->withFile('file', new File(Utils::tryFopen($filepath, 'r')))
     ->willRespond(new Response(409, [], ''));