Magento 2 – How to Run PHPUnit for Testing

magento2phpunitunit tests

I tried to run a unit but failed with the following error.

My test class

<?php

namespace Vendor\Module\Test\Unit\Observer;

class CheckoutOnepageControllerSuccessActionObserverTest extends \PHPUnit_Framework_TestCase {

    public function testExecute() {
        $this->assertTrue(false);
    }

}

I run the phpunit command at /dev/tests/unit/

phpunit --filter CheckoutOnepageControllerSuccessActionObserverTest

It returns the following errors

PHP Fatal error:  Call to protected method PHPUnit_Framework_TestCase::getMockForAbstractClass() from context 'Magento\Framework\TestFramework\Unit\Helper\ObjectManager' in /vendor/magento/framework/TestFramework/Unit/Helper/ObjectManager.php on line 139

Fatal error: Call to protected method PHPUnit_Framework_TestCase::getMockForAbstractClass() from context 'Magento\Framework\TestFramework\Unit\Helper\ObjectManager' in /vendor/magento/framework/TestFramework/Unit/Helper/ObjectManager.php on line 139

Best Answer

The error probably is caused by some other test initializing an object with the object manager during construction, which is trying to mock the arguments.
This shouldn't happen unless the tests actually are being executed. Given the code and the command you posted, the error is not on your side.

Workaround

If you only want to run a single test class, it is much faster to specify the file as a command line argument instead of using the --filter parameter.

When using --filter phpunit will scan all tests for matches. This takes a long time, and along the way the error you encountered is triggered.

Instead, execute phpunit as follows.

From dev/tests/unit:

../../../vendor/bin/phpunit ../../../app/code/Vendor/Module/Test/Unit/Observer/CheckoutOnepageControllerSuccessActionObserverTest.php

Or from the Magento base directory:

vendor/bin/phpunit -c dev/tests/unit/phpunit.xml.dist app/code/Vendor/Module/Test/Unit/Observer/CheckoutOnepageControllerSuccessActionObserverTest.php

The phpunit command can also take a directory path instead of a file, which will limit the scanning for tests to that directory branch.
You can still use --filter to limit the test run to a single test method if you need to.

Related Solutions

Magento – Unit Test for overwrite collection class in magento2

First of all better to do not mock class under test.

Second one, better to use plugins instead of class overwrite.

And last, you must pass all parameters of parent constructor to your class.

Simplest way to instantiate class is using objectMangerHelper

    $objectManager = new \Magento\Framework\TestFramework\Unit\Helper\ObjectManager($this);
    $this->collection = $objectManager->getObject(
        'SR\RewriteSales\Model\Resource\Order\Collection',
        [
            'resource' => $resource, 
            'connection' => $connection,

        ]
    );

Magento2 Unit Testing – Use Object Manager

The object manager for unit tests is in magento/framework/TestFramework/Unit/Helper/ObjectManager.php and you obviously instantiated it, otherwise you would not get this error message. But you are using it wrong, it does not have a create() method. As explained in the linked answer, you need getObject():

public function getObject($className, array $arguments = [])

I am using the ObjectManager::create method to get an Instance of my Helper class in another custom class. So i shouldnt use ~::create at all?

Not with this object manager helper for unit tests. It has a different interface than the regular object manager. It sounds like you are passing the unit test object manager to a class under test. This is not how it is intended to be used.

In an integration test you can use: Magento\TestFramework\ObjectManager::getInstance() which works like the "real" object manager. In a unit test, you could instantiate or mock the real object manager Magento\Framework\App\ObjectManager.

But the fact that you need it, tells you that there's something wrong. Don't use the object manager to get an instance of your helper. Instead, add your helper as a constructor parameter and let Magento handle the Dependency Injection.

Best Answer

Workaround

Related Solutions

Magento – Unit Test for overwrite collection class in magento2

Magento2 Unit Testing – Use Object Manager

Related Topic