Bugfix: various, Minor level internal change: outputs don't stack

Bugfixes:

• Output files now allow spaces (and other whitespace characters)
• Outputs will be converted to strings to avoid confusion
• Stub and wrapper internals now use command to allow for stubbing of bash, source, etc. (only restricted keywords are now command and function
• Outputs can now be to files with the names stderr and stdout for the bash based stub

Internal changes that prompted minor version change:

• Outputs no longer stack. Ex. stub.with_args('arg1').outputs('hello ') then stub.with_args('arg1').outputs('world') used to output 'hello world', now it will only output 'world'

Bugfix: bash stub ignoring certain characters set by outputs

0.2.1

bump version for 0.2.1 release

Performance improvements and support for absolute/relative path stubbing

• Adds performance improvements that decrease test run time by up to 50%
• Adds support for absolute and relative path stubbing for commands. Users can now stub commands like /usr/bin/nc or ./bin/my_command

Add "bugfix" to actually display differences

Differences for the argument matchers now actually return call details.

Example:

Expected first_command to be called with args ["not_first_argument", "second_argument"]

Expected Calls:
first_command not_first_argument second_argument

Actual Calls:
first_command first_argument second_argument
first_command first_argument second_argument third_argument

Integrate RSpec matchers

• Allow for traditional rspec matchers for stubbing calls and verifying output
• Allow for mocking commands with paths
• Fix bug when tests would fail when nothing was stubbed
• Update documentation to more clearly show usage

Initial gem release

v0.0.3

update homepage for gem

Initial gem release

0.0.3

Update README before creating gem