File: TESTING

package info (click to toggle)
wsclean 3.6-3
  • links: PTS, VCS
  • area: main
  • in suites: forky, sid
  • size: 16,296 kB
  • sloc: cpp: 129,246; python: 22,066; sh: 360; ansic: 230; makefile: 185
file content (21 lines) | stat: -rw-r--r-- 963 bytes parent folder | download | duplicates (2)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
Unit, integration and system checks

To build the tests during compilation, "-DBUILD_TESTING=True" should be added to your cmake command, e.g. from your wsclean directory:

mkdir -p build && cd build
cmake ../ -DBUILD_TESTING=True

To run the unit test and the fast integration tests, run the following from the build directory:

make check

To perform the system tests that might take a considerable amount of time:

make longsystemchecks

System checks perform basic run tests that produce a number of FITS files that can be manually checked for quality. These are stored in the directory build/test_data/test_results.

Individual unit tests can be run with "./unittest -t <testname>". The testname can be a test group, such as "commandline", or a single specific test, such as "commandline/pb_grid_size".

Individual python ("system") tests can be performed by going to build/tests/python and running: python3 -m pytest source/long_system_checks.py -k <name>