Order of packages when using pkgname about gotestsum HOT 2 CLOSED

Currently gotestsum doesn't order the packages at all. You are correct that output is printed as go test emits the "package pass/fail" event. I believe the reason that the order changes is because go test will run packages in parallel, and that can change the order of when they complete.

If you run

gotestsum -fpkgname -- -p 1 ./...

That tells go test to only run a single package at a time, and I think that may give you predictable ordering.

For gotestsum to order things it would have to buffer all of the output, which doesn't seem worth it.

from gotestsum.

My main motivation for this was because I thought that getting coverage for top-level (.) package is the same as coverage across all packages (when using -coverpkg ./.... And having it be last would then work with GitLab coverage extraction. But top-level coverage is not really total coverage. I made golang/go#66506 to request total coverage output. Closing this.

from gotestsum.