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)
1
Part 1 – Technical Background and Setup
6
Part 2 – Implementing Test-Driven Development in a PHP Project
11
Part 3 – Deployment Automation and Monitoring

Applying BDD using Behat and Gherkin

To help us easily understand what BDD is and how it is used, we will try to apply it to example scenarios in a project.

Going back to Chapter 2, Understanding and Organizing the Business Requirements of Our Project, we have created some Jira tickets to help us break down the features that we need to build. Within the Inventory Clerk Solution epic, we have created a user story with the following title:

As an inventory clerk, I want to be able to log in to the system so that I can access the inventory system.

With this user story, we can deduce that we will need a user for the application and that user will need to be able to authenticate themself so that they can access a restricted feature.

So, usually, as software developers, we’ll then go ahead and start building the solution code for that– write code, then check the results from the controller or web page we just created. We won’t be doing that.

With BDD...