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

Unit Testing

Imagine working on a project without any automated tests with a few other developers, and everything seems to be working fine in production. Then, a bug has been discovered, and one of the developers fixes this bug. The QA department approves the fix and then is pushed to production. A few days later, another bug is reported in production. After investigation, the developers found out that the new bug was introduced by the fix for the other bug. Does that sound familiar?

One small change in the code base can easily change the behavior of software. A single decimal point change can cause millions of dollars worth of incorrect computations. Imagine handballing all these computation checks to the QA department for manual testing – they would have to run these checks every time something had been updated in the code base. It’s simply inefficient, stressful, and not sustainable.

One of the solutions to this recurring issue is unit testing. Writing unit...