Testing tool doesn't show output

[mileusna]

I love "run test" option in test files.

However, after VS Code update on 1.14.2 on MacOS executing tests inside Code doesn't show up any log output. So if I have log.Println(err) it won't be printed, however, fmt.Println(err) will be printed.

[ramya-rao-a]

I am able to see the log.Println output

Can you share sample code?

[mileusna]

Sure, anything. Same testing works OK in terminal window.

It just started to happen after the VS Code upgrade.

[ramya-rao-a]

Ah! Looks like the log part is going to stderr and the fmt one goes to stdout

And in a recent commit stderr is not shown unless there is a test failure 94dadaa

@uudashr Can you take a look at this?

[mileusna]

Sorry, but this new description is incorrect, I don't see log.* output, failure or no failure. It has nothing to do with the test's outcome.

[ramya-rao-a]

@mileusna Its right there.... look at the line which has the file path... In the end it says "Failed, but no Hello"

[ramya-rao-a]

I have pushed a fix. But even with the fix the log will appear after the rest of the output. This is because like I said earlier, log is going to stderr. And while running the go test the extension can only fetch stdout and stderr separately.

[uudashr]

@ramya-rao-a your changes on the master?

[mileusna]

@ramya-rao-a Yes, the t.Error is there but not the log.Println. That is why I wrote no Hello, there is no Hello on the screen from log.Println("Hello")

This is the same code on macOS with VS Code. 1.14.0 and vscode-go v0.6.62.

And this is with upgraded VS Code 1.14.2 and vscode-go v0.6.63

In both cases t.Error makes test fail, but there is no log.Println output.

I thought that it was the version of the VS Code that is problematic with vscode-go, but now I realised that the vscode-go is also different version 0.6.63 vs 0.6.62 so I guess it is the vscode-go 0.6.63 issue, not related to the VS Code upgrade.

[uudashr]

Fixed on #1124 cc @ramya-rao-a