After the checkout is complete, you must update your CASAtools RC file to indicate where the unit test data can be found. In my case it looks like:
-bash-4.2$ cat ~/.casa/config.py
datapath=[ "~/develop/casa/casatestdata/" ]
The `datapath` list specifies directories where CASAtools should look for data files, and should include the directory we just checked out. After all of this is set, the full suite of tests can be run with:
The `datapath` list specifies directories where CASAtools should look for data files, and should include the directory we just checked out.
A few of the casatools tests use the casatestutils module. That is built independently from casatools.
The path to a casatestutils build can be provided via PYTHONPATH prior to running the full suite of tests.
After all of this is set, the full suite of tests can be run with:
-bash-4.2$ ./setup.py test
-bash-4.2$ PYTHONPATH=../casatestutils/build/lib ./setup.py test
There are bout 48 tests in total. Running all of them takes about 12 minutes on my laptop.
There are about 28 tests in total. Running all of them takes about 48 minutes.
The test results can be found in subdirectory of the casatools/build directory (e.g.
casatools/build/testing.linux-x86_64-3.6). A separate directory is use for each tool
*To run a single set of test*, you can just execute the test file:
-bash-4.2$ PYTHONPATH=build/lib.macosx-10.12-x86_64-3.6 python tests/tools/coordsys/test_coordsys.py
If the ```casatools``` module is already available in your ```PYTHONPATH```, you would not need to
explicitly specify it on the command line. This would be the case, for example, if you installed
CASAtools via a binary *PyPI* wheel. If you want to run a single test from the set, you can specify
it on the command line like: