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

Writing tests and solution code for the example project

Back in Chapter 2, Understanding and Organizing the Business Requirements of Our Project, we used Jira as a tool to organize the list of things we need to build for the project. Aside from using Jira, there is other project tracking software out there too, or we can just simply use a notepad or a piece of paper and write down the tasks we want to write programs for. But we just want to be a bit more organized, and if you’re working with a team of software developers and with other teams in the company, it’s easier to collaborate if you use issue-tracking software, rather than a piece of physical paper.

We have grouped the Jira user stories into two groups: the Inventory Clerk Solution group and the Visitors Page group. These groups are called epics. We will start working on the Inventory Clerk Solution epic first. This is to allow the car museum inventory clerk to enter that valuable data into the system for...