Download the PHP package ambimax/ecomdev_phpunit without Composer
On this page you can find all versions of the php package ambimax/ecomdev_phpunit. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download ambimax/ecomdev_phpunit
More information about ambimax/ecomdev_phpunit
Files in ambimax/ecomdev_phpunit
Package ecomdev_phpunit
Short Description Magento PHPUnit Integration
License OSL-3.0
Homepage http://www.ecomdev.org/shop/code-testing/php-unit-test-suite.html
Informations about the package ecomdev_phpunit
Magento PHPUnit Integration
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.3 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
- Add extension as dependency in your composer.json to install it from Magento Composer Repository
-
-
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
If you receive a warning on PHPUnit checks for optional packages, run the following command
-
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
Contributions
If you want to take a part in improving our extension please create branches based on dev one.
Create your contribution branch:
$ git checkout -b [your-name]/[feature] dev
Then submit them for pull request.