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

Polymorphism with a PHP interface

A PHP interface is a simpler version of a PHP abstract class. An interface cannot have properties like a normal class can, and it can only contain publicly visible functions. Each method in an interface must be implemented by any class that uses the interface but without the need to add the abstract keyword. Therefore, we must be very careful when declaring functions to an interface. It’s very easy to end up having an interface with too many functions that it doesn’t make sense for each implementing class to use. This is where the Interface Segregation Principle comes in to help, and this will be discussed more in Chapter 8, Using TDD with SOLID Principles.

Imagine that you need a program to return results in different formats, and you’d also like to be able to isolate the logic and dependencies to come up with the desired results. You can use an interface to set a contract that will be followed by your objects. For example...