Consider using :mox instead of or along with :meck

[antonmi]

No description provided.

[danielfoxp2]

Hey, I don't have any suggestions about this enhancement. I am here just to thank you for this great work that is ESpec. ExUnit is very powerful and works very good. But I love the RSpec DSL and the ESpec is almost the same. So, for you @antonmi and every other person who put the effort to doing this happens I leave here my deepest appreciation and respect. (I was not search you on twitter to say this because I am currently log out there and I am lazy =p)

I just finish the instalation on my environment (which is not a simple environ...) and everything just worked... no headaches.

Thanks again. Hope you the best.

[antonmi]

Thanks, Daniel!
I’m very appreciated it!

[leifg]

I think the suggestion is great. Espec already works with mox but you need to write some boilerplate code and there is possible namespace collision.

import Mox
# ...
it "passes"
  defmock(MyMock, for: MyImpl)
  expect(MyMock, :call, fn -> :ok end) # expect from Mox
  MyMock.call()
  verify!(OptimizationJobMock)
end

The verify! part is not necessary in ExUnit as you can just use a setup function to hook in verify_on_exit!. But this will result in an error in espec:

** (ArgumentError) on_exit/2 callback can only be invoked from the test process
      lib/ex_unit/callbacks.ex:287: ExUnit.Callbacks.on_exit/2