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

More about the acceptance test flow in Mink


As you saw in the previous topic, an acceptance test with Mink is all about finding elements in a page and checking to see whether they do what is expected from them. Behind the scenes, there are four important Mink objects that carry a lot of heavy lifting for us:

  • Driver: The Driver class implements Behat\Mink\Driver\DriverInterface, and Mink deals with every browser emulator or browser controller through this interface. We have two drivers installed in our project (Goutte and Selenium2), but keep in mind that the current version of Mink comes with five drivers out of the box.

  • Session: Controlling the browser happens through the Session object. This is where Mink sends HTTP requests and listens for responses.

  • DocumentElement: This is the actual web page containing all the page elements.

  • NodeElement: Through this object, you can access and manipulate all the elements in a page.

In general, the acceptance test workflow looks something like this: