Off topic - quickly searched and looks like xml re...
# testballoon
e
Off topic - quickly searched and looks like xml reporting is done by junit itsefl
o
XML reporting is actually done by Gradle. But it needs to be fed really carefully as it still does not understand nesting tests, although JUnit 5+ folks have been requesting support for this for years. Luckily, TestBalloon knows ways to get around this.
e
Ah cool! Context of the question - I'm working on parsing test reports utility and had hope you're using kotlin serialisation for junit report.
o
TestBalloon is trying to be a good citizen in the existing ecosystem here. So it's all under Gradle's control and not that well defined. Also, depending on the platform, some characters in these reports must be mapped to alternatives in order to work around class/method assumptions and avoid crashing the test process (on Android). If you wanted parseable reports, what if you'd produce your own stable report format and parse that?
e
Thanks! I will try.
Actually, better not. Since other tooling pretty well work with junit format. I'm just new to Kotlin serialization for xml. Should deeper dig for mapping.