Skip to end of metadata
Go to start of metadata
You are viewing an old version of this page. View the current version. Compare with Current  |   View Page History
HELP WANTED!
If you have written testing standards previously, please read the guidelines below, and help author testing standards for the Zend Framework.

Why use unit tests?

Components will not be included in Zend Framework releases without a reasonable collection of working unit tests. This includes incubator components.

Test Standard Goals

We are moving towards continuous integration and are looking at having a build/test server (build docs, api docs and run tests) responding on check-in similar to CruiseControl.

  • Sane defaults
    • default database names, usernames, passwords, etc. should not conflict with existing ones
    • desired [database] account restrictions and access should be included
    • include example database creation scripts for each of the tested database engines
    • reports produced in less than 15 minutes on typical systems
  • All tests work out of the box, with minimal configuration
  • Test startups and teardowns should be "smart" with persistent data, such that restarting the testing process works, regardless of possibly aborted previous tests.
  • Zend_Environment runs first (to determine if the environment meets minimum ZF requirements)

Zend Framework Testing Standards Best Practices

  • Zend Framework unit tests are written for PHPUnit.
  • By the end of the 2nd week of August, 2006, everyone should be using the new rollout of PHPUnit, version 3. See http://www.phpunit.de/wiki/SubversionRepository for download instructions.
  • If the new rollout of version 3 is not yet available above, then please use the latest available version of PHPUnit2 (requires PEAR). (Version 3.0.0alpha11 at the time of this writing.)
    • New install:
    • Upgrading:

Please contribute.

Labels:
None
Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.