Our test coverage is very spotty in some areas. We can attack this
piecemeal, but we also really need to get some idea of *how* spotty it
is... so let's grab a python coverage tool from somewhere and stick it and
yatest together. (This may be tricky in that we need to communicate
coverage information back from the child processes...)
Original issue reported on code.google.com by njsmith@ucsd.edu on 7 Nov 2009 at 5:11
Original issue reported on code.google.com by
njsmith@ucsd.edu
on 7 Nov 2009 at 5:11