Path: | README.rdoc |
Last Update: | Mon Apr 25 17:28:19 +0000 2011 |
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 (e.g. env.rb)
require 'aruba/cucumber'
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).
Aruba has tags you can put on on individual scenarios, or on a feature.
To get more information use these tags:
To prevent Aruba from removing its working directory before each scenario:
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
Set @aruba_timeout_seconds to control the amount of time Aruba will wait for a process to finish running before terminating it:
Before do @aruba_timeout_seconds = 5 end
Running processes interactively can result in race conditions when Aruba executes an IO-related step but the interactive process has not yet flushed or read some content. To help prevent this Aruba waits before reading or writing to the process if it is still running. You can control the wait by setting @aruba_io_wait_seconds to an appropriate value. This is particularly useful with tags:
Before('@slow_process') do @aruba_io_wait_seconds = 5 end
Copyright (c) 2010 Aslak Hellesøy and David Chelimsky. See LICENSE for details.