blob: ccd6c136739370557cd95ad5aa9c487cb944a993 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
|
Test coverage
=============
It is considered good practice to develop and maintain the test suite
with high level of test coverage, i.e., the tests that execute every
single statement, every line of the code and then validate the result.
The GNU's gcov is a tool that analyses the frequency of execution of
each line of the code. For more details see GNU documentation
http://gcc.gnu.org/onlinedocs/gcc/Gcov.html
To invoke gcov on krb5 tree, do configure with the following options
and run the tests::
./configure CFLAGS="-fprofile-arcs -ftest-coverage -O0" LIBS=-lgcov
make
make check
It will result into creation of the new helper files with the
extentions gcno and gcda.
To validate the test coverage of the specific file, change the
directory to its location and run ::
gcov -o filename.so.gcno filename.c
To see the test coverage of the filename.c open a newly created file
filename.c.gcov in the editor.
Some recent test coverage result can be found at the
http://k5wiki.kerberos.org/wiki/Test_coverage
|
