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

Summary

In this chapter, we defined and explained what BDD is and why we need it. By implementing BDD, we will be able to develop our solutions better to properly address the actual business goal. We can start defining these business goals using features and scenarios, written in the Gherkin language, which is just plain English. By doing so, different people from different teams in the company will be able to coordinate and understand each other better in defining the system’s intended behavior. This will help bridge the gap and language barrier between different teams.

We created a feature and a scenario, then used Behat, Mink, and Goutte to define the intended system behavior, open a headless browser, visit the web application, and verify the content of the home page.

This is just the tip of the BDD iceberg. In the next chapter, we will start writing solution code while making sure that our code is maintainable and testable by using BDD and TDD together.