cmd/go: how to disable (run test) Cached

[imkos]

What version of Go are you using (go version)?

1.10 (win10_x64)

go test, The results always appear cached.
I made an HTTP request, the result of the server return was changed, but the test results were old.
However, run test (cached) does not make HTTP requests
Unless, I modified the code in func Test_** (), the result is the latest

func Test_gotest_cached(t *testing.T) {
	req := NewRequest()
	resp, b_resp, e1 := req.Get("http://10.20.60.52:8080/help")
	if e1 != nil {
		t.Error(e1)
		return
	}
	fmt.Println(string(b_resp), resp.Status)
}

server code:

http.HandleFunc("/help", func(w http.ResponseWriter, r *http.Request) {
		w.Write([]byte("hello!"))
	})

go test -v -timeout 30s newpay_svc -run ^Test_gotest_cached$

"hello!" => "hello world!" , but the test results were old.

[myitcv]

The Go project does not use its bug tracker for general discussion or asking questions about the language. The Github bug tracker is only used for tracking bugs and proposals going through the Proposal Process.

Please see the Questions wiki page; it has a list of good places for asking questions.

But as a quick pointer, the Go 1.10 release notes discuss how to disable test caching (and indeed when caching kicks in in the first place):

https://golang.org/doc/go1.10#test

[imkos]

Thanks for the reply, I found the reason and the solution.

[zyfdegh]

On go1.10

GOCACHE=off go test

[davecheney]

go test -count=1

…

On 1 Jun 2018, at 17:55, zyfdegh ***@***.***> wrote: On go1.10 GOCACHE=off go test — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.

[franciscocpg]

Using go1.11 GOCACHE=off breaks go mod.

So I am using go test -count=1.

[zignd]

The idiomatic way to bypass test caching is to use -count=1.

https://golang.org/doc/go1.10#test

Is there any documentation on the -count flag? I'd like to understand its purpose.

[myitcv]

Is there any documentation on the -count flag? I'd like to understand its purpose.

https://golang.org/cmd/go/#hdr-Testing_flags

or

go help testflag

[lengocgiang]

In vscode
"go.testFlags": ["-count=1"]

[tj]

Can't say -count is very intuitive. I keep hitting scenarios where test caching is not invalidating correctly, but I haven't pinned down any specific pattern yet. go help test vs go help testflag is a bit awkward as well IMO.

[pedromss]

Just arrived at this thread. Is a -no-cache something that could be considered for future versions?
Or maybe print ... (cached, run with -count=1)?

Something that wouldn't force people to google "go test no cache"

[EnchanterIO]

+1 @pedromss Just landed here after I was intuitively trying go test -no-cache.

[ghostsquad]

any chance this can be reopened?

[ghostsquad]

@EnchanterIO @pedromss @tj @myitcv @lengocgiang @franciscocpg @davecheney @imkos please upvote the above issue

[cristaloleg]

@ghostsquad be patient, please. There is no need to mention everyone.

[ghostsquad]

my apologies

[arvenil]

I think the best would be if we could do something like t.NoCache() to mark specific tests. Otherwise everyone will just disable cache altogether with -count=1. I run into this problem when I simply changed sql fixture file, so I would like that specific test to run without caching but I would like to cache others.