Is this sandbox module actively maintained? If so, I have some updates I can provide to make it compatible with newer versions of Mockery.

Also, I'm working on a module that integrates Mockery with Libraries API so that users don't have to rely solely on having access to PECL to install the Mockery library.

Comments

GuyPaddock created an issue. See original summary.

znerol’s picture

znerol commented

No, it is not maintained. I did start that project in order to simplify testing the substantial API of Authcache 2, but then ended up using a quite similar thing but without external dependencies HookStub.inc.

I remember that I have had some serialization-issues when passing around the mockery objects between the test-runner and the child-site in some cases, but maybe that's better now(?).

Anyway, I'm more than willing to transfer module ownership to anyone willing to work with that code.

guypaddock’s picture

guypaddock commented

I wonder how ownership transfers work for Sandbox projects.

At a minimum, I have a patch I'd like to submit. :)

guypaddock’s picture

guypaddock commented
Status: Active » Fixed
guypaddock’s picture

guypaddock commented
Status: Fixed » Closed (fixed)

Thanks, @znerol.

After spending the weekend tinkering with this, I think I figured out exactly what you were talking about. If you're curious, checkout the new code in DrupalMockeryMockProxy. Part of it feels like a kludge -- because I had to break some encapsulation in the Mockery library in order to restore state -- but it seems to work pretty well.

All of my findings are documented in new docblocks on DrupalMockeryMockProxy and throughout new docblocks on the other classes in the mockery.inc file.