Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

proposal: testing: output timing and outcome of TestMain or possible setup and teardown functions #57326

doron-cohen opened this issue Dec 15, 2022 · 2 comments


Copy link


We are currently using the TestMain function to setup and teardown test-containers in our integration tests. This allows us to prepare the environment once for the entire test suite and save time.
We also monitor our test CI step by using gotestsum which practically parses the output from go test -json. This lets us keep the CI snappy.

One issue we are having is that there is no way to monitor TestMain's timing or outcome. In gotestsum there is some code to add a fake test case in the case the failure occurred in TestMain (see comment by @dnephin ). But, there is still no way to monitor how long did the logic before and after the tests ran.

There are several possible ways to tackle this IMO:

Declaring setup and teardown functions

Introduce new functions for setup and teardown:

func TestMain(m *testing.M) {

This can work just like testing.T.Cleanup does. I think this is beneficial for other use cases where there is a need to better organize testing code.

Emitted JSONs could look like:


Monitor TestMain timing without m.Run time

Another option is to time the entire TestMain but stop the timer on m.Run and resume when it ends.

Hypothetical code:

func (m *testing.M) Run() int {
	defer m.timer.Continue()

	# ... run tests

Emitted JSONs could look like:

@gopherbot gopherbot added this to the Proposal milestone Dec 15, 2022
Copy link

note testing.M.Cleanup was previously declined in #42161

Copy link

note testing.M.Cleanup was previously declined in #42161

Thanks for the reference. I think there is another valid use case here which I didn't see in that proposal. Also, we can achieve TestMain timing without these as I suggested.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Status: Incoming

No branches or pull requests

3 participants