Cmd wraps exec.Cmd and represents a binary being prepared or run. In the typical end-to-end testing scenario, Cmd will end up running two times: 1. from TestMain when the test suite is first executed. At this point it will spawn the already-compiled test binary (itself) again and... 2. from the sp
source not stored for this graph (policy: none)
nothing calls this directly
no outgoing calls
no test coverage detected