Magento – Tools for Unit Testing in Magento

ecomdev-phpunittestingunit tests

What do you use for Unit Testing in Magento? Or what do you know about Unit Testing and Magento? Whether you do TDD or you just want to have unit test coverage for your project components, you need some tools to do this.

The first basic approach is to use plain phpunit, but there are things that need additional gimmicks to make Magento "testable".

Everything I worked with is related to phpunit:

MTAF
EcomDev_PHPUnit (drawbacks: can't test emails)
TechDivision_MagentoUnitTesting (attempt to backport Magento 2 Unit Tests)
Mage-Test (lightweight unit testing for Magento)

Are there other options?

Best Answer

Check out PHPSpec with MageSpec if you want something not based on PHPUnit, but with some Magento Integration. Its usable, but not just quite ready for prime time. For mocking PHPSpec 2 uses Prophecy (which is great), but doesn't like magic getters and setters at all. For that reason its better to use Mockery instead, which works fine (and I also like it a lot).

Then there also is Behat with BehatMage for BDD with Magento. Worth a look, but it fails in for example if you want to test different store views on different domains.

There also is an extension to BehatMage called MageBehat (awful naming!), which came out of a hackathon. It provides a lot of Magento specific actions to BehatMage, but to be honest, some of the workarounds used are more of a hack then real solutions to the underlying issues. Still, its usable.

I hope to see both projects - MageSpec and BehatMage - flourish in future.

Related Solutions

Magento – Magento 1 Testing Frameworks

We are using the EcomDev_PHPUnit extension which allows you to test almost everything in Magento without modifying any core files.

I recommend the dev branch which is currently more stable than the master.

We also have experience with Mage-Test, but can not recommend it, because it overwrites some core files in the community codePool.

Magento – Unit Testing Observers in Magento

I also like to ensure that the observer is in fact called when doing an appropriate action, e.g. when you dispatch a catalog_product_save_after, then do something like:

// initialize $mock as your observer
$mock->expects($this->once())
     ->method('catalogProductSaveAfter')
     ->will($this->returnSelf()); // the observer usually returns itself
$product = Mage::getModel('catalog/product')->load(4);
// Do action which should dispatch your event once
$product->setName("test")->save();

This will fail if your method is not called exactly once.

Best Answer

Related Solutions

Magento – Magento 1 Testing Frameworks

Magento – Unit Testing Observers in Magento

Related Topic