The underlying problem is that a "go test" only has one output stream: the text written via `T.Log`. Additional output on stdout or stderr isn't associated with the test that produced it, which is bad when running tests in parallel or when running without "go test -v".
Sean Liao schrieb am Freitag, 10. März 2023 um 19:11:02 UTC+1: > implementing a helper/wrapper on your side might be easier, I believe most > helpers take the TB interface rather than the concrete T type. > also it sounds more like a failure of the application to separate its > output streams properly. > -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/7d2e99d0-7037-4452-9210-0b1242a97a1bn%40googlegroups.com.
