I have a shell script that I would like to test with shUnit. The script (and all the functions) are in a single file since it makes installation much easier.
Example for script.sh
#!/bin/sh
foo () { ... }
bar () { ... }
code
I wanted to write a second file (that does not need to be distributed and installed) to test the functions defined in script.sh
Something like run_tests.sh
#!/bin/sh
. script.sh
# Unit tests
Now the problem lies in the .
(or source
in Bash). It does not only parse function definitions but also executes the code in the script.
Since the script with no arguments does nothing bad I could
. script.sh > /dev/null 2>&1
but I was wandering if there is a better way to achieve my goal.
Edit
My proposed workaround does not work in the case the sourced script calls exit
so I have to trap the exit
#!/bin/sh
trap run_tests ERR EXIT
run_tests() {
...
}
. script.sh
The run_tests
function is called but as soon as I redirect the output of the source command the functions in the script are not parsed and are not available in the trap handler
This works but I get the output of script.sh
:
#!/bin/sh
trap run_tests ERR EXIT
run_tests() {
function_defined_in_script_sh
}
. script.sh
This does not print the output but I get an error that the function is not defined:
#!/bin/sh
trap run_tests ERR EXIT
run_tests() {
function_defined_in_script_sh
}
. script.sh | grep OUTPUT_THAT_DOES_NOT_EXISTS
This does not print the output and the run_tests
trap handler is not called at all:
#!/bin/sh
trap run_tests ERR EXIT
run_tests() {
function_defined_in_script_sh
}
. script.sh > /dev/null
If you are using Bash, a similar solution to @andrewdotn's approach (but without needing an extra flag or depending on the script name) can be accomplished by using
BASH_SOURCE
array.script.sh:
run_tests.sh:
If you are using Bash, another solution may be:
According to the “Shell Builtin Commands” section of the bash manpage,
.
akasource
takes an optional list of arguments which are passed to the script being sourced. You could use that to introduce a do-nothing option. For example,script.sh
could be:and
unit.sh
could be:Then
script.sh
will behave normally, andunit.sh
will have access to all the functions fromscript.sh
but will not invoke themain()
code.Note that the extra arguments to
source
are not in POSIX, so/bin/sh
might not handle it—hence the#!/bin/bash
at the start ofunit.sh
.Picked up this technique from Python, but the concept works just fine in bash or any other shell...
The idea is that we turn the main code section of our script into a function. Then at the very end of the script, we put an 'if' statement that will only call that function if we executed the script but not if we sourced it. Then we explicitly call the script() function from our 'runtests' script which has sourced the 'script' script and thus contains all its functions.
This relies on the fact that if we source the script, the bash-maintained environment variable
$0
, which is the name of the script being executed, will be the name of the calling (parent) script (runtests
in this case), not the sourced script.(I've renamed
script.sh
to justscript
cause the.sh
is redundant and confuses me. :-)Below are the two scripts. Some notes...
$@
evaluates to all of the arguments passed to the function or script as individual strings. If instead, we used$*
, all the arguments would be concatenated together into one string.RUNNING="$(basename $0)"
is required since$0
always includes at least the current directory prefix as in./script
.if [[ "$RUNNING" == "script" ]]...
. is the magic that causesscript
to call the script() function only ifscript
was run directly from the commandline.script
runtests