Realtime output of "run test(s)" code lens

[ronakg]

Is your feature request related to a problem? Please describe.
When I trigger a test or multiple tests, the output of the tests shows up only after all tests have finished.

Describe the solution you'd like
The output of go test should be displayed in realtime in the output window like how it works in a terminal.

Describe alternatives you've considered
Running the go test command manually in a terminal is an option, but I don't get the code coverage from that.

[gopherbot]

Change https://golang.org/cl/269917 mentions this issue: src/goTest: always mark workspace uri as directory

[hyangah]

@ronakg Thanks for the report. For workspace testing, I sent the fix for a bug that caused unnecessary buffering.
In a single file test mode, go test buffers t.Log unless -v is specified. (https://golang.org/doc/go1.14#go-command).
#900 discusses another recently discovered issue related to streaming test output even with -v.

The purpose of buffering is to expand the file names in the failed test output message to the full paths, so the convenient file link feature of vscode can work. The info necessary for the file name expansion (package name) is at the end of each test, so it can't be perfectly real time.

[ronakg]

@hyangah Thanks for letting me know. I'm already using -v for all my test runs by having this configuration.

    "go.testFlags": [
        "-v"
    ]

The purpose of buffering is to expand the file names in the failed test output message to the full paths, so the convenient file link feature of vscode can work. The info necessary for the file name expansion (package name) is at the end of each test, so it can't be perfectly real time.

Is it possible to have an option to chose this behavior? For me personally, having real-time output of t.Log, fmt.Print* and my own logs is far more important than having full paths for filenames in the output.