I don't have a capacity to implement this myself right now. Putting for adoption from community.

I think this a good first issue to solve even though the scope is a bit big if this is your first PR ever. There is already code that creates jacoco format and cobertura would be similar hopefully.

I found where the JaCoCo generation code is.

As Cobertura is another XML-based coverage format, I'm hoping it wouldn't be too hard to implement. I did find the Cobertura DTD files which describe the format: https://github.com/cobertura/cobertura/tree/master/cobertura/src/site/htdocs/xml

That being said, I'm not sure which version of Cobertura we would want to support. The Cobertura output I get from Jest JavaScript unit tests (via jest-junit) shows as coverage-04.dtd, so perhaps that would be a good place to start as I already know that it is supported by tools like ReportGenerator and Azure Pipelines. Thoughts? If I get a chance I may take a crack at it since I could really use this functionality.

That being said, I'm not sure which version of Cobertura we would want to support. The Cobertura output I get from Jest JavaScript unit tests (via jest-junit) shows as coverage-04.dtd, so perhaps that would be a good place to start as I already know that it is supported by tools like ReportGenerator and Azure Pipelines. Thoughts? If I get a chance I may take a crack at it since I could really use this functionality.

Searching around the web it seems coverage-04.dtd is mostly the one referenced. Didn't look at what the differences would be. Looks like Cobertura isn't really maintained much lately, but I guess that means the DTD is kinda stable.

JaCoCo seems to be generally widely supported in CI and tools, so as long as the Cobertura-version is compliant with Gitlab which requires conversion atm, then it should be fine I guess. 🙂 Really weird how they keep delaying the JaCoCo-support (ETA Q2'24 for now).

Yeah, seems like Cobertura is still a preferred format in the JS world, as that's one of the most commonly referenced output formats when I'm looking into Jest code coverage. Unfortunately I haven't found any JaCoCo format plugin for Jest... It would be nice if all the code ecosystems could agree on some kind of uniform standard LOL!