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 started by creating an easy-to-understand list of features and scenarios detailing what needs to be built, based on a Jira ticket. Before working on the solution code, we first started with a Gherkin feature called Inventory Clerk Registration. This feature can be read by anyone—even non-developers will be able to understand it. This feature explains how our system should behave. We then took that behavior and created simple and failing functional tests inside the Symfony application. Creating these failing tests gave us a list of things we need to build. We then proceeded to develop the solution to pass these failing functional tests. And finally, we wrote code to tell Behat the intricate steps to click a link or a button, and fill up fields. BDD and TDD are not just about writing automated tests—it’s about using them as a process to develop our solutions.

In the next chapter, we will continue building tests and solution code. We...