proposal: testing: add Test function

The testing package has long contained the Benchmark function, which allows code in a non-testing source file to run benchmarks.

It is sometimes useful to be able to run test code in a non-testing context too; for example to demonstrate a failing test in the Go playground.

Perhaps something like this?

// Test runs f as a test with the given name. Any test output
// is written to w. Test reports whether the test has succeeded.
func Test(w io.Writer, name string, f func(t *testing.T)) bool

See also #6511

There is work in progress now to allow multiple files in the playground, which should make this better yet.

@bradfitz

I had no idea that https://play.golang.org/p/LnHfX2yF4Oe worked, but it does. (We should write clearer docs for the playground - @bradfitz will file a bug.)

Given that https://play.golang.org/p/LnHfX2yF4Oe does work, @rogpeppe, is there still much rationale for adding testing.Test?

I filed #32294

@rogpeppe

Looking at this again I am surprised that GitHub says I closed this. I suspect I clicked the wrong button again. I intended to leave it open for @rogpeppe to respond.

Thanks Russ - the close did feel a little sudden :) The playground was my main motivation behind raising this issue, so I think it's OK to close this issue. I might remember another use case in time though.

Navigation Menu

Repository navigation

proposal: testing: add Test function #32067

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

proposal: testing: add Test function #32067

Description

Activity

josharian commented on May 15, 2019

rsc commented on May 28, 2019

bradfitz commented on May 28, 2019

rsc commented on May 29, 2019

rogpeppe commented on May 29, 2019

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions