Philipp M

Shortened the interface a bit to not depend on any external stuff: ``` public interface IAerospikeClient { public Record get(Policy policy, Key key) throws AerospikeException; public Record get(Policy policy, Key...

What you can try is to not use a trait with a parameter. So instead of ``` trait Foo[T] { def create(bar: T) def create(bar: Seq[T]) } ``` try ```...

You should be extending your test suite with `org.scalamock.scalatest.proxy.MockFactory`, `org.scalamock.scalatest.MockFactory` or `org.scalamock.scalatest.MixedMockFactory`. Worth keeping in mind that the Proxy mocks are limited by what the API for proxies can supply...

why would this test fail if you wrap the call in a try/catch? it does print the exception which would usually make the test fail. Remove the try/catch and it...

you do have the choice between `mock`, which has this behaviour, and `stub`, which uses verify after test. If your test double is used in a path where exceptions are...

@KarelCemus please provide a concrete example where you think an issue exists. I pointed out the relevant documentation above regarding mock / stub behaviour and you already have a choice...

If it's useful to people then we could add the `MockFactoryRecordingUnexpectedCalls` implementation as an alternative. If you can create a pull request then that will speed things up, otherwise i'll...

You can mock a raw type like this Code: ```java import java.util.Map; public interface Foo { public void route2(Map map); public void route(Map map); } ``` Test: ```scala it should...

This is now mentioned in the FAQ: http://scalamock.org/user-guide/faq/ We will aim to make this easier to use without the additional boilerplate in a future version.

Thanks for raising this. There are some patterns where the macro based mocks struggle and this looks like another bug related to this - meaning it will be hard if...