frostblog_net / ecomdev_phpunit
Magento PHPUnit Integration. Forked from EcomDev_PHPUnit
Installs: 112
Dependents: 0
Suggesters: 0
Security: 0
Stars: 0
Watchers: 1
Forks: 178
Open Issues: 1
Type:magento-module
Requires
Replaces
- ivanchepurnyi/ecomdev_phpunit: *
This package is not auto-updated.
Last update: 2018-11-24 18:26:45 UTC
README
Magento PHPUnit Integration
Fork of EcomDev_PHPUnit. Magento is a quite complex platform without built in unit test suite, so the code is not oriented on running tests over it.
This extension was created especially for resolving this problem and promoting test driven development practices in Magento developers community. It doesn't change core files or brake your Magento instalment database, because all the system objects are replaced during the run-time with the test ones and a separate database connection is used for tests.
System Requirements
- PHP 5.6 or higher
- PHPUnit 3.7.x
- Magento CE1.4.x-1.7.x/PE1.9.x-PE1.10.x/EE1.9.x-1.12.x
Build Status
Documentation
Also you may follow our related blogposts.
Installation
-
There are two ways of obtaining the extension:
- Use Module Manager
modman clone git://github.com/EcomDev/EcomDev_PHPUnit.git
- Add extension as dependency in your composer.json to install it from Magento Composer Repository
{ "require": { "ecomdev/ecomdev_phpunit": "*" } }
-
Open your terminal and navigate to your magento directory for performing the following command, they are required to configure system for running the test suite
# Shell scripts needs to be run from this directory cd $YOUR_MAGENTO_DIRECTORY/shell # Specify your test database name and base url for controller tests php ecomdev-phpunit.php -a magento-config --db-name $DB_NAME --base-url http://your.magento.url/
If you receive a warning on PHPUnit checks for optional packages, run the following command
php ecomdev-phpunit.php -a fix-autoloader
-
Run the unit tests first time for installing test database. It will take about 3 minutes.
$ phpunit
-
If it shows that there was no tests found, it means that extension was successfully installed. If it shows some errors, then it means, that your customizations has install scripts that relay on your current database data and you should fix them. Or use your dev database as a base for the tests, but prior first time running the suite.
Issue Tracker
We use github issue tracker only for contributions management. If you want to post an issue please use our Issue Tracker