Hi Rafal,
Rafal Somla, 17.03.2009 09:47:
> Hi Ingo,
>
> I tried the new script and it works now. Everything looks fine.
Does it mean that I can push it now?
>
> I have a question though. I remember you explaining that it is possible
> to create a coverage report which informs only about uncovered *new*
> lines added on top of the current tree. I.e., when I work on my patch, I
> will see which lines in the code I've just written are not covered. Is
> it possible to create such report with your script? Would it be useful
> to have an option selecting if coverage of all code or only new code
> should be tested?
There is the DGcov tool. It builds a relation between the coverage
counters and a [set of] revision[s]. It displays all parts of the
changed code, which is not covered. It does so in textual form. Since we
want to cover all lines in new revisions, this shouldn't be a problem.
I have no idea, how a combination of both tools could look like.
http://forge.mysql.com/wiki/DGCov
Regards
Ingo
--
Ingo Strüwing, Database Group
Sun Microsystems GmbH, Sonnenallee 1, D-85551 Kirchheim-Heimstetten
Geschäftsführer: Thomas Schröder, Wolfgang Engels, Dr. Roland Bömer
Vorsitzender des Aufsichtsrates: Martin Häring HRB München 161028
