Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support for parameters #26

Open
dhoer opened this issue Feb 4, 2018 · 3 comments
Open

Support for parameters #26

dhoer opened this issue Feb 4, 2018 · 3 comments

Comments

@dhoer
Copy link

dhoer commented Feb 4, 2018

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.

@dhoer
Copy link
Author

dhoer commented Feb 4, 2018

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.

@dhoer
Copy link
Author

dhoer commented Feb 6, 2018

I'm not sure why adding prompt for password would make the test pass, but it did: https://gist.github.com/83b5b44e6c2e9520852112a2d72e33c5.

@ferventcoder
Copy link
Contributor

Agreed. That is weird, unless in doing so you may have snuck an emtpy default password in.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants