1
0
Fork 0
mirror of synced 2024-11-29 20:25:34 -05:00
ultimate-vim/sources_non_forked/vim-go/autoload/go/test.vim

330 lines
12 KiB
VimL
Raw Normal View History

2018-12-17 06:28:27 -05:00
" don't spam the user when Vim is started in Vi compatibility mode
let s:cpo_save = &cpo
set cpo&vim
2017-07-06 08:57:35 -04:00
" Test runs `go test` in the current directory. If compile is true, it'll
" compile the tests instead of running them (useful to catch errors in the
2018-02-04 06:35:08 -05:00
" test files). Any other argument is appended to the final `go test` command.
2017-07-06 08:57:35 -04:00
function! go#test#Test(bang, compile, ...) abort
2018-06-14 06:31:12 -04:00
let args = ["test", '-tags', go#config#BuildTags()]
2017-07-06 08:57:35 -04:00
" don't run the test, only compile it. Useful to capture and fix errors.
if a:compile
let testfile = tempname() . ".vim-go.test"
call extend(args, ["-c", "-o", testfile])
endif
2017-07-06 08:57:35 -04:00
if a:0
let goargs = a:000
" do not expand for coverage mode as we're passing the arg ourself
if a:1 != '-coverprofile'
" expand all wildcards(i.e: '%' to the current file name)
let goargs = map(copy(a:000), "expand(v:val)")
endif
call extend(args, goargs, 1)
else
" only add this if no custom flags are passed
2018-06-14 06:31:12 -04:00
let timeout = go#config#TestTimeout()
2017-07-06 08:57:35 -04:00
call add(args, printf("-timeout=%s", timeout))
endif
2019-05-17 10:09:13 -04:00
if go#config#TermEnabled()
call go#term#new(a:bang, ["go"] + args, s:errorformat())
2019-08-22 11:36:17 -04:00
return
2018-08-25 12:13:42 -04:00
endif
2018-09-24 20:40:17 -04:00
if go#util#has_job()
2017-07-06 08:57:35 -04:00
" use vim's job functionality to call it asynchronously
2018-07-19 08:52:53 -04:00
let job_options = {
2017-07-06 08:57:35 -04:00
\ 'bang': a:bang,
2018-07-19 08:52:53 -04:00
\ 'for': 'GoTest',
\ 'statustype': 'test',
\ 'errorformat': s:errorformat(),
2017-07-06 08:57:35 -04:00
\ }
2018-07-19 08:52:53 -04:00
if a:compile
let job_options.statustype = 'compile ' . job_options.statustype
2017-07-06 08:57:35 -04:00
endif
2018-07-19 08:52:53 -04:00
call s:test_job(['go'] + args, job_options)
return
2017-07-06 08:57:35 -04:00
endif
2018-09-24 20:40:17 -04:00
if go#config#EchoCommandInfo()
if a:compile
call go#util#EchoProgress("compiling tests ...")
else
call go#util#EchoProgress("testing...")
endif
endif
2017-07-06 08:57:35 -04:00
call go#cmd#autowrite()
redraw
2018-06-14 06:31:12 -04:00
let l:cmd = ['go'] + l:args
2019-03-08 06:04:56 -05:00
let [l:out, l:err] = go#util#ExecInDir(l:cmd)
2018-02-04 06:35:08 -05:00
" TODO(bc): When the output is JSON, the JSON should be run through a
" filter to produce lines that are more easily described by errorformat.
2017-07-06 08:57:35 -04:00
let l:listtype = go#list#Type("GoTest")
2017-07-06 08:57:35 -04:00
let cd = exists('*haslocaldir') && haslocaldir() ? 'lcd ' : 'cd '
let dir = getcwd()
execute cd fnameescape(expand("%:p:h"))
2018-06-14 06:31:12 -04:00
if l:err != 0
2019-05-17 10:09:13 -04:00
let l:winid = win_getid(winnr())
2018-06-14 06:31:12 -04:00
call go#list#ParseFormat(l:listtype, s:errorformat(), split(out, '\n'), l:cmd)
2018-02-04 06:35:08 -05:00
let errors = go#list#Get(l:listtype)
2017-07-06 08:57:35 -04:00
call go#list#Window(l:listtype, len(errors))
2019-05-17 10:09:13 -04:00
if empty(errors)
2017-07-06 08:57:35 -04:00
" failed to parse errors, output the original content
call go#util#EchoError(out)
2019-05-17 10:09:13 -04:00
elseif a:bang
call win_gotoid(l:winid)
else
call go#list#JumpToFirst(l:listtype)
2017-07-06 08:57:35 -04:00
endif
else
call go#list#Clean(l:listtype)
if a:compile
call go#util#EchoSuccess("[test] SUCCESS")
2017-07-06 08:57:35 -04:00
else
call go#util#EchoSuccess("[test] PASS")
2017-07-06 08:57:35 -04:00
endif
endif
execute cd . fnameescape(dir)
endfunction
" Testfunc runs a single test that surrounds the current cursor position.
" Arguments are passed to the `go test` command.
function! go#test#Func(bang, ...) abort
" search flags legend (used only)
" 'b' search backward instead of forward
" 'c' accept a match at the cursor position
" 'n' do Not move the cursor
" 'W' don't wrap around the end of the file
"
" for the full list
" :help search
let test = search('func \(Test\|Example\)', "bcnW")
if test == 0
echo "vim-go: [test] no test found immediate to cursor"
return
end
let line = getline(test)
let name = split(split(line, " ")[1], "(")[0]
let args = [a:bang, 0, "-run", name . "$"]
if a:0
call extend(args, a:000)
2018-02-04 06:35:08 -05:00
else
" only add this if no custom flags are passed
2018-06-14 06:31:12 -04:00
let timeout = go#config#TestTimeout()
2018-02-04 06:35:08 -05:00
call add(args, printf("-timeout=%s", timeout))
2017-07-06 08:57:35 -04:00
endif
call call('go#test#Test', args)
endfunction
2018-07-19 08:52:53 -04:00
function! s:test_job(cmd, args) abort
2017-07-06 08:57:35 -04:00
" autowrite is not enabled for jobs
call go#cmd#autowrite()
2018-07-19 08:52:53 -04:00
call go#job#Spawn(a:cmd, a:args)
2017-07-06 08:57:35 -04:00
endfunction
2018-06-14 06:31:12 -04:00
let s:efm = ""
let s:go_test_show_name = 0
2018-02-04 06:35:08 -05:00
function! s:errorformat() abort
" NOTE(arslan): once we get JSON output everything will be easier :).
" TODO(bc): When the output is JSON, the JSON should be run through a
" filter to produce lines that are more easily described by errorformat.
" https://github.com/golang/go/issues/2981.
let goroot = go#util#goroot()
2018-06-14 06:31:12 -04:00
let show_name = go#config#TestShowName()
2018-02-04 06:35:08 -05:00
if s:efm != "" && s:go_test_show_name == show_name
return s:efm
endif
let s:go_test_show_name = show_name
2017-07-06 08:57:35 -04:00
2018-02-04 06:35:08 -05:00
" each level of test indents the test output 4 spaces. Capturing groups
" (e.g. \(\)) cannot be used in an errorformat, but non-capturing groups can
" (e.g. \%(\)).
2018-09-24 20:40:17 -04:00
let indent = '%\\%( %\\)'
2018-02-04 06:35:08 -05:00
" ignore `go test -v` output for starting tests
2018-06-14 06:31:12 -04:00
let format = "%-G=== RUN %.%#"
2018-02-04 06:35:08 -05:00
" ignore `go test -v` output for passing tests
2018-09-24 20:40:17 -04:00
let format .= ",%-G" . indent . "%#--- PASS: %.%#"
2017-07-06 08:57:35 -04:00
2018-02-04 06:35:08 -05:00
" Match failure lines.
2019-08-22 11:36:17 -04:00
" Example failures start with '--- FAIL: ', followed by the example name
" followed by a space , followed by the duration of the example in
" parantheses. They aren't nested, though, so don't check for indentation.
" The errors from them also aren't indented and don't report file location
" or line numbers, so those won't show up. This will at least let the user
" know which example failed, though.
let format .= ',%G--- FAIL: %\\%(Example%\\)%\\@=%m (%.%#)'
2018-02-04 06:35:08 -05:00
" Test failures start with '--- FAIL: ', followed by the test name followed
2019-08-22 11:36:17 -04:00
" by a space, followed by the duration of the test in parentheses.
2018-02-04 06:35:08 -05:00
"
" e.g.:
" '--- FAIL: TestSomething (0.00s)'
if show_name
2018-09-24 20:40:17 -04:00
let format .= ",%G" . indent . "%#--- FAIL: %m (%.%#)"
2018-02-04 06:35:08 -05:00
else
2018-09-24 20:40:17 -04:00
let format .= ",%-G" . indent . "%#--- FAIL: %.%#"
2018-02-04 06:35:08 -05:00
endif
2018-09-24 20:40:17 -04:00
" Go 1.10 test output {{{1
2018-02-04 06:35:08 -05:00
" Matches test output lines.
"
" All test output lines start with the test indentation and a tab, followed
" by the filename, a colon, the line number, another colon, a space, and the
" message. e.g.:
" '\ttime_test.go:30: Likely problem: the time zone files have not been installed.'
2018-09-24 20:40:17 -04:00
let format .= ",%A" . indent . "%#%\\t%\\+%f:%l: %m"
2018-02-04 06:35:08 -05:00
" also match lines that don't have a message (i.e. the message begins with a
" newline or is the empty string):
" e.g.:
" t.Errorf("\ngot %v; want %v", actual, expected)
" t.Error("")
2018-09-24 20:40:17 -04:00
let format .= ",%A" . indent . "%#%\\t%\\+%f:%l: "
2018-02-04 06:35:08 -05:00
" Match the 2nd and later lines of multi-line output. These lines are
" indented the number of spaces for the level of nesting of the test,
" followed by two tabs, followed by the message.
"
" Treat these lines as if they are stand-alone lines of output by using %G.
" It would also be valid to treat these lines as if they were the
" continuation of a multi-line error by using %C instead of %G, but that
" would also require that all test errors using a %A or %E modifier to
" indicate that they're multiple lines of output, but in that case the lines
" get concatenated in the quickfix list, which is not what users typically
" want when writing a newline into their test output.
2018-09-24 20:40:17 -04:00
let format .= ",%G" . indent . "%#%\\t%\\{2}%m"
" }}}1
" Go 1.11 test output {{{1
" Match test output lines similarly to Go 1.10 test output lines, but they
" use an indent level where the Go 1.10 test output uses tabs, so they'll
" always have at least one level indentation...
let format .= ",%A" . indent . "%\\+%f:%l: %m"
let format .= ",%A" . indent . "%\\+%f:%l: "
let format .= ",%G" . indent . "%\\{2\\,}%m"
" }}}1
2018-02-04 06:35:08 -05:00
" set the format for panics.
" handle panics from test timeouts
let format .= ",%+Gpanic: test timed out after %.%\\+"
" handle non-timeout panics
" In addition to 'panic', check for 'fatal error' to support older versions
" of Go that used 'fatal error'.
"
" Panics come in two flavors. When the goroutine running the tests panics,
" `go test` recovers and tries to exit more cleanly. In that case, the panic
" message is suffixed with ' [recovered]'. If the panic occurs in a
" different goroutine, it will not be suffixed with ' [recovered]'.
let format .= ",%+Afatal error: %.%# [recovered]"
let format .= ",%+Apanic: %.%# [recovered]"
let format .= ",%+Afatal error: %.%#"
let format .= ",%+Apanic: %.%#"
" Match address lines in stacktraces produced by panic.
"
" Address lines in the stack trace have leading tabs, followed by the path
" to the file. The file path is followed by a colon and then the line number
" within the file where the panic occurred. After that there's a space and
" hexadecimal number.
"
" e.g.:
" '\t/usr/local/go/src/time.go:1313 +0x5d'
2019-03-27 11:08:56 -04:00
" panicaddress and readyaddress are identical except for
2018-02-04 06:35:08 -05:00
" panicaddress sets the filename and line number.
let panicaddress = "%\\t%f:%l +0x%[0-9A-Fa-f]%\\+"
let readyaddress = "%\\t%\\f%\\+:%\\d%\\+ +0x%[0-9A-Fa-f]%\\+"
" stdlib address is identical to readyaddress, except it matches files
" inside GOROOT.
let stdlibaddress = "%\\t" . goroot . "%\\f%\\+:%\\d%\\+ +0x%[0-9A-Fa-f]%\\+"
" Match and ignore the running goroutine line.
let format .= ",%-Cgoroutine %\\d%\\+ [running]:"
" Match address lines that refer to stdlib, but consider them informational
" only. This is to catch the lines after the first address line in the
" running goroutine of a panic stack trace. Ideally, this wouldn't be
" necessary, but when a panic happens in the goroutine running a test, it's
" recovered and another panic is created, so the stack trace actually has
" the line that caused the original panic a couple of addresses down the
" stack.
let format .= ",%-C" . stdlibaddress
" Match address lines in the first matching goroutine. This means the panic
" message will only be shown as the error message in the first address of
" the running goroutine's stack.
let format .= ",%Z" . panicaddress
2019-03-27 11:08:56 -04:00
" Match and ignore errors from runtime.goparkunlock(). These started
" appearing in stack traces from Go 1.12 test timeouts.
let format .= ",%-Gruntime.goparkunlock(%.%#"
let format .= ",%-G%\\t" . goroot . "%\\f%\\+:%\\d%\\+"
2018-02-04 06:35:08 -05:00
" Match and ignore panic address without being part of a multi-line message.
" This is to catch those lines that come after the top most non-standard
" library line in stack traces.
let format .= ",%-G" . readyaddress
" Match and ignore exit status lines (produced when go test panics) whether
" part of a multi-line message or not, because these lines sometimes come
" before and sometimes after panic stacktraces.
let format .= ",%-Cexit status %[0-9]%\\+"
"let format .= ",exit status %[0-9]%\\+"
2018-09-24 20:40:17 -04:00
" Match and ignore failure lines whether part of a multi-line message
2018-02-04 06:35:08 -05:00
" or not, because these lines sometimes come before and sometimes after
" panic stacktraces.
let format .= ",%-CFAIL%\\t%.%#"
"let format .= ",FAIL%\\t%.%#"
2018-09-24 20:40:17 -04:00
" match compiler errors.
" These are very smilar to errors from <=go1.10 test output, but lack
" leading tabs for the first line of an error, and subsequent lines only
" have one tab instead of two.
2018-06-14 06:31:12 -04:00
let format .= ",%A%f:%l:%c: %m"
let format .= ",%A%f:%l: %m"
" It would be nice if this weren't necessary, but panic lines from tests are
" prefixed with a single leading tab, making them very similar to 2nd and
" later lines of a multi-line compiler error. Swallow it so that it doesn't
2019-03-27 11:08:56 -04:00
" cause a quickfix entry since the next %G entry can add a quickfix entry
" for 2nd and later lines of a multi-line compiler error.
2018-06-14 06:31:12 -04:00
let format .= ",%-C%\\tpanic: %.%#"
let format .= ",%G%\\t%m"
2018-02-04 06:35:08 -05:00
" Match and ignore everything else in multi-line messages.
let format .= ",%-C%.%#"
" Match and ignore everything else not in a multi-line message:
let format .= ",%-G%.%#"
let s:efm = format
return s:efm
2017-07-06 08:57:35 -04:00
endfunction
2018-12-17 06:28:27 -05:00
" restore Vi compatibility settings
let &cpo = s:cpo_save
unlet s:cpo_save
2017-07-06 08:57:35 -04:00
" vim: sw=2 ts=2 et