Closed LYP951018 closed 3 years ago
Thank you for your suggestion. However, the problem with printf
is that its output is not captured by the Catch2 framework. As such output generated by printf
can appear (semi) randomly in the Catch2 xml reporter output, resulting in invalid XML that cannot be read by an Xml parser.
But as I'm writing this answer I came up with a possible solution. I've been making some changes recently that also effect Xml report handling for an upcoming feature. Based on those changes I now do have an idea to maybe fix this. Basically, instead of reporting to the default output, send the report to a file. Maybe the printf
output will then not be intertwined with the Xml report. I will have a look if this helps solve this problem.
Update. I was able to test the possible solution today and it seems to work. As such it will be part of the next release.
Finally released the new version (1.6.0) that fixes this problem. So closing this issue.
e.g., what if we add
to
ProcessXml
?I could submit a PR for this.