26

I'm trying my hand at writing TDD in Go. I am however stuck at the following.

The test to write:

func TestFeatureStart(t *testing.T) {}

Implementation to test:

func (f *Feature) Start() error {
  cmd := exec.Command(f.Cmd)
  cmd.Start()
}

How would one test this simple bit? I figured I only wanted to verify that the exec library is spoken to correctly. That's the way I would do it in Java using Mockito. Can anyone help me write this test? From what I've read the usage of interfaces is suggested.

The Feature-struct only contains a string Cmd.

Jonathan Hall
  • 75,165
  • 16
  • 143
  • 189
Patrick
  • 489
  • 2
  • 8
  • 12

1 Answers1

20

You can fake the whole deal with interfaces, but you could also use fakeable functions. In the code:

var cmdStart = (*exec.Cmd).Start
func (f *Feature) Start() error {
    cmd := exec.Command(f.Cmd)
    return cmdStart(cmd)
}

In the tests:

called := false
cmdStart = func(*exec.Cmd) error { called = true; return nil }
f.Start()
if !called {
    t.Errorf("command didn't start")
}

See also: Andrew Gerrand's Testing Techniques talk.

Ainar-G
  • 34,563
  • 13
  • 93
  • 119
  • 6
    If this is used inside go routines, or your function will be called in a go routine, it'll have data race condition. Just saying so it might help someone else. –  Jan 30 '18 at 02:24