You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am writing a library that will handle our configuration management. Part of what I need to test is setting those options from the command line... its a standard part of input for this library and critical for a properly tested package. So is there a mechanism to send command line switches not to behave, but to the package behave is testing? This is a pretty critical piece of testing for most programs I write.
The text was updated successfully, but these errors were encountered:
Can you describe the way you'd like to use Behave to test the CLI behavior of your application?
It really depends on that. Behave is just a test runner. How you implement your tests is a different story.
For example, you may want to take a look at cli-test-helpers for ready-to-use test setups if you're fine to run unit tests. You can use the ideas to test a CLI from there too, and use (nearly) the same test code in your step implementations, if you prefer to stick to Behave.
behave4cmd0 in own repo (WIP): https://github.com/behave/behave4cmd0
NOTE: There may be some setup steps need to be able to use it (setup where the root-directory is).
NOTES:
Questions are normally asked under discussions and not under issues.
I am writing a library that will handle our configuration management. Part of what I need to test is setting those options from the command line... its a standard part of input for this library and critical for a properly tested package. So is there a mechanism to send command line switches not to behave, but to the package behave is testing? This is a pretty critical piece of testing for most programs I write.
The text was updated successfully, but these errors were encountered: