This PR introduces a distinction between forward slashes (unix) and backslashes (windows) in filepaths.
However, there's a huge problem with ANSI codes and other stuff is garbling up the JSON output from go test -json. Very strange. Only happens on Windows (Powershell). A workaround is to use gotestsum as runner, which will then write to JSON file without a console roundtrip:
# make gotestsum available on $PATH by installing it
go install gotest.tools/gotestsum@latest
Then set the (for now undocumented/experimental) runner option, and instruct it to use gotestsum instead of go test:
This PR introduces a distinction between forward slashes (unix) and backslashes (windows) in filepaths.
However, there's a huge problem with ANSI codes and other stuff is garbling up the JSON output from
go test -json
. Very strange. Only happens on Windows (Powershell). A workaround is to usegotestsum
as runner, which will then write to JSON file without a console roundtrip:Then set the (for now undocumented/experimental)
runner
option, and instruct it to usegotestsum
instead ofgo test
:Fixes: #147