One possibility would be to use build constraints.  If you run go test as:

go test -tags testing pkgname


Then you can use that tag to select which files will be included in a standard build of your package, and which will be used for testing.

If you put your standard configuration in a file of its own, then adding a line to the top like the following will ensure that it is not used for testing:

// +build !testing


You can then include the testing configuration in one of the *_test.go files, or in some other file that requires that the testing tag be set.

How do I know I'm running within "go test"
I was browsing around the new tag synonym proposal system and when I browsed to the .NET tag info page I was greeted with an "edit tag wiki" link. So I edited it and created some text. Very cool.

So I have a few questions.


What is the requirement to be able to edit this tag wiki? I clearly can't do it on all tags, so I'm guessing there is some activity requirement within the tag space before you get the ability to edit the wiki.
What should the content be? I browsed around a little, but I couldn't find any other examples with any content. I just included some basic text for the .NET one. "Questions relating to the Microsoft .NET framework" with a link to http://www.microsoft.com/net/.

