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

TDD and BDD with Codeception


Now is a good opportunity to see Codeception and our understanding of TDD and BDD in action. To implement a maintainable code, we are going to follow these three steps:

  1. First, we create a failing functional test (a scenario) that summarizes our expectations of the application. This means that according to the business logic, we need to see an overall function related to each entity. So we will create actions that, without worrying about what they will have inside, simply return a desired response.

  2. Next, we create a failing unit test and assess the legitimacy of the response created from step one. In other words, we test the logic in each action to make sure that the generated response is accurate.

  3. Finally, we create acceptance tests to see if the tests created from the first two steps satisfy the application performance from the end user's point of view. In this step, we see the results in a browser, and we can see how our application interacts with JavaScript codes...