New formatter idea: worker-oriented view about gotestsum HOT 5 OPEN

Here is a little visualization tool, that I did:
https://github.com/afbjorklund/go-test-trace

It can help show some of the concurrency issues, as an addition to what is already shown by this tool.

from gotestsum.

This is awesome! Thank you for working on this!

I've used the actiongraph before to debug build times, but had not considered using it to augment gotestsum. I really like this idea. I see you attempted to use a file descriptor to receive the data. did that not end up working for some reason?

Let me know if there is anything I can help with!

from gotestsum.

Yeah I initially tried to pass pipes to it then give go /dev/fd/3. I don't really know why it doesn't work TBH, but the reads from the same pipe in gotestsum never return anything for actiongraph. For debug-trace it worked though afaik. go handles these differently, with actiongraph it open+closes at the start, then open+closes at the end. With trace it just opens, appends a bunch for the lifetime of the program, then closes, which could be related. Probably a way to make it work, but I couldn't figure it out so moved to tmp file for now. Probably something we should track down if/when we move forward with this, though

from gotestsum.

This really showcases golang/go#61233 well. So much time spent "running" packages with no tests at all!

Spent some time refining the UI

from gotestsum.

This looks very cool. In my case, all tests are in the same package (with many tests running simultaneously via t.parallel()). It'd be nice to have a way of showing which tests are 'in progress' with a runtime for each.

from gotestsum.