It'd be useful if the playground could run tests -- more like `go test` instead of `go run`. This is possible now (http://play.golang.org/p/K0gFil6jFC), but it's clumsy and non-obvious. Just to get the conversation started, here's a concrete proposal: * Tests and examples are supported, but not benchmarks. (Benchmarks are going to unreliable anyway, right?) * If main is not present and there is an appropriate test function (or example function with output), then the playground executes in test mode. Otherwise, behavior is unchanged. * "Test mode" is equivalent to `go test -v`. * Add text to the About page explaining how to use playground for tests.
josharian
All 11 comments
_Labels changed: added repo-playground, removed priority-triage, repo-main._
_Owner changed to @josharian._
_Status changed to Started._
josharian
on 14 Jun 2014
CL https://golang.org/cl/102420043 mentions this issue.
gopherbot
on 17 Jun 2014
@adg any new thoughts about this? I could bring that old CL back to life if you were interested.
josharian
on 26 Jun 2016
If we're to do this, we could be more general: extend the API to accept multiple input files, which are built together as a package. We could even permit building a tree of packages. Then we could provide execution options (run, test, bench, others?) to run against those packages. I think the implementation of this would be pretty straightforward. The hardest part would be designing a nice JSON API for the requests.
adg
on 27 Jun 2016
@adg, we could even introduce magic comments as a way to mark new files, which is common in people's bug reports anyway.
But I see no reason to tie that feature to this. They seem separable.
bradfitz
on 26 Jan 2018
Change https://golang.org/cl/98155 mentions this issue: playground: support running tests
gopherbot
on 2 Mar 2018
I have committed a change based mostly on the way @josharian did it 3.5 years ago. I was going different direction at first but ended with something very close to that old change by Josh. At worst it was very good learning experience for me. I would be glad of somebody gave it a proper review.
ysmolsky
on 2 Mar 2018
Related issues
mingrammer
路
3Comments
rakyll
路
3Comments
go101
路
3Comments
michaelsafyan
路
3Comments
rsc
路
3Comments
Most helpful comment
If we're to do this, we could be more general: extend the API to accept multiple input files, which are built together as a package. We could even permit building a tree of packages. Then we could provide execution options (run, test, bench, others?) to run against those packages. I think the implementation of this would be pretty straightforward. The hardest part would be designing a nice JSON API for the requests.