Go to file
Suhas Karanth fe0d4f3360
Fix var name generation to avoid conflict (#145)
When the type and the package name is the same for an anonymous
parameter (ex: time.Time), and there are more than 1 such parameters,
the generated name for both was the same. And the generated code would
not be valid.

Fix the bug by ensuring the parameter name does not conflict with
package imports first before checking against other parameter names.
2021-02-14 13:10:16 +00:00
.github/workflows Replace Travis CI with GitHub Actions workflow 2020-08-16 11:56:22 +05:30
example Internal registry for disambiguated imports, vars (#141) 2021-02-01 19:20:20 +00:00
generate Internal registry for disambiguated imports, vars (#141) 2021-02-01 19:20:20 +00:00
internal Fix var name generation to avoid conflict (#145) 2021-02-14 13:10:16 +00:00
pkg/moq Fix var name generation to avoid conflict (#145) 2021-02-14 13:10:16 +00:00
.gitignore ignored dist folder 2020-09-02 10:36:09 +01:00
.goreleaser.yml fixed whitespace 2020-09-02 10:34:06 +01:00
go.mod Migrate to Go modules 2020-08-16 11:56:22 +05:30
go.sum Migrate to Go modules 2020-08-16 11:56:22 +05:30
LICENSE added credit 2016-09-01 10:30:27 +01:00
main.go made Version exported to match .goreleaser config. 2021-02-14 13:07:18 +00:00
Makefile testing releasing 2020-09-02 10:30:40 +01:00
moq-logo-small.png new logo 2016-09-01 10:13:13 +01:00
moq-logo.png new logo 2016-09-01 10:13:13 +01:00
preview.png New preview image 2017-07-11 21:31:14 +01:00
README.md Removed credit line given major contributrions 2021-02-01 19:22:42 +00:00
releasing.md testing releasing 2020-09-02 10:30:40 +01:00

moq logo build Go Report Card

Interface mocking tool for go generate.

What is Moq?

Moq is a tool that generates a struct from any interface. The struct can be used in test code as a mock of the interface.

Preview

above: Moq generates the code on the right.

You can read more in the Meet Moq blog post.

Installing

To start using Moq, just run go get:

$ go get github.com/matryer/moq

Usage

moq [flags] source-dir interface [interface2 [interface3 [...]]]
	-fmt string
		go pretty-printer: gofmt, goimports or noop (default gofmt)
	-out string
		output file (default stdout)
	-pkg string
		package name (default will infer)
	-stub
		return zero values when no mock implementation is provided, do not panic
	-skip-ensure
		suppress mock implementation check, avoid import cycle if mocks 
		generated outside of the tested package

Specifying an alias for the mock is also supported with the format 'interface:alias'

Example: moq -pkg different . MyInterface:MyMock

NOTE: source-dir is the directory where the source code (definition) of the target interface is located. It needs to be a path to a directory and not the import statement for a Go package.

In a command line:

$ moq -out mocks_test.go . MyInterface

In code (for go generate):

package my

//go:generate moq -out myinterface_moq_test.go . MyInterface

type MyInterface interface {
	Method1() error
	Method2(i int)
}

Then run go generate for your package.

How to use it

Mocking interfaces is a nice way to write unit tests where you can easily control the behaviour of the mocked object.

Moq creates a struct that has a function field for each method, which you can declare in your test code.

In this example, Moq generated the EmailSenderMock type:

func TestCompleteSignup(t *testing.T) {

	var sentTo string

	mockedEmailSender = &EmailSenderMock{
		SendFunc: func(to, subject, body string) error {
			sentTo = to
			return nil
		},
	}

	CompleteSignUp("me@email.com", mockedEmailSender)

	callsToSend := len(mockedEmailSender.SendCalls())
	if callsToSend != 1 {
		t.Errorf("Send was called %d times", callsToSend)
	}
	if sentTo != "me@email.com" {
		t.Errorf("unexpected recipient: %s", sentTo)
	}

}

func CompleteSignUp(to string, sender EmailSender) {
	// TODO: this
}

The mocked structure implements the interface, where each method calls the associated function field.

Tips

  • Keep mocked logic inside the test that is using it
  • Only mock the fields you need
  • It will panic if a nil function gets called
  • Name arguments in the interface for a better experience
  • Use closured variables inside your test function to capture details about the calls to the methods
  • Use .MethodCalls() to track the calls
  • Use go:generate to invoke the moq command
  • If Moq fails with a go/format error, it indicates the generated code was not valid. You can run the same command with -fmt noop to print the generated source code without attempting to format it. This can aid in debugging the root cause.

License

The Moq project (and all code) is licensed under the MIT License.

Moq was created by Mat Ryer and David Hernandez, with ideas lovingly stolen from Ernesto Jimenez. Featuring a major refactor by @sudo-suhas, as well as lots of other contributors.

The Moq logo was created by Chris Ryer and is licensed under the Creative Commons Attribution 3.0 License.