Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Starting to cover blue-ridge with cucumber integration tests #19

Open
drnic opened this issue Jul 27, 2009 · 1 comment
Open

Starting to cover blue-ridge with cucumber integration tests #19

drnic opened this issue Jul 27, 2009 · 1 comment
Labels

Comments

@drnic
Copy link

drnic commented Jul 27, 2009

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)

@karnowski
Copy link

I've had a few people (most notably David Chelimsky & Chad Humphries) recommend this strategy too. I'll definitely take a look.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants