| E. Scott Daniels | 2301eb8 | 2020-07-15 13:46:51 -0400 | [diff] [blame^] | 1 | |
| 2 | This directory contains all of the tests which can be run |
| 3 | to vet the modules for the MG xAPP. |
| 4 | |
| 5 | Run the script unit_test.sh (ksh or bash) to build and execute |
| 6 | each test. The script will leave the relivent .gcov files |
| 7 | in the directory for any additional use. It will also provide |
| 8 | a high level summary of the coverage of each of the modules. |
| 9 | |
| 10 | The data directory contians input files which are used during |
| 11 | the tests. |
| 12 | |
| 13 | |
| 14 | The test programmes are all named *_test.cpp. There are support |
| 15 | tools also located in this directory: |
| 16 | |
| 17 | ut_support.cpp -- test tools used by all test programmes |
| 18 | parse_gcov.sh -- script to parse .gcov files for summary |
| 19 | stats_sender.c -- A simple xAPP which sends RMR messages with |
| 20 | the metrics message type. |
| 21 | |
| 22 | It is possible to drive the unit tests from the top level CMake |
| 23 | generated build environment: |
| 24 | |
| 25 | mkdir .build |
| 26 | cd .build |
| 27 | cmake .. |
| 28 | make test ARGS="-V" |
| 29 | |