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


Out in the real world, in a production environment, is where your application gets really tested to its limits. Despite all the effort in developing test scenarios, and going through different stages of quality assurance, there will come a time when there are edge case scenarios that the development team or the quality assurance team might have not considered and, therefore, these missed edge case scenarios might cause bugs to occur. There are times when hardware-related issues will be encountered, or sometimes there will be some code-related performance bottlenecks causing timeouts and unhappy clients. It happens, but it’s not the end of the world. It would be great if the development team had access to a production environment’s usage statistics, the CPU or memory usage of the containers, the most accessed controllers, the stack trace of an exception, and so on.

Having this information will help you and your team resolve issues more quickly when they happen...