Please give us an easy way to ensure all tests in a list of packages compile..... right now I have to go test ./... -test.run=xxx ... and that does all the linking and crap that I don't care about into N binaries, which takes forever. I just want to know if I caught all the places that need to get updated in the tests when I do a change. For juju this takes *minutes* when a single compile of the actual code only takes ~15 seconds.
+1 for consolidated documentation on testing, building, etc. Having to look at specific package to know how to test is really unintuitive... and it assumes you know that there's a testing package that has that information. I expect there to be a "here's how to test with go" in some obvious top level place in golang.org. Put the package selector "..." directly in the help for tools that use it. It took me a long time to figure out how to build more than a single directory, and it's something that gets used all the time. It's buried in a separate help menu halfway down a wall of text... and I've seen a ton of newbies ask how to do it. Put examples in the help output. I can't tell you how often examples help far more than a wall of text. Something as simple as this would save a lot of newbie questions: Examples: // build this directory and all subdirectories go build ./... Are there still tools you have to download separately from the go tool, like coverage? I've had everything installed so long, I forget if this is still a thing. But if it is, please just include it in the normal install. Choose a default GOPATH. Just pick one. Doesn't matter if it's good or bad, as long as people can just go get as soon as they have the tool on disk. -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
