2016-10-31 16:40 GMT+01:00 Sean P. DeNigris <sean@clipperadams.com>:

> You can look at features here:
> http://dionisiydk.blogspot.fr/2016/04/new-version-of-mocketry-30.html.

Ah, yes. I seem to recall one major hurdle for me was that each test needed
everything wrapped in a block. Is that still the case? Could this be hidden
somewhere in the mechanism?

It was changed in version 3. Now blocks could be used to easily get multiple mocks (as block arguments) or to validate group of messages.

But it is not necessary. You can just work with separate mocks created by "Mock new". So you don't need blocks generally.

I thought it was seen in my blog post.

��

I also wonder whether Mocketry could be easily
integrated with Phexample, as I really love the stacked test concept...

Months ago I committed version of Phexample based on StateSpecs (new config in Phexample repo). So all projects are compatible.

��

Denis Kudriashov wrote
> BabyMock could not be treated as modern mock library just because it uses
> symbols instead of normal message sends. Even C# and Java mocks are based
> on normal messages.��

In practice, I don't see why this makes such a big difference. What am I
missing?

For me it is just not readable, more code to write.

But also it makes tests fragile for refactorings. Try to change signature of method: new argument, remove argument, switch argument places. And tests will be broken (because mocks use symbols and not real messages).