Add `tools/ and move scripts

- addressing #89 (Re-organize repository with more sub-folders)

README.md

@@ -162,11 +162,11 @@ Run unit tests locally on the command-line with
 ```
 
 If you want to run unit tests repeatedly (e.g., to sample a range of
-random numbers), then you may use the bash-script `many_test_runs.sh` which
-runs `N` number of times and reports only unit test failures, e.g.,
+random numbers), then you may use the bash-script `tools/many_test_runs.sh`
+which runs `N` number of times and reports only unit test failures, e.g.,
 ```{.sh}
-      ./many_test_runs.sh        # will run a default (currently, 10) number of times
-      N=3 ./many_test_runs.sh    # will run 3 replicates
+      ./tools/many_test_runs.sh        # will run a default (currently, 10) number of times
+      N=3 ./tool/many_test_runs.sh     # will run 3 replicates
 ```
 
 <br>

makefile

@@ -249,7 +249,7 @@ cov : cov_clean $(lib_gtest) $(lib_target_cov)
 .PHONY : cov_run
 cov_run : cov
 		./$(bin_test)
-		./run_gcov.sh
+		./tools/run_gcov.sh
 
 
 

many_test_runs.sh → tools/many_test_runs.sh

@@ -1,6 +1,6 @@
 #!/bin/bash
 
-# N=3 ./many_test_runs.sh: run unit tests repeatedly and report failures only
+# N=3 ./tools/many_test_runs.sh: run unit tests repeatedly and report failures
 # $N number of test runs; default 10 if empty or unset
 
 iters=${N:-10}
@@ -22,4 +22,3 @@ for i in $(seq 1 $iters); do
 done
 
 echo $(date): Completed ${iters} test replicates.
-