This handy guide answers all your PHPUnit questions, and then some. Written by the tool’s creator, PHPUnit Pocket Guide delivers insight and sage advice not found anywhere else. It brings together hard-to-remember information, syntax, and rules for working with this popular code-testing tool. Perfect for developers of any level.
Book Description
Even good programmers make mistakes. The difference between a good programmer and a bad programmer is that the good programmer uses tests to detect his mistakes as soon as possible. The sooner you test for a mistake the greater your chance of finding it and the less it will cost to find and fix. This explains why leaving testing until just before releasing software is so problematic. Most errors do not get caught at all, and the cost of fixing the ones you do catch is so high that you have to perform triage with the errors because you just cannot afford to fix them all.
Testing with PHPUnit is not a totally different activity from what you should already be doing. It is just a different way of doing it. The difference is between testing, that is, checking that your program behaves as expected, and performing a battery of tests, runnable code-fragments that automatically test the correctness of parts (units) of the software. These runnable code-fragments are called unit tests.
Table of Contents
- Automating Tests
- PHPUnit’s Goals
- Installing PHPUnit
- Writing Tests for PHPUnit
- The Command-Line Test Runner
- Fixtures
- Organizing Tests
- TestCase Extensions
- Database Testing
- Incomplete and Skipped Tests
- Test Doubles
- Testing Practices
- Test-Driven Development
- Behaviour-Driven Development
- Code Coverage Analysis
- Other Uses for Tests
- Skeleton Generator
- PHPUnit and Selenium
- Logging
- Extending PHPUnit