<p>I have used go tool cover to get 100% coverage. Apparently <code>go tool cover -http <file></code> is not working anymore with go 1.8 as it did with go 1.7.x. </p>
<p>How can we see the code coverage ?</p>
<hr/>**评论：**<br/><br/>gohacker: <pre><blockquote>
<p>-http <file></p>
</blockquote>
<p>Did that ever work? It has always been <code>-html</code>.</p></pre>chmikes: <pre><p>It could be a typo. Sorry. I had an alias. So I'm using the exact same command that worked with go 1.7.x.
However, in the mean time there have been system updates and firefox updates. I'll retry tomorrow after the reboot.</p></pre>gohacker: <pre><p>Well, it definitely works for me. Here's how go tool cover chooses between browsers: <a href="https://github.com/golang/go/blob/678f35b676de075375066ade2935296dfb8050ec/src/cmd/internal/browser/browser.go#L17-L38" rel="nofollow">https://github.com/golang/go/blob/678f35b676de075375066ade2935296dfb8050ec/src/cmd/internal/browser/browser.go#L17-L38</a></p></pre>chmikes: <pre><p>I'm ashamed. I didn't notice that I was connected on a remote host. Of course it could not work in this condition. After switching to the local host it now works. </p></pre>gotack: <pre><p><code>go tool cover -html <file></code> seems to do the trick for me on <code>go version go1.8 linux/amd64</code></p></pre>SSoreil: <pre><p>Not sure if this will help you but I had issues with it on either Go 1.6 or Go 1.7 as well. The process would use 100% CPU and I think memory started to leak like crazy as well.</p></pre>nstratos: <pre><p>This command used to be my bread and butter before vim-go made it easier:</p>
<pre><code>go test -covermode=count -coverprofile=count.out && go tool cover -html=count.out
</code></pre>
<p>But I still use it sometimes because <a href="https://blog.golang.org/cover#TOC_6." rel="nofollow">heat maps</a> are cool! Oh wait.</p></pre>TcM1911: <pre><p>You may need to set the environment variable $BROWSER in your shell. </p></pre>
