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

Why bother with Gherkin, then?

The example we used in this chapter is very simple, but you might be tempted to think that we can just skip the features written in the Gherkin language. Well, I did that too. I thought: it’s not that useful. But when I started working on bigger projects, with bigger teams, with different companies working collaboratively on the same project and goal, I thought to myself: I wish there were a common format that we could share so that we all understand what the business is trying to achieve. I was working collaboratively with a third-party company, and I wanted to ask them whether I could borrow or get a copy of their test cases, but the thing is, they wrote down their test cases directly into their application, which is not written in PHP. I then realized how important it is to have some sort of a common language that we can use to understand the intended behavior of a system that is programming-language agnostic!

The following diagram represents...