As an example of getting Autotest, Cucumber, and Growl up and running I’ve created a super simple test project. You can download the example project, or just create it from the code on this post.
Following on to my previous post on Autotest, Cucumber, and Growl, I have forked the autotest-growl repository, and applied my fix for Cucumber notifications.
You find my patched version of autotest-growl on GitHub.
You can switch to this version of autotest-growl by uninstalling any existing version, and then installing from my fork on GitHub:
sudo gem uninstall autotest-growl sudo gem install karl-autotest-growl --source http://gems.github.com
As well as using Autotest to run Cucumber scenarios I have also been looking into integrating lower level test into the Autotest cycle.
*.js files in the project, outputs the results to the autotest results object and the standard output, and finally fires a new
Autotest is a great Ruby tool to speed up test driven development by automatically running your tests every time a file is saved.
Cucumber is an awesome tool for doing behavioural driven development. It allows you to write plain text automated acceptance tests.
Autotest and Cucumber work together seamlessly, you just need to set the
AUTOFEATURE environment variable to true:
You can add Growl support to Autotest (using the autotest-growl gem) so that you get popup notifications of test results.
But the current version of autotest-growl doesn’t provide notifications for the result of Autotest Cucumber runs.