How to specify `go test` to build and run executable in exact folder but not random folder

[szmcdull]

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

$ go version
go version go1.17 windows/amd64

Does this issue reproduce with the latest release?

yes

What operating system and processor architecture are you using (go env)?

go env Output

$ go env
set GO111MODULE=
set GOARCH=amd64
set GOBIN=
set GOCACHE=C:\Users\EDZ\AppData\Local\go-build
set GOENV=C:\Users\EDZ\AppData\Roaming\go\env
set GOEXE=.exe
set GOEXPERIMENT=
set GOFLAGS=
set GOHOSTARCH=amd64
set GOHOSTOS=windows
set GOINSECURE=
set GOMODCACHE=d:\golibs\pkg\mod
set GONOPROXY=
set GONOSUMDB=
set GOOS=windows
set GOPATH=d:\golibs
set GOPRIVATE=
set GOPROXY=direct
set GOROOT=D:\Go
set GOSUMDB=sum.golang.org
set GOTMPDIR=
set GOTOOLDIR=D:\Go\pkg\tool\windows_amd64
set GOVCS=
set GOVERSION=go1.17
set GCCGO=gccgo
set AR=ar
set CC=gcc
set CXX=g++
set CGO_ENABLED=1
set GOMOD=D:\code\digifinex\acts\go.mod
set CGO_CFLAGS=-g -O2
set CGO_CPPFLAGS=
set CGO_CXXFLAGS=-g -O2
set CGO_FFLAGS=-g -O2
set CGO_LDFLAGS=-g -O2
set PKG_CONFIG=pkg-config
set GOGCCFLAGS=-m64 -mthreads -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=C:\Users\EDZ\AppData\Local\Temp\go-build2790652590=/tmp/go-build -gno-record-gcc-switches

What did you do?

D:\Go\bin\go.exe test -timeout 1m -tags debug -run ^TestActs$ acts/util -o test -count=1

What did you expect to see?

build the test to the file test and then run it

What did you see instead?

built the test to the file test but then run it in a random temp folder.
Each time I go test a new file in a new random folder is created and run. And Windows Firewall warn me to add a rule to allow it to listen on a local port (because in the test I must listen on a local port)

[szmcdull]

Please help I don't want to garbage my firewall rules

[ALTree]

Hi,

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. Thanks!

Closing here, since this is not a bug.

[szmcdull]

It is not a question. I just tried to be polite.

        -o file
            Compile the test binary to the named file.
            The test still runs (unless -c or -i is specified).

In fact it still compiles to random folder/file.test but then copies it to file. The test still runs in the temporary folder which is non-sense.

[ALTree]

-c will generate a binary for the test that you can then run from your folder. Doesn't that work?

[szmcdull]

-c will generate a binary for the test that you can then run from your folder. Doesn't that work?

I'm not sure how to reproduce a bug. I need to mock the server and debug the use case. Theoretically -c will work. But it needs extra commands and is not that convenience.