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 were able to come up with an example project based on a real-life problem that my friends encountered with a car museum. By trying to understand what the business or client wants to achieve, we were able to identify the problems or challenges that are stopping the business or client from achieving that goal. By analyzing our proposed solution to the problems, we were able to come up with plans for a solution. We listed down the solutions as user stories and grouped them under an epic.

These user stories tell us about behaviors—system behaviors, to be exact. Why are these important? Well, by understanding what we need to build, we developers can plan how we build solutions better. I have seen software being built for weeks or months, and after completion, the developers and business analysts realize that the solution does not even solve the problem that is stopping the business or the client from achieving its goal simply because the business analysts...