Omise Unit Tests Clashing With Laravel Unit Tests about omise-php HOT 2 OPEN

@ahirota Hi, this might not related to the solution that you are looking for, but would you mind to share a case where you want to connect to the real API server for a unit test script? Is there any specific reason to bypass the fixture files?

from omise-php.

@guzzilar To Preface, I've created a Repository to handle calls to the Omise API. My test suites are all designed to test basic functionality within my application and I'd need to connect to the real API server in order for my tests to pass.

One of my test suites generates a new customer with a customer token, tests creating charges, creating and destroying charge schedules, adding and removing cards from the customer, and then finally removing the customer all together. If I were to use the default fixture files, the act of creating a new customer with email: [email protected] and any other parameters, returns with the response saved in the fixture files.

Here's a code example:

  public function testCustomer()
    {
        // create
        $customer = $this->OmiseRepository->makeCustomer('[email protected]', 333);
        self::assertEquals('[email protected]', $customer->email);

        // delete
        $bool = $this->OmiseRepository->destroyCustomerById($customer->id);
        self::assertTrue($bool);
    }

In this test, both assertions fail because new customer data is never created. The response is always taken from the fixture files. This issue extends to customer tokens and beyond.

I guess my main issue is that I don't want to test the package itself, but rather the extensions and wrappers I've created, and using PHPunit calls _executeTest for any Omise API related functions.

from omise-php.