PEAR QA Continuous Integration and Unit Tests

There are a number of tools qa use to maintain quality.

http://test.pear.php.net/ hosts continuous integration tools

• Pearweb test installation
• Test results overview
• Jenkinsl
• Migrate to github script

The helper scripts live at http://svn.php.net/viewvc/pear/ci/phpuc/trunk/

Jenkins is a continuous integration platform. Currently, all packages in both PEAR and PEAR2 are built by it.

In general, we encourage the use of an AllTests.php - we target PHPUnit 3.4 at this time.

Your package directory layout should allow you to successfully run your test suite as below:

$ cd Foo_Bar/trunk
$ php tests/AllTests.php

... or as per the phpunit command above.

http://jenkins-php.org/ is also worth a look.

A common pattern with older packages is to have a directory structure which is unlike the installed package layout. IE: Foo_Bar/trunk/Bar.php. Most authors make use of the baseinstalldir attribute in the package.xml, or only run tests after installation

To fix this:

$ svn mkdir Foo
$ svn mv Bar.php Foo/
# Edit package.xml, change baseinstalldir to /
$ vim package.xml
 
# Rebuild package using PEAR_PackageFileManager_CLI
$ pfm
 
# Run tests to confirm no fatal errors, using one of
$ php tests/AllTests.php
$ pear run-tests -r tests/
$ phpunit tests/
 
# Commit
$ svn commit -m "Updated directory layout"

See migration

Two strategies exist for this: - Making use of PHPUnit's mocking capabilities or utilising something like HTTP_Request2's Mock Adapter - Checking your environment and skipping the test if it cannot run

1. Put more packages into jenkins
2. Investigate a notification task to package maintainers?
3. Investigate allowing bootstrapped build.xml files back in (Pyrus)
4. Upgrade PHP on test.pear.php.net
5. Install xdebug for proper code coverage

Before releasing a new version of PEAR, we need to make sure it runs on as many systems as possible. It's pretty easy:

1. Install the new PEAR
2. Make sure you have the XML_RPC package
3. Checkout pear-core from the repository to get the tests
4. Run the tests

pear upgrade -f PEAR
pear upgrade XML_RPC
svn co http://svn.php.net/repository/pear/pear-core/trunk pear-core
cd pear-core/tests && pear run-tests -r

Tell pear-qa@lists.php.net if you got failures, and if, which tests did not pass. We will come back to you in that case.

• Make sure that PHP is compiled with tokenizer support (--enable-tokenizer). On most systems this is default, but on Gentoo Linux for instance, you need to enable the tokenizer USE flag.
• For some tests the executable php-cgi is needed. In some Linux distributions this is contained in a separate package, but on for instance Gentoo Linux this has to be enabled using the cgi USE flag.
• If running on linux, do not run the tests as root