Closed pickworth closed 7 years ago
can you give sample mocha output file?
All you have to do to trigger this issue with junit 4 is have a test fail on assertEquals. The default output of a failed assert equals is: expected:<[expected]Value> but was:<[actual]Value> The <>s trigger the parse error.
@lukejpreston I have given the output file (first 20 lines or so) in the original post. I truncated the end as it is irrelevant, and seems fine. The beginning of the Output file should obviously be an HTML element, not Parse Error: < 3.0
It seems that 3/4 of the actual expected HTML is just plain missing from the start of the output..
@wrlyonsjr interesting..
A workaround for this is to run with the option --minify=false
.
For example: junit-viewer --results=target/surefire-reports/ --port --minify=false
Observed this issue as well - the workaround @evansiroky mentioned works
this project is now deprecated, please see https://github.com/lukejpreston/xunit-viewer which supports the same features
I think the above works there
Looks like the beginning of the output is truncated and showing "Parse Error: < 3.0"
I am using mocha to output the junit test via mocha-jenkins-reporter.
the junit file is parsed correctly via Jenkins CI user interface, but junit-viewer seems to have some problems
this is how the html is output from the very beginning of the output (showing only the first 19 lines):