In this blogpost, my thought was to gather some useful material on how to manage assets on a Symfony project by using the Assetic bundle.

As a project gets bigger, handling more and more assets can become overwhelming. Assetic can help us in organizing where the assets should load, combine multiple assets into a single file, compile assets (e.g. Less or Sass sources into CSS) and even optimize them e.g. by minification.


One of the things I find great about codebender is its large collection of hosted libraries and examples.
As this collection grows, we need to keep track the status of each example. If an example compiles successfully, its set of boards that it can compile against, the error that happened during compile in case of failure. It is a process that can be automated and we managed to do so with the help of Selenium.

Hello once more!

In this blogpost, I am going to talk about functional testing using the casperjs utility.

My previous article: Handling multiple sessions with Ace editor, resulted in an editor with support for some basic file operations (add/remove/rename file). In this article, I will demonstrate an example of how to test this page, with the help of casperjs. As before, you can reach the code at github.