tree 0aabaa65c15993ab0ce16fdad550d5dda6ed1d68
parent ab62b6c01968dbb7a7dac16ea88247349668e420
author Hana <hyangah@gmail.com> 1613055486 -0500
committer Hyang-Ah Hana Kim <hyangah@gmail.com> 1613088975 +0000

test/integration: use module mode for testing

With go1.16, the default build mode will be module mode and
the meaning of GO111MODULE='' will change. So, stop depending
on the default behavior during testing. This CL runs
extension.test.ts in GOPATH mode and module mode. And
explicitly sets GO111MODULE depending on the mode we want to
test.

Also, we place the fixtures in a temp directory when running
in module mode - that is 1) to test module mode works when
the source is outside of GOPATH/src, and 2) to avoid the conflicts
caused by the buffer (editor) in vscode when opening the same
file path twice (one for GOPATH mode, another for module mode)
if we lay out the code in the GOPATH/src. We use one instance
of vscode for all the integration test and the open file edit
buffer's lifetime is not controlled by us.

test.test.ts already tests both GOPATH and module modes.
Assuming GO111MODULE='', we switched between these two modes
by placing the test data under GOPATH/src and placing or not
placing go.mod.

For golang/vscode-go#983

Change-Id: Ia18d6672183b838203562095fefc3a3445a4cb66
Reviewed-on: https://go-review.googlesource.com/c/vscode-go/+/291313
Trust: Hyang-Ah Hana Kim <hyangah@gmail.com>
Run-TryBot: Hyang-Ah Hana Kim <hyangah@gmail.com>
TryBot-Result: kokoro <noreply+kokoro@google.com>
Reviewed-by: Rebecca Stambler <rstambler@golang.org>