PHP IDE :: NuSphere Forums :: View topic - Debugging issues of PHPUnit tests in PhpED

Posted: Tue Jul 02, 2013 6:59 am

PhpED has issues when debugging (not running) some type of tests with PHPUnit.
For example mock of a class with multiple methods.

Code:

class MyClass
{
function root($x)
{
$base = $this->getRootBase();
$presision = $this->getConfig('presision');
$root = pow($x, 1/$base);
return round($root, $presision);
}

protected function getConfig($key)
{
$aConfig['presision'] = 2;
return $aConfig[$key];
}

protected function getRootBase()
{
return 3;
}
}

We need a mock of MyClass with two methods:

Code:

class MyClassTest extends PHPUnit_Framework_TestCase
{
function testroot()
{
$mockMy = $this->getMock('\MyClass', array('getConfig', 'getRootBase'));

$mockMy->expects($this->any())
->method('getConfig')
->with('presision')
->will($this->returnValue(2));

$mockMy->expects($this->any())
->method('getRootBase')
->will($this->returnValue(2));

$this->assertEquals(2.83, $mockMy->root(8));
}
}

When I try to debug a such test in PhpED I get an error message:
Project ... raised exception class PHPUnit_Framework_ComparisionFailure with message: "Failed asserting that strings are equal."
This happens only while debugging. Running such tests has no problem in PhpED.

Posted: Wed Jul 03, 2013 7:52 am

That's because PHPEd handles all exceptions thrown during a debug session.

You can filter those messages by the exception's namespace in project's debugging properties.

Posted: Wed Jul 03, 2013 5:12 pm

That's right that PhpED handles exceptions. But there should not be any exceptions in this code.
It is totally legal code.
Something goes wrong only while debugging when comparing mock-methods names when there are more then one method. And that should not be.

Posted: Wed Jul 03, 2013 5:33 pm

I don't think that's the case.

Nothing goes wrong when debugging session is enabled. It's only alerting you to an exception that otherwise would have been caught.

What happens if you catch the exception and click "Break" button and continue in the debugger? My bet is that you will find yourself in catch () {....} block.