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

Understanding and Organizing the Business Requirements of Our Project

Before writing a single line of code, we first need to understand the goals of a project and what problems we are trying to solve. We build software to solve problems, and if we do not adequately understand what the client or the business is trying to achieve, we will have problems coming up with the ideal solution—or, worse, we can end up spending months building software that doesn’t even address the business requirements.

As software developers, it is great to have a clear list of what needs to be built. It’s just like having a simple grocery list. This list will help us determine which features we need to develop or release first. So, before we start building solutions to a problem by writing software, we will try to come up with a simple example where we will try to interpret business problems and goals into a list of software features that we will need to write code for.

In this chapter...