I'm on an XP team whose nightly metrics report includes counts of (cutting and pasting
Unit testsJava source filesJava classesJava total source linesJava unit-test source linesJava non-test linesTotal code lines analyzedUnexecuted linesTest coveragePassing functional testsFailing functional testsUnexpected failuresSkipped functional testsUses of "instanceof"/KLOC The ones we actually use are unit test coverage percentage, functional test pass/fail, and especially "Unexpected failures". Our functional test framework lets you mark a test as "I know this one doesn't pass yet." Unexpected functional test failures are ones that used to work and are now broken.
We used to look at unit test count and line count a lot, earlier in the project, to see how it grew and pat ourselves on the back. We never think about those anymore.