quii/modest-mock

modest-mock's Issues

if there is > 1 interface in the file bad things happen

handle multiple calls/returns

Currently it will only ever return one value, should be possible to do things like mock.Calls.Save[1].Firstname and mock.Returns.Save[2].err=errors.New("blah"

Acceptance test with go generate

Create a separate sub-project like cmd that has a non-trivial interface with the go generate directive set up for modest mock.

Then write some strawman tests using the automatically generated code.

This should serve as a good overall test and documentation

the testing of the generated mock sucks

Currently I use templating to generate mocks which has the following problems

• Tests are sensitive to white space
• Cant actually test the behaviour of the created mocks

There has to be a better way for this to work.

handle anonymous return types

Method() err wont work right now because err does not have a name

Have mocks based on arguments sent to the method rather than in order

To accomplish MVP there is a simple returns struct which lets you set return values for call 1 of method x, call 2 of method y, etc.

That is ok but it would be better for the users writing their tests to be able to describe when my method is called with arguments x, y it will return z. This reads better and is less susceptible to flakiness .

imports not written to mock