[bind10-dev] unit tests and include symlink tree
Jeremy C. Reed
jreed at isc.org
Fri Feb 5 19:28:31 UTC 2010
See data.h
http://bind10.isc.org/~tester/20100205191051-740/coverage/src/lib/cc/cpp/index.html
and
http://bind10.isc.org/~tester/20100205191051-740/coverage/include/cc/index.html
This is the same file. But the symlink version got 100% coverage and the
real one (target of symlink) only 57%.
The reverse is exceptions.h:
http://bind10.isc.org/~tester/20100205191051-740/coverage/include/exceptions/index.html
and
http://bind10.isc.org/~tester/20100205191051-740/coverage/src/lib/exceptions/cpp/index.html
In this case the included symlink got 70% coverage and the real one got
100% coverage.
It appears that some unit tests are using the headers from the src tree
while others are using the include tree.
I was going to remove include from the lcov report, but then realize it
was inconsistent and the results would be wrong. I suggest we don't use
the include symlink tree for the gtest tests.
More information about the bind10-dev
mailing list