fix: can name a test file named after an binary

If one named its test file after an binary that can be found in
PATH then bash_unit was trying to source this binary instead of
the test file.

Also note that the path displayed in test output may not be the
exact path of the file as bash_unit changes directory to the test
file directory before running the test so it's a local path that is
displayed. That's a problem I keep for later.

Author: pgrange

bash_unit

@@ -580,7 +580,7 @@ do
     then
       cd "$(dirname "$test_file")"
       # shellcheck disable=1090
-      source "$(basename "$test_file")"
+      source "./$(basename "$test_file")"
     else
       # shellcheck disable=1090
       source "$test_file"

tests/test_cli.sh

@@ -5,7 +5,7 @@ test_run_all_tests_even_in_case_of_failure() {
 "\
 Running tests in code
 	Running test_fails ... FAILURE
-code:2:test_fails()
+./code:2:test_fails()
 	Running test_succeed ... SUCCESS
 Overall resultcode: FAILURE\
 " \

tests/test_tap_format

@@ -27,7 +27,7 @@ test_tap_format_for_one_failing_test() {
 "\
 # Running tests in code
 not ok - test_not_ok
-# code:2:test_not_ok()
+# ./code:2:test_not_ok()
 1..1" \
 "$(bash_unit_out_for_code <<EOF
   test_not_ok() {
@@ -74,7 +74,7 @@ test_tap_format_for_failing_test_with_stdout_stderr_outputs() {
 not ok - test_not_ok
 # out> message on stdout
 # err> message on stderr
-# code:2:test_not_ok()
+# ./code:2:test_not_ok()
 1..1" \
 "$(bash_unit_out_for_code <<EOF
   test_not_ok() {
@@ -90,7 +90,7 @@ test_assertion_message_is_tap_formatted() {
 # Running tests in code
 not ok - test_not_ok
 # obvious failure
-# code:2:test_not_ok()
+# ./code:2:test_not_ok()
 1..1" \
 "$(bash_unit_out_for_code <<EOF
   test_not_ok() {
@@ -107,7 +107,7 @@ test_multi_lines_assertion_message_is_tap_formatted() {
 not ok - test_not_ok
 # obvious failure
 # on multiple lines
-# code:2:test_not_ok()
+# ./code:2:test_not_ok()
 1..1" \
 "$(bash_unit_out_for_code <<EOF
   test_not_ok() {