I've started writing integration tests for the rake tasks. Specifically there are scenarios for running 'rake test:javascripts' on: a rails project, a non-rails project, and on blue-ridge itself. With integration tests this will allow us to explore alternate compositions of technology (say trialling htmltest instead of env.js + rhino, or switching out screw.unit for jspec or whatever), but make sure that the core generators and headless test rake tasks keep working.
If you want the cucumber specific changes only, let me know, else hopefully you can pull in all the changes (some which solve other issues such as #14)
I've started writing integration tests for the rake tasks. Specifically there are scenarios for running 'rake test:javascripts' on: a rails project, a non-rails project, and on blue-ridge itself. With integration tests this will allow us to explore alternate compositions of technology (say trialling htmltest instead of env.js + rhino, or switching out screw.unit for jspec or whatever), but make sure that the core generators and headless test rake tasks keep working.
This work is in a "features" branch (http://github.com/drnic/blue-ridge/tree/features) though this branch also includes all my other commits and merged commits from other people's branches.
If you want the cucumber specific changes only, let me know, else hopefully you can pull in all the changes (some which solve other issues such as #14)