Can't cope with constructor pattern?

[asomers]

Can't cope with constructor pattern?

[asomers]

Yep, you're missing something. new is a static method just like any other, and you need to set an expectation for it. The confusion stems from the fact that if you hadn't explicitly defined a new method, then Mockall would've created one, which wouldn't be a regular method, requiring expectations. If you rename new to something else, then the problem will be more obvious.

In this case, you have two easy solutions:

1. In your test, use MockFooTrait::default instead of MockFooTrait::new, or
2. Create an expectation for the new method, like this:

let ctx = MockFooTrait::new_context();
ctx.expect().returning(|| MockFooTrait::default());
let mut mock_foo = MockFooTrait::new();

Hope that helps.

[michaelmarconi]

Thanks, that's perfectly clear in retrospect and solves the issue!

The thought had occurred to me but I couldn't see how to create an expectation for new before I had created the mock object. In my case, default is a fine solution.