Re: [go-nuts] Capture test output per-function

You should never use fmt.Printf in a test. Use t.Logf instead. On Thu, Jul 6, 2017, 17:29 wrote: > On Thursday, July 6, 2017 at 12:40:30 AM UTC-7, Jan Mercl wrote: > >> On Thu, Jul 6, 2017 at 12:56 AM wrote: >> >> > As far as I can tell, go test

Re: [go-nuts] Capture test output per-function

On Thursday, July 6, 2017 at 12:40:30 AM UTC-7, Jan Mercl wrote: > > On Thu, Jul 6, 2017 at 12:56 AM wrote: > > > As far as I can tell, go test captures the output per-package, and when > one test fails it dumps all the captured logs. > > It's per test, not package. > > I

Re: [go-nuts] Capture test output per-function

On Thu, Jul 6, 2017 at 12:56 AM wrote: > As far as I can tell, go test captures the output per-package, and when one test fails it dumps all the captured logs. It's per test, not package. jnml@r550:~/tmp/test$ ls all_test.go jnml@r550:~/tmp/test$ cat all_test.go

[go-nuts] Capture test output per-function

In Funnel, we have a growing end-to-end test suite which has many test functions. https://github.com/ohsu-comp-bio/funnel/tree/master/tests/e2e When one test fails, Funnel's logs are dumped, and there are lots of them. Debugging tests has become difficult. As far as I can tell, go test