I am currently looking into DI for javascript objects, as well as phantom.js and jasmine-jquery to start putting together some examples for user journey testing and easier testing of jquery widgets and fixture loading.

With Node.js installed grab the following modules using npm

• coffee-script
• jasmine-node

Easiest way to get tests running type 'node ./spec.js ' at the command line, which is pointing to ./spec/ folder

In my BlogSpec.js file let's start with some basic tests

When you run the spec with : 'node-blog git:(master) ✗ node spec.js' the test should fail

So everything is as expected at this stage, let's start work on getting the basic tests to pass. First off let's create out Blog object

And not let's bring the Blog object into our test and initialise it:

Now let's get the first test to pass, by editing our Blog.js file

Nearly there, only problem is that our second test is failing because we require a title to not be null.

Let's see what the output looks like:

And just because I can, let's rewrite the Blog.js in Coffee Script:

How much terser is that?

• Use Git
• Build it using tests (Rspec)
• and conversely take a look at BBD
• Refactor common elements using partials
• Have fun

Heroku came along after the initial build because my server seemed to struggle serving the app using a combination of Apache and Passenger Phusion (looks like I need more RAM...). Overall the experience has simply put been great. Building an app using the Ruby and Rails toolset is just a pleasure. RVM for ruby version management, Bundler for Gem management, autotest for continuous background tests, easy deployment with Git integration. Compared to the CF world I am in [big caveat this might not be true for you], the rails ecosystm is incredibly rich, well documented, functional and fun.

I started off by following the Rails guide over at Rails Tutorial and borrowed the set up to get started. After creating my project, the first thing I got to grips with was getting Git set up. I use both a local repository and a remote one over at Github, Knowing that your code is versioned in two places is quite a comfort and I have since started using it for absolutely everything locally and have pushed a few other projects (terribly old projects that I am a little embarrassed about, but being the sentimental individual didn't want to loose) on to Github.

Then came setting up autotest, having this run in the background with Growl integration gives you instant notification that your tests are passing or failing whenever you save a file. This is so incredibly useful and responsive. I really love the continuous testing nature of this setup.

Given the nature of the site, the coding part was easy-ish and I am sure there are a plenty of things I have done like a noob.

Where all this really comes to shine is during deployment time. I opted for Heroku, it wasn't so much a choice as a case of I'd be stupid not to. The documentation for signing up and getting started is first class (as it is with Github by the way). Once you have your account, created your app and linked it to your git repository, deploying your code is a simple case of typing:

From then on in, you just watch the code being checked out, gem dependency being resolved and your app launching. Knowing that your site is Ok thanks to your tests, the one line deployment command is pure joy.

To give you an indication of how great this setup is, consider that I decided to switch from erb files to Haml. I spent a few hours reading up and converting my erb files over, while having autotest running showing me where things were breaking (due to my lack of knowledge of the new syntax) or working. Then pushing changes into Git. I confess I had also cast my eye over the resulting output (old habits die hard ) and finally running a one line deployment to Heroku. Job done and once again a pleasure and full of confidence about the result.

Where there any downsides? Well not downsides, but hiccups, wrapping my head around RVM and gem management was a bit bewildering especially when some gems were being used unexpectedly, the problem lay with what's between the chair and the keyboard. Some of the RSpec view testing tripped me up. When you decide to test the content of views, eg:

Don't forget to include render_views after your describe statement for the controller, or else your tests will fail and you will be be scratching your head as to why that is the case. :S

There's a lot to take in and it is a little overwhelming when things do not work as intended, but the information to resolve these is out there and with a careful reading of the error messages it does not take very long to figure out.

I also tidied up a few things in the code for rendering the CFCs and fixed an issue with the VarScopeChecker not being picked up by MXUnit.

As always feedback is most welcome!

1. cfUnit is now supported
2. A fix for cfmx 6.1 and recursive directory lookups
3. The code can now handle missing tearDown methods in existing test cfcs.

I have also tried to simplify the config.xml file a little and here's what the default looks like:

A concrete example usually works best, so:

appName : This now refers to a cf mapping in the administrator for my project, in this case art, however if you are using a package approach (with say a value of "com.domain"), then this value would simply be appended to the packageRoot (e.g. com.domain.art)

appPath : This is now the full path to the application, e.g. on my local machine /Users/gregstewart/Sites/Client X sites/Fusebox/ART2/

packageRoot : Hasn't changed

saveTestFilesTo : Hasn't changed

unitTestFramework : Now supports cfUnit.

coldSpring : Something working on, i.e. use ColdSpring to generate mock objects. Could be ages before it sees the light of day, if my past track record is anything to go by.

Thoughts and suggestions are still most welcome!

• Squidhead and CFUnit
• Stub Generator for CFCs, Unit Tests, and More

Both projects do a hell of a lot more than just create test objects though. Definitely worth checking out.

Feel free to comment here, use the forums or even log an issue with the tracker!