Setting a Symfony2 project up for testing can be tricky, however in this short guide I will show you how you are able to setup your project so you can spend more time coding and less time trying to fix issues you run into while setting up a testing environment.
If you are like me, I hate having a lot of extra stuff on my laptop such as mysql, apache/nginx, etc. All those extra services are such a pain in the ass to maintain and other developers may have different versions of the same things. This can lead to issues during development and has the
Symfony 2 has an amazing Form Component, however it is very complex and most users will have a hard time understanding the component. In the future I suspect that there will be more data mappers that you can use along with an easier way to configure these by creating a service and telling the configuration
So recently I have been playing a lot with phing, symfony2, and Jenkins. Today I will show you how to build a very basic build script that runs phpunit. Future articles I will show you how to add to your build script to generate documentation and eventually integrate it all into Jenkins.
So I have been playing with [Vagrant](http://www.vagrantup.com/), [Puppet](https://puppetlabs.com/), and [Symfony](http://symfony.com/) for about the past month or so. There have been a few issues that I have run into, but it has mostly been a joy to work with.