Open dhoer opened 6 years ago
Another approach could be a yaml file that would allow for more sophisticated control over test configuration and execution. I put this out there to make sure that other options are taken in consideration. But I like the simpler properties approach for now, since it should be trivial to implement.
I'm not sure why adding prompt for password would make the test pass, but it did: https://gist.github.com/83b5b44e6c2e9520852112a2d72e33c5.
Agreed. That is weird, unless in doing so you may have snuck an emtpy default password in.
While it is desirable to not require parameters, sometimes it is necessary. I have a package that requires a password and there is no way to pass that information to test environment.
I would like to propose support for a properties file e.g.,
tools\choco_test.properties
that is optional and would be converted to--params "''"
automatically before executing the command.