https://bz.apache.org/bugzilla/show_bug.cgi?id=65030
--- Comment #6 from Jaikiran Pai <jaiki...@apache.org> --- > or we could replace them with an entity reference (i.e. 0 with �) - which > would still be illegal per se - but benefit from writeAttribute escaping the > ampersand - this is what JUnit 5 itself or Surefire seem to be doing > (unknowingly, maybe). I think we should go with this approach - i.e. replace the illegal characters with their entity references and then let writeAttribute escape them. That will at least prevent any data loss in the reports (losing data like this while debugging test failrues can be annoying and can lead to difficult to debug issues). > either fix would be pretty easy to implement but a bit tricky to test. Wouldn't the test involve just checking, in the report, for a string which represents this escaped value? -- You are receiving this mail because: You are the assignee for the bug.
