<p>I want to avoid global variables in my tests, would it be better to make a function that retuns a local variable for use in a test or just make a global variables in the test because it wont be compiled into the main program (or will it?)</p>
<p>example of using a function to return a local variable</p>
<p><code>
func DefaultConfig() *Config {
return &Config{
SomeValue: 1,
OtherValue: 2,
}
}
</code></p>
<p>Or since it isnt compiled just use gloabl test variable</p>
<p><code>
var DefaulttestConfig = &config{
Somevalue: 1,
Someothervalue: 2,
}
</code></p>
<hr/>**评论：**<br/><br/>edwinTop: <pre><p>Ben johnson wrote a helpful post - check out point 1
<a href="https://medium.com/@benbjohnson/structuring-applications-in-go-3b04be4ff091" rel="nofollow">https://medium.com/@benbjohnson/structuring-applications-in-go-3b04be4ff091</a></p></pre>0xjnml: <pre><p>Nit: Go doesn't have global scope. Somehow similar is the universe scope, but user code cannot define anything in universe scope. Go package scope is what you probably mean by 'global scope'.</p></pre>jackmott2: <pre><p>Just as an aside, if you ever find yourself having to create a bit of a mess, or add a bunch of code, to avoid one of the rules of thumb of programming, you might consider just breaking the rule.</p>
<p>I don't know if this is one of those cases, just keep that in mind.</p></pre>
