You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Running :GoTest on passing tests is fine. Running :GoTest on failing tests with no logging/output is fine. Running :GoTest with a test that hits code which logs or produces output and fails the test will cause vim-go to replace the current buffer with a blank buffer.
The command status line has this in it:
"2015/11/25 13" [New file] --No lines in buffer--vim-go: [test] FAIL
Minimal code to reproduce:
main_test.go
package main
import (
"log""testing"
)
funcFoo() {
log.Printf("Foo: Computing the answer.")
}
funcTestFoo(t*testing.T) {
Foo()
t.Fail() // This prompts `go test` to present the captured output which presumably spawns the empty buffer somehow
}
You can split it up into main.go/main_test.go if you prefer.
The text was updated successfully, but these errors were encountered:
We have a fix for :GoRun which filters out these kind of problems. We need to do the same thing for this. Thanks for adding a test code, this will simplify and make it easier for me :)
It'll be in master once I've merged the neovim integration. It was handy, and the brances master and nvim are really different, I didn't want to cherry pick and and merge them forth and back. So it'll probably be in master in ~1 week.
Running
:GoTest
on passing tests is fine. Running:GoTest
on failing tests with no logging/output is fine. Running:GoTest
with a test that hits code which logs or produces output and fails the test will cause vim-go to replace the current buffer with a blank buffer.The command status line has this in it:
Minimal code to reproduce:
main_test.go
You can split it up into main.go/main_test.go if you prefer.
The text was updated successfully, but these errors were encountered: