PHP IDE :: NuSphere Forums :: View topic

Posted: Sat Mar 08, 2014 5:23 pm

I have just upgraded to PHPUnit version 4.0.
All my tests run fine in console.
But same tests in PhpEd shows the following error

Quote:

PHP Fatal error: Class PhpED_phpUnitListener contains 1 abstract method and must therefore be declared abstract or implement the remaining methods (PHPUnit_Framework_TestListener::addRiskyTest) in C:\Users\mike\AppData\Roaming\NuSphere\PhpED\unitTest\phpUnitListener.php on line 192

It happens with any test. Even the most simple
php 5.4.25 NTS, PhpED 32bit v12.0 build 12045

Code example

Code:

class Math
{
function add($x, $y)
{
return $x+$y;
}
}

class MathTest extends \PHPUnit_Framework_TestCase
{
function testadd()
{
$obj = new \Math();
$result = $obj->add(1,2);
$this->assertEquals(3, $result);
}
}

Posted: Sun Mar 16, 2014 4:37 pm

It looks like its only me who use PHPUnit with PhpEd.
Guys do you test your php code?!
Don't you have this problem?

Posted: Thu Mar 27, 2014 3:34 am

What was the reason to upgrade to 4.0?
3.7 worked fine, didn't it?

Posted: Wed May 28, 2014 7:20 am

I had the same problem. I installed phpuint throught PhpED 12 Pro. This installed phpuint 4, which is not compatible with PhpED 12.

This is because of incompatibility PhpED_phpUnitListener.php with interface PHPUnit_Framework_TestListener, there was aded one method in 4th version. The solution is to add this row:

Code:

public function addRiskyTest(PHPUnit_Framework_Test $test, Exception $e, $time) {}

into class definition in PhpED_phpUnitListener.php file, which is in your case located at C:\Users\mike\AppData\Roaming\NuSphere\PhpED\unitTest\phpUnitListener.php

Posted: Wed May 28, 2014 1:14 pm

dmitri wrote:

What was the reason to upgrade to 4.0?
3.7 worked fine, didn't it?

Why should there be a reason not to upgrade? Wink

Posted: Sun Jun 01, 2014 2:06 pm

JCI wrote:

Why should there be a reason not to upgrade? Wink

Have you tried?

Posted: Sun Jun 08, 2014 4:19 pm

dmitri wrote:

Have you tried?

Not yet (lack of time). But that's not the point. Normally upgrading is a good thing, so I don't need a reason to upgrade a software. There might of course be reasons not to upgrade.

Should I be reluctant to upgrade PhpED in the future? Wink

Posted: Mon Jun 09, 2014 4:56 am

JCI wrote:

But that's not the point

v13 works fine with PhpUnit4.x. That's the point.

Posted: Mon Jun 09, 2014 5:03 am

dmitri wrote:

v13 works fine with PhpUnit4.x. That's the point.

So why don't you just state that instead of asking for the reason for upgrading to PHPUnit 4.0? Confused

I guess I often just don't understand your way of discussing...

Posted: Tue Jun 10, 2014 7:55 am

mikhailt asked about v12, btw

Posted: Tue Jun 10, 2014 8:26 am

dmitri wrote:

mikhailt asked about v12, btw

"Sorry for the trouble, we're working on it" would have been more helpful than "what was the reason to upgrade to 4.0" then, don't you agree? Wink

But this is getting rather off-topic.

Posted: Tue Jul 01, 2014 2:15 am

dmitri wrote:

JCI wrote:

But that's not the point

v13 works fine with PhpUnit4.x. That's the point.

Thank you!

Reason to upgrade in addition to the mentioned before (it is basically a good thing)
is that upgrade happens automatically after pear upgrades.
Then my development environments must be compatible with build environments, that are always upgraded to the last versions of all PEAR packages.