PHP Unit Testing with PHPUnit

Install PHP

Install a Code Editor

Install PHPUnit as a PHP Archive File

Install PHPUnit Using Composer

Write Your First Test

Testing Application Code: Test a Function Defined in a Separate File

Test Each Aspect of the Code: Write Multiple Test Methods

Testing Application Code: Test a Class Defined in a Separate File

Controlling the Test Runner Output: Colours, Testdox and More

Running a Script Before the Tests are Executed: the Bootstrap Script

Add an Autoloader to Load Classes Automatically

Using Composer's Autoloader to Load Classes and Functions

The PHPUnit Configuration File: phpunit.xml

Running Multiple Tests: Organising Tests Into Test Suites

Running Individual Tests with Filters

Two Ways of Marking Methods as Test Methods

Add a Test but Mark It to Be Implemented Later

Fixing a Bug Through Testing: The Difference Between Errors and Failures

Simplifying Tests with Test Method Arguments and Data Providers

Unit Test a Queue Class: Multiple Assertions in a Single Test Method

Test Dependencies: Make a Test Method Dependent on Another

Fixtures: Set Up the Known State of the Tests Using setUp and tearDown

Easily Add a New Test Method When Fixtures are Being Used

Testing Exceptions: Expecting Code to Throw an Exception

Unit Testing Classes in Isolation: An Introduction to Test Doubles

Dependency Injection: Inject Objects That a Class Depends On

Test Doubles: Create and Configure Test Stubs

Expecting and Handling Exceptions in Test Stubs

Use Mocking to Assert Test Double Behaviour

Customise the Test Double Generation with the getMockBuilder Method

Set Up a Project for Test-Driven Development

Start TDD: Write a Test First, Then Write the Code to Make it Pass

Include Refactoring in The TDD Process

Add Another Test Class To Satisfy a Design Requirement

Rewrite Code To Make Additional Tests Pass

Add Further Tests to Drive the Development of Additonal Functionality

Install a Code Coverage Driver

Configure Your Development Environment So PHPUnit Can Use Xdebug

Configure PHPUnit With the Location of the Project Source Code

Generate Code Coverage Reports in Different Formats

Add Tests to Increase Coverage Based on the Report

Non-Public Methods: Should They Be Tested?

Testing Non-Public Methods Using Inheritance

Testing Non-Public Methods Using Reflection

Testing Protected Properties Using Reflection

Testing Abstract Classes

Unit Test a Static Method

The Problem with Static Methods: Dependencies and Test Doubles

Refactor Code to Remove the Static Method Call

Inject the Static Method Call as a Dependency Using a Closure

Installation of Mockery and Integration with PHPUnit

Comparing Mock Objects: PHPUnit vs Mockery

Using Mockery to Mock a Dependency that Doesn't Exist Yet

Multiple Method Calls: Returning Different Values with Different Argumen

Use Mockery Alias Mocks to Stub a Static Method Call

Mockery Spies: Verify Test Double Method Calls After They Happen

Conclusion