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.
@quentinmit can you cite the exact message. #2981 is too long to find the answer for people coming here from search engine(s).
Problem with AppVeyor and Windows in general that there is no native tee command there, so directing output to file and to screen at the same time is tricky.
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.