Environment and development tools: Difference between revisions

Jump to navigation Jump to search
m
Line 152: Line 152:
* Download a release archive from http://pear.phpunit.de/get/ and extract it to a directory that is listed in the include_path of your php.ini configuration file.
* Download a release archive from http://pear.phpunit.de/get/ and extract it to a directory that is listed in the include_path of your php.ini configuration file.
* Prepare the phpunit script:
* Prepare the phpunit script:
** Rename the phpunit.php script to phpunit.
** For Linux: Rename the phpunit.php script to phpunit and replace the @php_bin@ string in it with the path to your PHP command-line interpreter (usually /usr/bin/php).
** Replace the @php_bin@ string in it with the path to your PHP command-line interpreter (usually /usr/bin/php).
** For Windows: Replace the @php_bin@ string in it with the path to your PHP command-line interpreter and @bin_dir@ string with the path of the PHPunit directory.
** Copy it to a directory that is in your path and make it executable (chmod +x phpunit).  
** Edit your Path to inclulde PHPunit directory
** Make script runnable (chmod +x phpunit on Linux).  
* Prepare the PHPUnit/Util/PHP.php script:
* Prepare the PHPUnit/Util/PHP.php script:
** Replace the @php_bin@ string in it with the path to your PHP command-line interpreter (usually /usr/bin/php).
** Replace the @php_bin@ string if it exists in file it with the path to your PHP command-line interpreter (usually /usr/bin/php).
* Module xdebug can also be required if you plan to make reporting of test code covering.  
* Module xdebug can also be required if you plan to make reporting of test code covering.


=== Execute PHPUnit tests ===
=== Execute PHPUnit tests ===

Navigation menu