Book Image

Mastering Symfony

Book Image

Mastering Symfony

Overview of this book

In this book, you will learn some lesser known aspects of development with Symfony, and you will see how to use Symfony as a framework to create reliable and effective applications. You might have developed some impressive PHP libraries in other projects, but what is the point when your library is tied to one particular project? With Symfony, you can turn your code into a service and reuse it in other projects. This book starts with Symfony concepts such as bundles, routing, twig, doctrine, and more, taking you through the request/response life cycle. You will then proceed to set up development, test, and deployment environments in AWS. Then you will create reliable projects using Behat and Mink, and design business logic, cover authentication, and authorization steps in a security checking process. You will be walked through concepts such as DependencyInjection, service containers, and services, and go through steps to create customized commands for Symfony's console. Finally, the book covers performance optimization and the use of Varnish and Memcached in our project, and you are treated with the creation of database agnostic bundles and best practices.
Table of Contents (17 chapters)
Mastering Symfony
Credits
About the Author
About the Reviewers
Index

Getting started with BDD


Behavior-Driven Development (BDD) is a software development process introduced by Dan North to clarify the purpose of a development request and simplify acceptance tests. In BDD, you basically define a feature for a project in plain and human readable sentences and, when it is accepted by everyone, then you start creating the required code to implement that feature.

In contrast to this, in Test-Driven Development (TDD), it is not unusual to be carried away by many unnecessary tests. As you know, in TDD, you have to write a failing test first and then develop the code to pass the test. The question is how would you know that you are heading in the right direction? In other words, how can you be sure that the test you have created in the first place is beneficial to your project? Yes, of course, you can do things right by creating those tests first. However, doing things right is totally different from doing right things. Again, it is all about the money and your client...