Magento 2 – ObjectManager Unusable in Unit Tests

magento2phpunittesting

I am following Vinai Kopp's Series on Mage2CodeKata but it gives me an error message when I declare the $objectManager. After seeing these treads:

I want to try the ObjectManager in Magento\TestFramework\ObjectManager not the one in magento/framework/TestFramework/Unit/Helper/ObjectManager

Here is my code:
before class definition:

use Magento\TestFramework\ObjectManager;

after class definition:

public function testTheModuleIsConfiguredAndEnabled()
{
    /** @var ObjectManager $objectManager */
    $objectManager = ObjectManager::getInstance();

    $moduleList = $objectManager->create(ModuleList::class);

    $this->assertTrue($moduleList->has($this->moduleName));
}

Here is the error message:

PHP Fatal error: Class 'Magento\TestFramework\ObjectManager' not found

Best Answer

For unit tests you should use Magento\Framework\TestFramework\Unit\Helper\ObjectManager which allows to create any object with needed arguments (if they aren't passed, mocks will be created instead).

The Magento\TestFramework\ObjectManager is used only by integration tests and you get the PHP Fatal error: Class 'Magento\TestFramework\ObjectManager' not found error because the different autoload.php file should be used.

For more details, please, see the testing section from official the Magento 2 dev docs.

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,

        ]
    );

Magento – Magento 2 integration tests load data fixtures before config fixtures

This looks to be impossible for now using annotations mechanism. Even if data fixture is declared on class level it will be executed for every test after config fixture.

The following approach works:

<?php
namespace VendorName\ModuleName\Model;

class SomeTest extends \PHPUnit_Framework_TestCase
{
    public static function setUpBeforeClass()
    {
        require realpath(TESTS_TEMP_DIR . '/../testsuite/Magento/Store/_files/core_fixturestore.php');
        parent::setUpBeforeClass();
    }

    public static function tearDownAfterClass()
    {
        /** Teardown is necessary because this fixture was committed to DB in setUpBeforeClass */
        require realpath(TESTS_TEMP_DIR . '/../testsuite/Magento/Store/_files/core_fixturestore_rollback.php');
        parent::setUpBeforeClass();
    }

    /**
     * @magentoConfigFixture fixturestore some/config/field 1
     **/
    public function testSomething()
    {
        /** Test content */
    }
}

Such approach also makes sense from performance standpoint, because store creation is pretty heavy operation, and now it will be done only once per test case.

Best Answer

Related Solutions

Magento – Unit Test for overwrite collection class in magento2

Magento – Magento 2 integration tests load data fixtures before config fixtures

Related Topic