Unit testing involves testing individual units of code to ensure they function as intended. Unit tests isolate and test each part of a program to show they are correct. Benefits of unit testing include finding problems early, facilitating change, simplifying integration, and serving as living documentation. PHPUnit is a popular unit testing framework for PHP, which can be installed via PEAR. Tests are written to make assertions and test exceptions, data, and dependencies. Results can be logged in verbose mode or testdox format.

1. Back to basics
Sebastian Marek

2. What is a unit test?
In computer programming, unit testing is a method by
which individual units of source code are tested to
determine if they are fit for use. A unit is the smallest
testable part of an application.
http://en.wikipedia.org/wiki/Unit_testing

3. For whom?
Unit tests are typically written and run by software
developers to ensure that code meets its design and
behaves as intended.
http://en.wikipedia.org/wiki/Unit_testing

4. What for?
The goal of unit testing is to isolate each part of the
program and show that the individual parts are correct. A
unit test provides a strict, written contract that the piece
of code must satisfy. As a result, it affords several
benefits. Unit tests find problems early in the
development cycle.
http://en.wikipedia.org/wiki/Unit_testing

5. Benefits
● Facilitates change
● Simplifies integration
● Living documentation
● Early design

6. Installing PHPUnit
#> pear channel-discover pear.phpunit.de
#> pear channel-discover components.ez.no
#> pear channel-discover pear.symfony-project.com
#> pear install phpunit/PHPUnit
#> phpunit –version
PHPUnit 3.5.11 by Sebastian Bergmann.

7. Managing tests

8. Writing tests
● assertions
● testing exceptions
● data providers
● test dependencies
● test fixtures
● stubs
● mock objects

9. Logging results
● verbose mode
● testdox format
● test results
● code coverage results

10. PHPUnit configuration file
● bootstrap file
● process isolation
● including and excluding files for code coverage
● logging

11. Resources
● http://www.phpunit.de/manual/current/en/index.html

12. Q&A
?