Book Image

Test-Driven Development with PHP 8

By : Rainier Sarabia
Book Image

Test-Driven Development with PHP 8

By: Rainier Sarabia

Overview of this book

PHP web developers end up building complex enterprise projects without prior experience in test-driven and behavior-driven development which results in software that’s complex and difficult to maintain. This step-by-step guide helps you manage the complexities of large-scale web applications. It takes you through the processes of working on a project, starting from understanding business requirements and translating them into actual maintainable software, to automated deployments. You’ll learn how to break down business requirements into workable and actionable lists using Jira. Using those organized lists of business requirements, you’ll understand how to implement behavior-driven development (BDD) and test-driven development (TDD) to start writing maintainable PHP code. You’ll explore how to use the automated tests to help you stop introducing regressions to an application each time you release code by using continuous integration. By the end of this book, you’ll have learned how to start a PHP project, break down the requirements, build test scenarios and automated tests, and write more testable and maintainable PHP code. By learning these processes, you’ll be able to develop more maintainable, and reliable enterprise PHP applications.
Table of Contents (17 chapters)
1
Part 1 – Technical Background and Setup
6
Part 2 – Implementing Test-Driven Development in a PHP Project
11
Part 3 – Deployment Automation and Monitoring

Implementing the Red-Green-Refactor pattern

The Red-Green-Refactor pattern is a type of programming approach to implementing TDD. It’s a cycle where you first deliberately write a failing test, in which you see a red-colored failing message when you execute the test. Then, you write solution code to pass that test, in which you will see a green-colored passing message. After passing the test, you can then go back to clean up and refactor your test and solution code.

If you open the codebase/symfony/runDebug.sh file that we created earlier in this book in Chapter 5, Unit Testing, you’ll notice that we are running PHPUnit by adding the --color=always parameter. Then, whenever we run PHPUnit and we get a failing test, you will notice that we always get a red error or failed test message.

To demonstrate the pattern clearly, let’s go through an example:

  1. Create a new file called HelloTest.php:

codebase/symfony/tests/Unit/HelloTest.php

<?php...