Refactor error handling inside of deploy_vm_test
The following discussion from !119 (merged) should be addressed:
-
@steveazz started a discussion: nitpick (follow-up): I keep seeing this in some merge requests and I'm not sure I understand the pattern. For tests, I believe we should still stick to the normal Go convention where we check if the error is not nil and return early if it isn't.
addr, err := c.DeployVM(context.Background(), tc.name) if err != nil { return err } assert.Equal(t, "127.0.0.1:22", addr.String()) assert.Equal(t, "tcp", addr.Network()) return nil