delve_client_testing_results_20190531.md

	VSCode	GoLand
Version	VSCode 1.34.0, VSCode-go 0.10.2	GoLand 2019.2 EAP (192.4205.56)	Vim-go 1.20 (vim 8.1)
1: debug a _test.go file	PASS	PASS	PASS
2: debug a core file	FAIL	FAIL	FAIL
3: let's users specify a --log-output parameter	PASS	OK*	OK*
4. dealing with simultaneous breakpoint triggering on multiple goroutines	FAIL	FAIL	FAIL
5. dealing with breakpoints during next/step/stepout	FAIL	0.5	FAIL
6. can request a manual stop	PASS	PASS*	FAIL
7. can show disassembly and CPU registers (and keep it up to date with the current instruction)	FAIL	FAIL	FAIL
8. can show local variables of different goroutines or different frames, can execute next in a different goroutine	FAIL	PASS	FAIL
9. displays a warning when stepping through a stale executable	FAIL	FAIL	FAIL
10. setting a breakpoint on a function should result in the breakpoint being after the prologue	FAIL	FAIL*	FAIL*
11. shows shadowed variables in a way that is distinct from visible variables	PASS	PASS	FAIL
12. can evaluate arbitrary expressions	PASS	PASS	PASS
13. continue loading strings	FAIL	PASS	FAIL
14. continue loading slices	FAIL	PASS	FAIL
15. continue loading maps	FAIL	PASS	FAIL
16. continue loading pointers	PASS	PASS	FAIL
17. continue loading interfaces	PASS	PASS	FAIL
18. displaying a map[int]string should not be confusing	PASS	PASS	FAIL
19. unreadable variables should be shown as such	PASS	PASS	FAIL
20. the debugger should run fast even in presence of very deep stacks, a large number of goroutines or very large variables	FAIL	FAIL	PASS
21. dealing with compiler-autogenerated stubs	PASS	PASS	FAIL
Count	10/21	15.5/21	3/21

https://github.com/aarzilli/delve_client_testing