Daniel Nephin

Thanks for opening this issue! I think this is similar to #136. I think adding an option to limit the output would be good. I don't think there is anyway...

Yes, exactly! `gotestsum` only sees output sent to stdout or stderr. So if you write the output to a separate file then the junit.xml will only contain the test success/pass...

I forgot to mention that #251 has some suggestions for how to do that.

> does not write anything useful to stdout, stderr Hmm, that's surprising. Any build errors should be reported as errors. Would you mind opening an issue about this? Could you...

The build errors are sent to stderr by `go test`, so they don't appear in the testjson. They are captured here: https://github.com/gotestyourself/gotestsum/blob/master/testjson/execution.go#L345-L356

Thank you for the PR, and for your interest in fixing this problem! I'm hoping this problem is fixed in the stdlib at some point. I think the solution proposed...

One way to work around problems like this is to add something like this to any test setup functions: ```go t.Cleanup(func() { t.Log("\n") }) ``` As long as that is...

Until we have server side stacks I think it's a mistake to change this. We kept it consistent with Compose knowing that either namespaces or server side stacks would be...

The default kind version does not appear to work anymore (see #140). It would be great to tag a new release so that the default configuration is usable.

ping @vieux @abronan