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

Building Solution Code with BDD and TDD

Now that we have gone through the fundamentals of writing test programs using test-driven development (TDD) and behavior-driven development (BDD), we can start using both processes in developing our example application. When working on commercially successful and large-scale applications, one thing is common: they all need maintenance. There will always be room for improvement in terms of the product’s functionality. There could be some bugs that were missed, and—more commonly—more features to improve the product will continuously be added to the application. This is usually how badly written code gets worse. A nicely written class can end up being a god class: a class that can do everything with a few thousand lines of code. A developer can start writing additional functions inside the god class while another developer is using that class, therefore changing the class’s behavior. You can guess what happens next! A...