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
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.
The text was updated successfully, but these errors were encountered:
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.
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.The text was updated successfully, but these errors were encountered: