Strange behavior after update to 0.7.0 about mockery HOT 5 CLOSED

You're right that mocked classes now feature an __isset() method. 0.7 uses it for public property mocking.

Do you have an actual test case and the relevant class I can use to replicate the issue? If I follow what you are mocking, and how, I'll be able to diagnose the problem.

from mockery.

Hi and thanks for quick response.
I've composed two files to reproduce issue, that are quite straightforward. Let's assume we do all the application bootstrapping and Mockery setup in test case superclass.

The class itself

class Test_Magic
{
protected $_properties = array();

public function __construct()
{
}

public function __isset($property=null)
{
    return isset($this->_properties[$property]);
}

}

And a test:

class Test_MagicTest extends Shift_Test_Case
{
public function setUp()
{
parent::setUp();
$this->appBootstrap();
}

public function testIsset()
{
    $form = Mockery::mock('Zend_Form');
    $mock = Mockery::mock('Test_Magic');
}

}

This throws the BadMethodCallException: Method Test_Magic::__isset() does not exist on this mock object
When test reaches tearDown().

Please let me now if I can provide any further info or assis in any way.

from mockery.

Please excuse github markdown

from mockery.

Thanks for that. I've committed a small patch to exclude __isset() from being replaced. That seems to resolve the exception. Let me know if the git master is now running clean for you.

from mockery.

Yes, that did it. Now everything is back to normal. Thanks a lot.

from mockery.