[Cobertura-devel] branch coverage reporting dependent on the order in which .ser files are merged

[Zschocke, F. <Flo...@cy...>]

Hello,

I noticed why generating reports from merged cobertura.ser files would sometimes show incorrect branch coverage. The branch coverage data is dependent on the order in which the cobertura.ser files are merged. The line coverage data seems to the unrelated. As I didn't see this being documented anywhere, I wonder if this is a bug. Why is this, is there a reason for it? Shouldn't merging data files be independent on the order?

Thanks,
Florian