qa:runtests:development
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| qa:runtests:development [2012/05/22 07:40] – [Getting the development version of parallel run-tests.php] zoe | qa:runtests:development [2017/09/22 13:28] (current) – external edit 127.0.0.1 | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ====== Setting up development environment ====== | ====== Setting up development environment ====== | ||
| run-tests.php is a PHP script so all you really need is a fairly standard development environment. This is a brief set of instructions. | run-tests.php is a PHP script so all you really need is a fairly standard development environment. This is a brief set of instructions. | ||
| + | If you just want to **run** the code this page is not for you - look [[http:// | ||
| ==== Installing PHP ==== | ==== Installing PHP ==== | ||
| Line 6: | Line 7: | ||
| * Extract into / | * Extract into / | ||
| * cd / | * cd / | ||
| - | * configure --with-zlib --enable-pcntl | + | * configure --with-zlib --enable-pcntl |
| * make | * make | ||
| * sudo make install | * sudo make install | ||
| - | This gets a recent copy of PHP installed in /usr/local. Note: you do not _need_ zlib, a couple of the unit test use it in testing the --GZIP_POST-- and --DEFLATE_POST-- sections. You can skip these tests with a configuration variable. You also only need pcntl for running tests in parallel. So, in fact your configure command here could be --disable-all. This woudl be enough to run the run-tests.php and its unit tests. | + | This gets a recent copy of PHP installed in /usr/local/ |
| ==== Installing other things ==== | ==== Installing other things ==== | ||
| - | The run-tests.php code is unit tested using PHPUnit. The unit tests can be run individually but teh easiest way to run them all is from a build.xml file drive by phing. | + | The run-tests.php code is unit tested using PHPUnit. The unit tests can be run individually but the easiest way to run them all is from a build.xml file driven |
| - | Code documentation is generated using Doxygen and test code coverage comes from Xdebug. | + | Code documentation is generated using Doxygen and unit test code coverage comes from Xdebug. |
| - | You don't need any of these things if all you want to do is run the code. You do need them if you want to make changes and test your changes. | + | You don' |
| So, in summary, install: | So, in summary, install: | ||
| Line 47: | Line 48: | ||
| ==== Checking that the code is working ==== | ==== Checking that the code is working ==== | ||
| - | The source code comes with a set of PHPUnit test cases and a QA test suite, all of this is controlled in a php build.xml file. | + | The source code comes with a set of PHPUnit test cases and a QA test suite, all of this is controlled in a build.xml file. |
| Before running the tests you **must set up a configuration file**. You will find phpdefinitions.txt.sample in the phpruntests directory. Copy it to phpdefinitions.txt and modify the settings to suit those on your system. | Before running the tests you **must set up a configuration file**. You will find phpdefinitions.txt.sample in the phpruntests directory. Copy it to phpdefinitions.txt and modify the settings to suit those on your system. | ||
qa/runtests/development.1337672449.txt.gz · Last modified: 2017/09/22 13:28 (external edit)