title: golang code coverage in integration tests?
body: <p>It seems the point of "go tool cover -var=foo" may be to generate instrumented code that can be deployed in an integration test harness.  Is anyone using this feature for that purpose?  If so, is there a conventional way to dump the counters periodically?  It seems the tricky part would be doing this across all files of interest with near simultaneity.  Even then, some skew (if using -mode=count) would be unavoidable.</p>