This makes sense, but what's your use case?

My use cases are simple. I want to know what test is running when I pass test functions to utility functions, and/or want to log the name of a test for recording to external services.

Ok, sounds good to me. Please write up a brief proposal document.

@adg Did you want a design document? As far as proposals go, it looks like this issue should be enough if I've understood the directions correctly.

The change should be very simple - don't feel like a design document is really necessary, but let me know.

Thanks,
Sean

Well, just spec out here what the method looks like.

On 28 September 2016 at 10:35, Sean Gerhardt notifications@github.com
wrote:

@adg https://github.com/adg Did you want a design document? As far as
proposals go, it looks like this issue should be enough if I've understood
the directions correctly.

The change should be very simple - don't feel like a design document is
really necessary, but let me know.

Thanks,
Sean

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#17231 (comment), or mute
the thread
https://github.com/notifications/unsubscribe-auth/AIDilSrVkbWga5qAwTbEVShdZc8R-crrks5qubZogaJpZM4KGFsB
.

I was thinking we could export the field. https://github.com/golang/go/blob/master/src/testing/testing.go#L269 change nameto Name

e.g. Name string // Name of test or benchmark.

I'd be wary of doing that, lest people change the Name in a test.
Safer would be to add a Name() string method to *testing.T and *testing.B, I think.
Care to send a CL?

That does sound like a safer approach. What's a CL?

A "change list" (see the contribution docs). But this is so simple that I'll do it, to save you the trouble of setting up a dev environment.

CL https://golang.org/cl/29970 mentions this issue.