With these few examples, you should know enough to start automating tests for your own command-line applications. Let’s review what we have learned:
Command-line applications all look the same from the outside, whatever language they’re written in.
We can verify that a command-line application prints what we expect it to print.
We know how to check that a command-line application exits with a specific exit status.
You can create temporary files that the command-line application you are testing can use.
Aruba uses an empty, temporary directory for each scenario.
Aruba recognizes special tags that let us see more informative output.
We can use Aruba to interact with simple command-line applications that ask for user input. ...