DocCheck output could be improved when no errors occur

Question

I am using DocCheck and find the output very useful if errors or warnings occur, but not very useful when there are no errors or warnings. In the latter case, the Executive Summary explains the table columns where there is no table, the Package Summary gives a note about the Minor Errors table which also isn't there and the Package Statistics merely states the number of packages checked. What I would like to see is an overview of the packages that are checked, much like the situation where there are errors or warnings.
Is there any way to control the output for this situation so that it always produces the output in the same format?

Answer 1

Wow. No errors. Congratulations!
Seriously, you have both bug requests and an enhancement request, here.
The bug is that when a table is empty, there should be text under the heading
that says "no errors found" or words to that effect. That's a minimum level of
functionality the program should include.
For the enhancement, you would like to see "an overview of the packages that are
checked, much like the situation where there *are* errors or warnings", but I'm
having a hard time figuring out what that would mean, in practice.
There is an overview of the packages checked on the executive summary
page, under "No Errors Found" (no point in using a table, since the number of
errors and percentage of errors columns would be zero).
The package summary pages, too, only show counts of errors, so if there are
no errors, there isn't much to show on that page.
On the statistics page, the first table should show number of classes, nubmer
of interfaces, etc. That should still be present, even with no errors. The next
two tables are nothing but error-distribution tables, which again would say
nothing at all if no errors were present.
Are you saying that you'd like some global statistics table that broke down how
many classes in a package, how many methods in the class, or things to that
effect? (That might be a useful enhancement, at some point.)
I think part of the problem may be that, since you're not seeing the tables (which
is a good thing) it's not clear just how little they would contain! Without errors to
report, there is nothing to put in the columns. (The only exception is "Items Inspected"
-- the first table at the top of the statistics page.
In general, DocCheck works on the concept of "exception reporting". It only shows
errors, so you don't have to scan through a huge report in an attempt to find them.
I can see where it could be helpful to see how many things there are that don't
have errors, though. That way, for example, you could tell that you added 50 methods,
all without error.
That raises the bar from an error-detecting tool to an error-management tool, but
I suspect that it is a useful goal to pursue.