Marcus: can you explain why you changed name="foo" to be name="full/path/to/foo" ? In Cobertura reports, it looks right to me that name should be short. Or maybe I don't understand how this XML change will translate to a user-visible change in Jenkins?
The first image is from the coverage report main page, the second is the report for an individual package, then the third is the individual file view, which has highlighted code output below (which I didn't screenshot).
I think this PR is breaking the XML output. Previously, I was able to get a <package> entry for every individual package in my code. Now I just get one anonymous <package>. PDBing, the "cu.name" attribute here doesn't have periods in it, it has slashes:
Yep, I didn't expect this to get merged after I reported that it was broken!
IIRC cu.name was fine when first collected, but once the data is serialized to .coverage, and re-loaded cu.name becomes cu.filename.
I have no idea if this is what happens with the latest code ;)
Ned Batchelder - yeah, I've no doubt that #67 is a real bug too. I don't know the details of how this logic works but my impression is that different scenarios lead to different kinds of data being passed xmlreport.py. I'm running here with py.test and the pycov extension, so it might be calling upon Coverage in a different way than Nose does. I think the solution would involve confirming and identifying every variety of .name that can occur there, then adding logic to detect and handle each contingency explicitly.