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

PHP Standards Recommendations (PSRs)

As mentioned earlier, there are a lot of open source libraries and frameworks built for PHP. Each individual developer will have their own preferences in their style of writing codes, and each framework or library can have its own standard or way of doing things. This can start to become problematic for PHP developers, as we tend to use a lot of different libraries and frameworks.

For example, it’s no fun transitioning from one framework to another only to end up having different types of service containers, which will require you to change the way you organize the dependencies for your application, and therefore PSR-11 was introduced. Service containers are applications that manage the instantiation of objects including their dependencies—they are very handy when implementing Dependency Injection or DI, which is discussed in Chapter 8, Using TDD with SOLID Principles. This is one of the examples of why it is important, although...