PHP
downloads | documentation | faq | getting help | mailing lists | reporting bugs | php.net sites | links | conferences | my php.net


 

PEAR QA Continuous Integration and Unit Tests

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

PHPCS and General QA tools

How to test a new PEAR release

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 (1.7.0RC2 currently)
  2. Make sure you have the XML_RPC package
  3. Checkout pear-core from CVS to get the tests
  4. Run the tests
pear upgrade -f PEAR
pear upgrade XML_RPC
cvs -d :pserver:cvsread@cvs.php.net:/repository checkout 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.

Common pitfalls

  • 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

Unit tests

There are nightly unit test results published at http://lauken.com/doconnor/, you can find out more about integrating by reading the documentation.

 
pear/qa/ci.txt · Last modified: 2009/01/04 14:48 by clockwerx
 
Atom | show source | credits | stats | sitemap | contact | advertising | mirror sites