Alexandre Conrad-Dormoy

@gro1m what do you think? I tend to agree with @notpushkin but since you implemented it I wanted to have your input and thoughts on it.

I'm marking this issue for milestone 3.0 since it would be a breaking change.

That sounds like a whole new utility to me. Such as `pycobertura merge`...

I guess the logic is: * if coverage1.xml has line `` and coverage2.xml has `` then the resulting merge would have ``. * coverage rates should get recomputed based on...

For 1. I think we have most of it implemented, pycobertura is first a cobertura parser. I believe that coveragepy has a functionality to merge/combine coverage reports. Is this relevant...

@chixiangzhou, thanks for your question. > **Column Stmts:** My understanding is this column indicates how many lines were added or deleted in the new coverage file. For instance, if 2...

Also... > I’ve recently started to use pycobertura for my on-going project at work. This is definitely a great tool and I’m already a big fan of this tool. Thanks...

> Still a bit confused about the definition of Column "Miss". If "Miss" only cares about the uncovered lines introduced, then take the dummy/dummy file for example.  > >...

> Okay, on top of this understanding, I found the number for **Column Miss** in dummy/dummy2 doesn't seem right to me. Please refer to the screenshot below:  > >...

Maybe "Missing" should only display the individual missing lines (no green lines, just red ones). My intention was to show a change of coverage/code status across lines but it might...