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)
Part 1 – Technical Background and Setup
Part 2 – Implementing Test-Driven Development in a PHP Project
Part 3 – Deployment Automation and Monitoring


In this chapter, we defined what unit testing is by writing our own examples. We have gone through building and passing unit tests, as well as writing our own shell scripts to help us execute different automated test configurations to make it easier for us to debug or run test coverages. We’ve gone through what a test coverage report is, and how we can use it.

We’ve written our first integration test and configured our development environment so that we can also use a MySQL database. We’ve created a solution class that will perform the business logic that we need to pass the test, and we are also able to verify that what we persist in the database is what we have intended.

In this chapter, we tried to clearly define what a unit test and an integration test are, how they differ, and why we must separate them into their baskets or test suites.

In the next chapter, we will be talking about Behaviour-Driven Development (BDD). We will understand what...