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

Browser emulators and Mink

Browser emulators are programs that emulate or mimic the functionalities and behaviors of a web browser. These emulators can then be used by another program, such as Behat or Codeception, to simulate what a real user would do on a web browser while using your application.

There are two types of browser emulators:

  • Headless: These types of emulators fire HTTP requests and simply listen for the returned DOM or response from the web application. They will be best suited for lightweight testing, without the need for complicated checks such as checking for an AJAX response after a mouseover event.
  • Controllers: These types of emulators use real browsers, and they basically act like a person who controls a real browser. The good thing about using these types of emulators, in my experience, is that we can set the type of browser we want to test with. We can also check for the JavaScript and AJAX results on a page.

In our example, we will use...