Cucumber steps for testing with Blimpy
Go to file
R. Tyler Croy 3c83069c9a It's unsafe to evaluate Dir.pwd everytime we want to generate a path to the work directory
We be changing dirs and shit
2012-09-03 12:20:08 -07:00
lib/blimpy It's unsafe to evaluate Dir.pwd everytime we want to generate a path to the work directory 2012-09-03 12:20:08 -07:00
.gitignore Ignore the rvmrc 2012-09-02 23:10:02 -07:00
Gemfile Add Rake to the gemfile for good measure 2012-09-02 23:09:42 -07:00
LICENSE Initial generation of the gem 2012-09-02 15:36:48 -07:00
README.md Remove some gem boilerplate from the readme 2012-09-02 16:04:45 -07:00
Rakefile Initial generation of the gem 2012-09-02 15:36:48 -07:00
blimpy-cucumber.gemspec Depend on a recent version of Blimpy 2012-09-02 16:08:04 -07:00

README.md

Blimpy for Cucumber

This gem helps incorporate Blimpy with Cucumber for integration testing with a VM running on any cloud that Blimpy supports.

Contributing

  1. Fork it
  2. Create your feature branch (git checkout -b my-new-feature)
  3. Commit your changes (git commit -am 'Added some feature')
  4. Push to the branch (git push origin my-new-feature)
  5. Create new Pull Request