[ << Regression tests ] | [Top][Contents][Index][ ? ] | [ Programming work >> ] | ||
[ < Finding the cause of a regression ] | [ Up : Regression tests ] | [ MusicXML tests > ] |
9.7 Memory and coverage tests
In addition to the graphical output of the regression tests, it is possible to test memory usage and to determine how much of the source code has been exercised by the tests.
Memory usage
For tracking memory usage as part of this test, you will need GUILE CVS; especially the following patch:
http://lilypond.org/vc/old/gub.darcs/patches/guile-1.9-gcstats.patch. |
Code coverage
For checking the coverage of the test suite, do the following
./scripts/auxiliar/build-coverage.sh # uncovered files, least covered first ./scripts/auxiliar/coverage.py --summary out-cov/*.cc # consecutive uncovered lines, longest first ./scripts/auxiliar/coverage.py --uncovered out-cov/*.cc
[ << Regression tests ] | [Top][Contents][Index][ ? ] | [ Programming work >> ] | ||
[ < Finding the cause of a regression ] | [ Up : Regression tests ] | [ MusicXML tests > ] |