Dave Marshall

Not quite, the `overload` syntax "overloads" the a class definition, and then applies any expectations to any new instances you create of that class. So the `$faxlist` variable you have...

Sadly I think Mockery can only mock protected methods, you'd either need to make them protected or change the visibility during the test.

Hi @MartinMystikJonas Could you perhaps explain with examples? Mockery will take Hamcrest matchers, so one option is to do ``` php

Looks good to me :+1:

Honestly, I'm not sure :flushed: It's not something I've ever delved in to. Historically, I know we tried to support `__get` and `__set`, but something about them was never quite...

Sure, that sounds sensible.

As mentioned on IRC in regards to BC, anyone currently cloning a Mockery mock would have to fix up their tests: ``` php

I think my preference would be to have a global toggle that disables that deep inspection for output.

Try turning `backupGlobals` and `backupStaticAttributes` to false in your PHPUnit configuration?

No idea. Maybe try putting `@preserveGlobalState disabled` on the test case itself, rather than the class?