1 A bunch of validation checks. Run automatically before allowing
2 merges/commits to the main branch. The smaller, faster subset is run
3 before allowing commits/merges to any branch.
5 Since this software is being developed on a cluster, many of the tests
6 take advantage of the more powerful environment. You should still be
7 able to run the tests if you're on a standard machine though, it will
8 just take more time :p. To allow for the differences in invocation,
9 the most tests are broken out into two scripts, a X.cl to be run on a
10 cluster and an X.sh to be run on a standard machine.
12 Each test directory contains the script run_test.sh, which gives
13 automated testing scripts a common file name to look for. Exporting
14 the global variable ISACLUSTER allows more efficient execution on a
15 cluster. This can be accomplised (in Bash) with the command
19 Note that it is also necessary to `touch' the testing directory after
20 you add or remove a test to update bin/run-test.sh.
22 The common directory stores code shared among the tests.