Join GitHub today
GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together.Sign up
testing: add -test.report flag for xunit/junit results #17542
The idea is to add
Why xUnit/JUnit first and not JSON?
JSON is not a specification for testing, so services like AppVeyor can't support it.
Why write report to file instead of streaming it to the screen?
Because screen is for humans and report are for robots. It is very inconvenient to sacrifice one for another with pipe formatters like https://github.com/jstemmer/go-junit-report and https://github.com/tebeka/go2xunit because there is no
referenced this issue
Oct 21, 2016
As already discussed in #2981, we're not going to directly generate JUnit or xUnit or any of these other formats. Our goal is to implement a single well-specified output format for Go, and you can then use whatever converter you want on that output. I don't understand why this makes it difficult to use AppVeyor?
There is a kernel of an interesting idea here, however, which is to support both structured output and human-readable output at the same time. That has been mentioned obliquely on #2981, but feel free to raise this request explicitly.
Problem with AppVeyor and Windows in general that there is no native
The output for user should be different than for build engine, and the problem with #2981 that it probably tries to kill that other bird. Another issues is that the request is about JSON format only, which bears the risk to provide a poor interface/API for extension to more common formats.