Testing

Unit Testing

We use phpunit for unit testing
Tests are definied in /tests (mainly application)
phpunit.xml defines the configuration, including codecoverage
phpunit.travis.xml runs phpunit, without codecoverage

phpunit --configuration tests/phpunit.xml

Continuous integration

We use Travis-CI for continuous integration testing: each push to the Github repository triggers a build that executes PHP unit tests.

• The test configuration is specified in .travis.yml
• The test suite is defined in tests/phunit.travis.xml (and excludes code coverage reporting, to make the test suite run fast)
• Test results are available via https://travis-ci.org/#!/Nivocer/webenq
• The repository on Github has a status image indicating the results of the last run.

We're currently testing on PHP versions:

• 5.3 (last travis-subversion)
• 5.3.3 (nivocer server)
• 5.4
• 5.5

Skipping a CI test

In order to skip a build by Travis, add the following to the commit message:

Checking the Travis config

With travis-lint, it's possible to check the configuration before deploying it: https://github.com/travis-ci/travis-lint

Testing coding guidelines

We use codesniffer to test the guidelines according to a (old) zend guideline.
phpcs.sh runs the tests, we have excluded applicatation/models/base, because it is generated by doctrine

Testing complexity of code

we use pdepend to test the complexity of the code
it results in:

• pdepend.php:
• overview of file/packages/classes with the statistics
• pyramid.svg 3 parts:
• top: inheritance
• left: balans in use of methods/classes/packages
• right: balans: loosely/tightly coupled of code: reusable/reused.
• jdepend.svg:
• hierarchy of the code with methods, within classes, within packages

Testing coding guidelines/complexity of code

Apart from codesniffer and pdepend, we use messdetector to get information about coding guidelines/complexity
phpmd.sh runs the tests

Testing for duplicate code

We are (going to) use duplicate code checker to check for duplicate code. It is an indicator that code is not reused proberly.
@todo script which runs the tests.

Daily build

We run a test server at http://test4.webenq.org/tests featuring PHP 5.4 and Java 6.

Each night, it gets the latest version from Github and runs the complete testsuite

• The directory application/models is currently excluded from code coverage reporting to make it fit into the 400MB memory of the (virtual) server (Amazon t1.micro).
• see if process isolation can improve performance (results in errors now)