Daniel Nephin

I added a comment to that issue with some other ideas about a fix. I like your suggestion of looking at the exit status to figure out if we might...

Thank you for raising this issue! Currently the time is based on runtime of the `gotestsum` command. We could add a flag to use the timestamps in the json instead...

This is what I see when I try that with the latest release of `gotestsum`, using go1.24.1. All of these report the error properly for me. Are you using an...

Hello! `gotestsum` should continue to run all the tests in all packages after a failure. The only time test runs will stop early is when there is a panic in...

Thanks for opening this issue! The reason `gotestsum` can't re-run tests after a panic is because it gets the list of tests to re-run from the list of tests that...

Looking at https://github.com/hashicorp/terraform-plugin-sdk/blob/v2.24.1/helper/resource/testing.go#L713-L717, it seems like it would be pretty easy to add a `Timeout` field to `TestCase`, and use that to set a deadline on the `context.Context`. That seems...

I think it would be interesting to implement the `go test -list` approach in `gotestsum`, since https://github.com/golang/go/issues/45508 does not appear to be going anywhere, and we now have a use...

I would love to have a more reliable way to detect a panic. I'm definitely not happy with having to look at the string prefix. I attempted to fix this...

Is it always safe in your case? If your test suite uses `os/exec.Cmd` to start the processes I assume there is a non-zero amount of code that runs in the...

I'd be happy to review a `-test.list` implementation, but I'm still not convinced it would be more correct. For one, `go test -list` only prints root test names, so there's...