It depends on the criticality of your command line tools. One
interessting approach is the one by the SpringBoot guys. They run
commands in a Docker container and collect stdout to check the behaviour
of their System V start script.
=>
Have you considered writing an integration test that invoked your command
line tool from the command line?
When you use tools like Failsafe, JUnit, etc, you can know that the process
works in that environment, but the real world execution won't be the same.
While most of your corner cases,
When writing integration tests for command-line tools, is there any
support in Failsafe, jUnit, or elsewhere to fork a process and manage
its standard IO streams?
Or am I over-designing? Would one typically write such an integration
test rather like a unit test, bypassing the command analyzer
mvn dependency:tree -Dinclude=group:id seems to print the whole tree and not
the only path to my target dep.
Sometimes the tree is big, is there a way to filter?
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For