davetron5000
commented
11 years ago The current Aruba steps only allow you to check if an option has documentation, but if you want to check behavior, you should be able to run the app and observe the output, e.g.
When I successfully run `my_app -e testing`
Then the output should contain:
"""
whatever might be output for -e testing
"""Not sure if that explains it, but with the Aruba tests, you are kinda limited to just testing things like output or standard error from your app. It kinda depends on what your app does in those situations.
Does that help?
Dave
Buy My Book: http://www.awesomecommandlineapps.com My Blog: http://www.naildrivin5.com/blog Fork me on Github: http://davetron5000.github.com
On Mon, May 13, 2013 at 9:01 AM, Roberto notifications@github.com wrote:
When using opt("-e environment", "--environment", "needed environment") I want to be able to reference an example So I don't drive myself insane trying to do it.
Basically I have an app that does not take arguments. I am using the options as a type of switch, it this option is defined and its value is not nill do this, else do this other thing. But I am having a hard time with aruba/cucumber testing this scenarion. I am aware that this can be done for arguments but I don't see anywhere where it can be done for options (in the wiki, the book, or the ibook)
— Reply to this email directly or view it on GitHubhttps://github.com/davetron5000/methadone/issues/66 .
Telmo
When using opt("-e environment", "--environment", "needed environment") I want to be able to reference an example So I don't drive myself insane trying to do it.
Basically I have an app that does not take arguments. I am using the options as a type of switch, it this option is defined and its value is not nill do this, else do this other thing. But I am having a hard time with aruba/cucumber testing this scenarion. I am aware that this can be done for arguments but I don't see anywhere where it can be done for options (in the wiki, the book, or the ibook)