<p>Let say I have a package containing two source files foo.go and bar.go, and their associated test files foo_test.go and bar_test.go. When I run <em>go test</em> in that package directory everything is fine. </p>
<p>Then I refactor code in foo.go. As a consequence bar.go, and the tests don't compile and run anymore. </p>
<p>I then would like to first refactor the foo_test.go to make sure foo is ok, before refactoring bar.go. But <em>go test</em> won't allow me to execute it because bar.go doesn't compile. </p>
<p>Is there a way to allow me to test foo.go with foo_test.go even if bar.go doesn't compile ? </p>
<p>Now I rename bar.go and bar_test.go into bar.go_lck and bar_test.go_lck, but it's inconvenient. </p>
<hr/>**评论：**<br/><br/>danredux: <pre><p>Add something like</p>
<pre><code>// +build imready
</code></pre>
<p>To the top of the file you want to hide (it's a build tag). It will no longer be included. Now you can pass in a build tag when you're ready to start including that file, or just remove the line.</p></pre>chmikes: <pre><p>This is great. Thank you very much.
Is there a place where such build tags are listed ? I have seen that there is a similar way to direct the compiler to only compile some code on specific OS. </p></pre>Akkifokkusu: <pre><p>Put them in separate packages? Comment out the parts of <code>bar.go</code> that were broken by the changes to <code>foo.go</code>?</p></pre>
