Book Image

Mastering PHP Design Patterns

By : Junade Ali
Book Image

Mastering PHP Design Patterns

By: Junade Ali

Overview of this book

Design patterns are a clever way to solve common architectural issues that arise during software development. With an increase in demand for enhanced programming techniques and the versatile nature of PHP, a deep understanding of PHP design patterns is critical to achieve efficiency while coding. This comprehensive guide will show you how to achieve better organization structure over your code through learning common methodologies to solve architectural problems. You’ll also learn about the new functionalities that PHP 7 has to offer. Starting with a brief introduction to design patterns, you quickly dive deep into the three main architectural patterns: Creational, Behavioral, and Structural popularly known as the Gang of Four patterns. Over the course of the book, you will get a deep understanding of object creation mechanisms, advanced techniques that address issues concerned with linking objects together, and improved methods to access your code. You will also learn about Anti-Patterns and the best methodologies to adopt when building a PHP 7 application. With a concluding chapter on best practices, this book is a complete guide that will equip you to utilize design patterns in PHP 7 to achieve maximum productivity, ensuring an enhanced software development experience.
Table of Contents (14 chapters)
Mastering PHP Design Patterns
Credits
About the Author
About the Reviewer
www.PacktPub.com
Preface

Tester-Driven Development


This is a tongue-in-cheek reference to Test-Driven Development (TDD). TDD is a software development strategy largely revolving around using development tests to drive implementation towards fulfilling the requirements.

Tester-Driven Development, however, is where the requirements are the shortcut and it becomes the case that the software team starts specifying the requirements through bug reports. Tester-Driven Development can also be referred to as Bug-Driven Development as it essentially results in bug reports being used to specify actions and features that developers should implement.

For example, a developer builds a tool to export data from a database to a spreadsheet. It works perfectly, but a tester still comes back and raises a ticket saying that there is a bug in the product; they say that it doesn't contain the ability to export to PDF. If this wasn't in the requirements it shouldn't be raised as a bug. And yes, you should have requirements.

QA teams and...