mrdrmccoy / bblib Goto Github PK

test.sh currently does not perform proper unit testing. This issue is to re-write it using BATS.

Variable and function naming conventions are not complaint with the Google style guide for Bash at https://google.github.io/styleguide/shell.xml.

Add netcat functionality with Bash builtins /dev/tcp and /dev/udp.

Stack trace does not properly print commands in many cases.

From: https://stackoverflow.com/questions/49439994
In testing prunner, I have ended up with the following scenario:

• prunner -c "gzip -fk" *.out - works as expected in test.bash and interactively.
• find . -maxdepth 1 -name "*.out" | prunner -c echo -t 6 - works interactively, but not in test.bash.

Testing was performed on Ubuntu 16.04 with Bash 4.3 and on Mac OS X with Bash 4.4.

What appears to be happening with the latter in test.bash is that getopts is refusing to process -c, and thus prunner will try to directly execute the argument without the prefix command it was given. The strange part is that I am able to observe it accepting the -t option, so getopts is at least partially working. Bash debugging with set -x has not been able to shed any light on why this is happening for me.

Can anyone please help me to determine why -c options are not working correctly for prunner in test.bash when lines are piped to stdin?