| | 70 | |
| | 71 | |
| | 72 | = Unit testing = |
| | 73 | |
| | 74 | Unit tests exist for all batch types in the {{{unitTests}}} folder. These tests confirm that data integrity is maintained after code changes have been made. All batch tests can be run like this |
| | 75 | |
| | 76 | {{{ |
| | 77 | cd unitTests |
| | 78 | ./runAllTests.sh |
| | 79 | }}} |
| | 80 | |
| | 81 | Or, individual test like this, for detections: |
| | 82 | |
| | 83 | |
| | 84 | {{{ |
| | 85 | cd unitTests/detectionTest |
| | 86 | ./run.sh |
| | 87 | }}} |
| | 88 | |
| | 89 | All test create batches in a 'test' mode, meaning, a current date will not be used and, in the case of detections, only chip 33 (instead of all 60) will be processed. The resultant FITS files are then compared (using {{{diff}}}) with FITS files known to be correct. The user is informed if they are identical or if they differ. |