don't count filtered tests as "OK" in report

[elliefm]

$./testrunner.pl ClamAV
Cyrus::ClamAV.aaasetup                                                  [  OK  ]
Cyrus::ClamAV.notify_deleted                                            [  OK  ]
Cyrus::ClamAV.custom_notify_deleted                                     [  OK  ]

Time:  0 wallclock secs ( 0.01 usr  0.01 sys +  0.31 cusr  0.12 csys =  0.45 CPU)

OK (4 tests)

In this case ClamAV.remove_infected_slow was skipped due to a filter, but the report at the end still counts it toward those "4 tests"

[elliefm]

I think this is just inherent to the way Cassandane blurs the line between what's a test and what's a suite. Test::Unit::Result increments the run_count when the test is started, and Test::Unit::TestSuite doesn't start tests that match the filter, but:

cassandane/Cassandane/Unit/TestPlan.pm

Lines 844 to 847 in b30e930

	# The 'run' method makes this class look sufficiently like a
	# Test::Unit::TestCase that Test::Unit::TestRunner will happily run it.
	# This enables us to run all our scheduled tests with a single
	# TestResult and a single summary of errors.

Uh oh!