Debugging tests with delve

debugging go delve
SpiderRico picture SpiderRico · Apr 13, 2017 · Viewed 10.2k times · Source

I'm using "go test -v" to run bunch of unit tests. I'd like to debug them using delve. When I try to run debugger, I get an "Can not debug non-main package" error. So, how can I debug unit tests using delve debugger ?

Answer

Martin Tournoij picture Martin Tournoij · Apr 14, 2017

Use dlv test:

$ dlv test -- -test.v
Type 'help' for list of commands.
(dlv) continue
=== RUN   TestReadFileError
--- PASS: TestReadFileError (0.00s)
=== RUN   TestReadFile
--- PASS: TestReadFile (0.00s)
[..]
PASS
Process 8014 has exited with status 0
(dlv) quit
Process 8014 has exited with status 0

You can also pass -test.run to select tests to run (just like go test -run).

Internally, this is the same as Flimzy's answer (it compiles the test binary with go test -c), but more streamlined and won't leave .test files for you to clean up.

Related questions

Does any golang interactive debugger exist?

The title pretty much sums it up. I am trying out Go and I really miss being able to set breakpoints and step in/over/out as much as I want within an interactive environment. I know I can use …

Read More
How to set up debugging in GoLand?

I am trying out GoLand and hear that the debugger is supposedly awesome, but I can’t find any documentation explaining how to set it up (GoLand is in preview stage, so that’s not really surprising). My use case: …

Read More
How to get the stacktrace of a panic (and store as a variable)

As we all know, panics produce a stacktrace to stdout (Playground link).: panic: runtime error: index out of range goroutine 1 [running]: main.main() /tmp/sandbox579134920/main.go:9 +0x20 And it seems when you recover from a panic, recover() returns only …

Read More