Cucumber steps for driving out command line applications. The command line application can be anything, a compiled C program, a Java program, a Perl script - anything.
gem install aruba
Then, just require the library in one of your ruby files under features/support
You now have a bunch of step definitions that you can use in your features. Look at aruba/cucumber.rb to see all the step definitions. Look at features/*.feature for examples (which are also testing Aruba itself).
Getting more output with tags.
Aruba has several tags you can use to get more information. You can put these tags on individual scenarios, or on a feature. The tags are:
@announce-cmd - See what command is is run
@announce-stdout - See the stdout
@announce-stderr - See the stderr
@announce-dir - See the current directory
@announce-env - See environment variables set by Aruba
@announce - Does all of the above
Configuring the working directory
Per default Aruba will create a directory tmp/aruba where it performs it's file operations. If you want to change this behaviour put this into your features/support/env.rb:
Before do @dirs = ["somewhere/else"] end
Note on Patches/Pull Requests
Fork the project.
Make your feature addition or bug fix.
Add tests for it. This is important so I don't break it in a future version unintentionally.
Commit, do not mess with rakefile, version, or history. (if you want to have your own version, that is fine but bump version in a commit by itself I can ignore when I pull)
Send me a pull request. Bonus points for topic branches.
Copyright © 2010 Aslak Hellesøy and David Chelimsky. See LICENSE for details.