Daniel Nephin

This is really cool, thanks for opening this issue! #293 was recently merged, which I think is trying to accomplish a similar thing, but there's always room for more improvements....

`go tool cover` (https://pkg.go.dev/cmd/cover) is a similar idea. It can produce 2 reports: coverage percentage per function, and a detailed HTML report. The HTML report effectively has this information, but...

Thanks for the issue. I'd suggest using `--jsonfile` argument to write the json to a file. Then you can use https://pkg.go.dev/github.com/gotestyourself/gotestsum/testjson#ScanTestOutput to read that file and then call `Failures()` to...

Thanks for the issue! There shouldn't be any need to parse the args because they are already parsed by the shell before being handled to `gotestsum`. I would expect something...

Hello, thank you for the bug report! Errors come from any stderr that is emitted from the test binary. I don't see any lines in this example. Do you have...

@ikari-pl what version of `gotestsum` ? Does it happen every time, or occasionally? This can happen when `go test -json` writes something to stderr. In this case it seems like...

Alternatives to fixing this problem could be to remove the `hasSubTestFailed` map to avoid the problem. Maybe those upstream bugs are fixed now. As you suggested in another issue, using...

Thank you for the bug report! When I was added tests for a change to coverage support I recall there being problems with the `testname` format when `-coverprofile` is enabled....

Thank you for the PR! This would be a great thing to improve. It has been a little while since I've looked at this code. I believe the only special...

> To stay consistent round robin approach can not be used because a new package would shift all packages after it by one. One important detail, that may be not...