aboutsummaryrefslogtreecommitdiff
path: root/changes/fancy_testing
diff options
context:
space:
mode:
authorNick Mathewson <nickm@torproject.org>2013-07-09 12:37:11 -0400
committerNick Mathewson <nickm@torproject.org>2013-07-10 15:22:16 -0400
commit17e9fc09c31dffdc647385220a14daef5a35273a (patch)
tree66b1a0ccb2e176bc2646a25cdd03fd6eb0d90435 /changes/fancy_testing
parenta3e0a87d951b1323ca542c9b115d5525d0d022c9 (diff)
downloadtor-17e9fc09c31dffdc647385220a14daef5a35273a.tar
tor-17e9fc09c31dffdc647385220a14daef5a35273a.tar.gz
Coverage support: build with --enable-coverage to have tests run with gcov
If you pass the --enable-coverage flag on the command line, we build our testing binaries with appropriate options eo enable coverage testing. We also build a "tor-cov" binary that has coverage enabled, for integration tests. On recent OSX versions, test coverage only works with clang, not gcc. So we warn about that. Also add a contrib/coverage script to actually run gcov with the appropriate options to generate useful .gcov files. (Thanks to automake, the .o files will not have the names that gcov expects to find.) Also, remove generated gcda and gcno files on clean.
Diffstat (limited to 'changes/fancy_testing')
-rw-r--r--changes/fancy_testing4
1 files changed, 4 insertions, 0 deletions
diff --git a/changes/fancy_testing b/changes/fancy_testing
index 3e8ccbca4..ad197c6f5 100644
--- a/changes/fancy_testing
+++ b/changes/fancy_testing
@@ -10,3 +10,7 @@
in the unit tests; all functions exposed from a module for
unit-testing only are now static in production builds.
+ - Add an --enable-coverage configuration option to make the unit
+ tests (and a new src/or/tor-cov target) to build with gcov test
+ coverage support.
+