A multi-environment, multi-runner JavaScript testing tool.
Go to file
John Bintz e101321c58 have the option for running code after step writer completes 2012-04-18 17:02:23 -04:00
bin whoa the tests are working again 2012-03-24 10:17:33 -04:00
config whoa the tests are working again 2012-03-24 10:17:33 -04:00
features whoa the tests are working again 2012-03-24 10:17:33 -04:00
lib have the option for running code after step writer completes 2012-04-18 17:02:23 -04:00
skel/cucumber make it possible to bootstrap a cucumber config, handle tables and strings in cucumber tasks 2012-03-17 17:54:23 -04:00
spec whoa the tests are working again 2012-03-24 10:17:33 -04:00
vendor/assets/javascripts still fllailing away 2012-03-08 08:54:27 -05:00
.gitignore gitignore for gh-pages leftovers 2012-03-20 17:15:47 -04:00
Gemfile changes and junk 2012-03-21 12:21:00 -04:00
Guardfile whoa the tests are working again 2012-03-24 10:17:33 -04:00
LICENSE yeehaw! 2012-02-22 11:47:07 -05:00
README.md yeehaw! 2012-02-22 11:47:07 -05:00
Rakefile yeehaw! 2012-02-22 11:47:07 -05:00
flowerbox.gemspec whoa the tests are working again 2012-03-24 10:17:33 -04:00

README.md

Flowerbox

TODO: Write a gem description

Installation

Add this line to your application's Gemfile:

gem 'flowerbox'

And then execute:

$ bundle

Or install it yourself as:

$ gem install flowerbox

Usage

TODO: Write usage instructions here

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