gmane.comp.php.phpunit.user

The mailinglist will be discontinued

Sebastian Bergmann — 2012-01-14T10:37:23

 Hello!

 The mailserver that is used to serve this mailinglist will soon be
 retired by Tobias Schlitt, who graciously donated it for the last couple
 of years.

 As the traffic on the PHPUnit mailinglists is not anymore what it used
 to be, I decided to discontinue them in favour of IRC, Twitter,
 StackOverflow, etc.

 Best,
Sebastian

RE: PhpUnit on Windows

Jeremy Cook — 2012-01-11T13:54:00

Hmm, strange. There's no error output at all? Can you check in your error
logs to see if there's anything at all there? Also, and this is a long shot,
your code seems to be using old PHP 4 conventions (for example, using the
name of the class as the name of the constructor method instead of
__construct()). Sebastian also noted that you were using constructs from old
versions of PHPUnit. Are you definitely running PHP5 and the latest version
of PHPUnit (3.6.x I think)?

 

From: Yevgen VORONETSKYY [mailto:voronetskyy< at >gmail.com] 
Sent: January-11-12 3:56 AM
To: user< at >phpunit.de
Subject: Re: [phpunit-user] PhpUnit on Windows

 

Sorry, guys, but it's always not working. Nothing after running the
phpunit...

After your comments my code looks like :

<?php

require_once 'PHPUnit/Autoload.php';
class ValidateTest extends PHPUnit_Framework_TestCase
{
    // contains the object handle of the string class
    var $abc;

    // constructor of the test suite
    function ValidateTest($name) {

       $this->PHPUnit_TestCase($name);
    }

    // called before the test functions will be executed
    // this function is defined in PHPUnit_TestCase and overwritten
    // here
    function setUp() {
        // create a new instance of String with the
        // string 'abc'
        $this->abc = 'abc';
    }

    // called after the test functions are executed
    // this function is defined in PHPUnit_TestCase and overwritten
    // here
    function tearDown() {
        // delete your instance
        unset($this->abc);
    }

    // test the toString function
    function testToString() {
        $result = $this->abc->toString('contains %s');
        $expected = 'contains abc';
        $this->assertTrue($result == $expected);
    }

    // test the copy function
    function testCopy() {
      $abc2 = $this->abc->copy();
      $this->assertEquals($abc2, $this->abc);
    }

  }
?> 

 

On 10 January 2012 19:46, Jeremy Cook <jeremycook0< at >gmail.com> wrote:

What David says. J

 

Also, assuming you're using the latest version of PHPUnit and that the path
to your PEAR installation is included in PHP's include path (which it seems
to be in your case), change the require statement line to be 'require_once
'PHPUnit/Autoload.php';'. That will make sure that the PHPUnit autoloader is
registered so that any dependencies that PHPUnit has can be loaded.

 

From: David Harkness [mailto:david.h< at >highgearmedia.com] 
Sent: January-10-12 12:32 PM
To: user< at >phpunit.de
Subject: Re: [phpunit-user] PhpUnit on Windows

 

If that is your real code, you are extending the wrong class that doesn't
exist. It must read

.... extends PHPUnit_Framework_TestCase

On Jan 10, 2012 9:24 AM, "Voronetskyy Yevgen" <voronetskyy< at >gmail.com> wrote:

I'm novice in PHP programming...

 

Below the code of my test class:

<?php

require_once 'PHPUnit.php';

class ValidateTest extends PHPUnit_TestCase
{
    // contains the object handle of the string class
    var $abc;

    // constructor of the test suite
    function ValidateTest($name) {

       $this->PHPUnit_TestCase($name);
    }

    // called before the test functions will be executed
    // this function is defined in PHPUnit_TestCase and overwritten
    // here
    function setUp() {
        // create a new instance of String with the
        // string 'abc'
        $this->abc = 'abc';
    }

    // called after the test functions are executed
    // this function is defined in PHPUnit_TestCase and overwritten
    // here
    function tearDown() {
        // delete your instance
        unset($this->abc);
    }

    // test the toString function
    function testToString() {
        $result = $this->abc->toString('contains %s');
        $expected = 'contains abc';
        $this->assertTrue($result == $expected);
    }

    // test the copy function
    function testCopy() {
      $abc2 = $this->abc->copy();
      $this->assertEquals($abc2, $this->abc);
    }

  }
?> 



On Jan 10, 2012, at 7:18 PM, Jeremy Cook wrote:

Re: PhpUnit on Windows

Yevgen VORONETSKYY — 2012-01-11T08:56:22

Sorry, guys, but it's always not working. Nothing after running the
phpunit...
After your comments my code looks like :

<?php
require_once 'PHPUnit/Autoload.php';
class ValidateTest extends PHPUnit_Framework_TestCase
{
    // contains the object handle of the string class
    var $abc;
    // constructor of the test suite
    function ValidateTest($name) {
       $this->PHPUnit_TestCase($name);
    }
    // called before the test functions will be executed
    // this function is defined in PHPUnit_TestCase and overwritten
    // here
    function setUp() {
        // create a new instance of String with the
        // string 'abc'
        $this->abc = 'abc';
    }
    // called after the test functions are executed
    // this function is defined in PHPUnit_TestCase and overwritten
    // here
    function tearDown() {
        // delete your instance
        unset($this->abc);
    }
    // test the toString function
    function testToString() {
        $result = $this->abc->toString('contains %s');
        $expected = 'contains abc';
        $this->assertTrue($result == $expected);
    }
    // test the copy function
    function testCopy() {
      $abc2 = $this->abc->copy();
      $this->assertEquals($abc2, $this->abc);
    }
  }
?>


On 10 January 2012 19:46, Jeremy Cook <jeremycook0< at >gmail.com> wrote:

Re: PhpUnit on Windows

Zechariah Campbell — 2012-01-10T20:43:55

How do I unsubscribe from this thread?

On Tue, Jan 10, 2012 at 2:39 PM, Jeremiah Dodds <jeremiah.dodds< at >gmail.com>wrote:

Re: PhpUnit on Windows

Jeremiah Dodds — 2012-01-10T20:39:54

On Tue, Jan 10, 2012 at 11:54 AM, Voronetskyy Yevgen
<voronetskyy< at >gmail.com> wrote:

I have had this happen in PHPUnit before (intermittently, and normally
only for the length of one point release) when I had xdebug.auto_trace
and/or xdebug.default_enable/xdebug.show_session_trace on.

Re: PhpUnit on Windows

Sebastian Bergmann — 2012-01-10T20:26:19

  The above look like PHPUnit 1.x code (~ 10 years ago). Please have a
  look at the current documentation at

    http://www.phpunit.de/manual/current/en/

Re: PhpUnit on Windows

Voronetskyy Yevgen — 2012-01-10T18:10:41

David & Jeremy,
Thanks for your insights. I'll try your advice tomorrow. Have a nice day, guys.
I didn't expect such fast responses :)
Thanks all for your activity

--
Voronetskyy Yevgen

Il giorno 10 janv. 2012, alle ore 19:46, "Jeremy Cook" <jeremycook0< at >gmail.com> ha scritto:

RE: PhpUnit on Windows

Jeremy Cook — 2012-01-10T17:46:21

What David says. J

 

Also, assuming you're using the latest version of PHPUnit and that the path
to your PEAR installation is included in PHP's include path (which it seems
to be in your case), change the require statement line to be 'require_once
'PHPUnit/Autoload.php';'. That will make sure that the PHPUnit autoloader is
registered so that any dependencies that PHPUnit has can be loaded.

 

From: David Harkness [mailto:david.h< at >highgearmedia.com] 
Sent: January-10-12 12:32 PM
To: user< at >phpunit.de
Subject: Re: [phpunit-user] PhpUnit on Windows

 

If that is your real code, you are extending the wrong class that doesn't
exist. It must read

.... extends PHPUnit_Framework_TestCase

On Jan 10, 2012 9:24 AM, "Voronetskyy Yevgen" <voronetskyy< at >gmail.com> wrote:

I'm novice in PHP programming...

 

Below the code of my test class:

<?php

require_once 'PHPUnit.php';

class ValidateTest extends PHPUnit_TestCase
{
    // contains the object handle of the string class
    var $abc;

    // constructor of the test suite
    function ValidateTest($name) {

       $this->PHPUnit_TestCase($name);
    }

    // called before the test functions will be executed
    // this function is defined in PHPUnit_TestCase and overwritten
    // here
    function setUp() {
        // create a new instance of String with the
        // string 'abc'
        $this->abc = 'abc';
    }

    // called after the test functions are executed
    // this function is defined in PHPUnit_TestCase and overwritten
    // here
    function tearDown() {
        // delete your instance
        unset($this->abc);
    }

    // test the toString function
    function testToString() {
        $result = $this->abc->toString('contains %s');
        $expected = 'contains abc';
        $this->assertTrue($result == $expected);
    }

    // test the copy function
    function testCopy() {
      $abc2 = $this->abc->copy();
      $this->assertEquals($abc2, $this->abc);
    }

  }
?> 



On Jan 10, 2012, at 7:18 PM, Jeremy Cook wrote:

Re: PhpUnit on Windows

David Harkness — 2012-01-10T17:32:16

If that is your real code, you are extending the wrong class that doesn't
exist. It must read

.... extends PHPUnit_Framework_TestCase

On Jan 10, 2012 9:24 AM, "Voronetskyy Yevgen" <voronetskyy< at >gmail.com> wrote:

I'm novice in PHP programming...

Below the code of my test class:

<?php

require_once 'PHPUnit.php';

class ValidateTest extends PHPUnit_TestCase
{
    // contains the object handle of the string class
    var $abc;

    // constructor of the test suite
    function ValidateTest($name) {

       $this->PHPUnit_TestCase($name);
    }

    // called before the test functions will be executed
    // this function is defined in PHPUnit_TestCase and overwritten
    // here
    function setUp() {
        // create a new instance of String with the
        // string 'abc'
        $this->abc = 'abc';
    }

    // called after the test functions are executed
    // this function is defined in PHPUnit_TestCase and overwritten
    // here
    function tearDown() {
        // delete your instance
        unset($this->abc);
    }

    // test the toString function
    function testToString() {
        $result = $this->abc->toString('contains %s');
        $expected = 'contains abc';
        $this->assertTrue($result == $expected);
    }

    // test the copy function
    function testCopy() {
      $abc2 = $this->abc->copy();
      $this->assertEquals($abc2, $this->abc);
    }

  }
?>



On Jan 10, 2012, at 7:18 PM, Jeremy Cook wrote:

Re: PhpUnit on Windows

Voronetskyy Yevgen — 2012-01-10T17:24:22

I'm novice in PHP programming...

Below the code of my test class:
<?php

require_once 'PHPUnit.php';

class ValidateTest extends PHPUnit_TestCase
{
    // contains the object handle of the string class
    var $abc;

    // constructor of the test suite
    function ValidateTest($name) {

       $this->PHPUnit_TestCase($name);
    }

    // called before the test functions will be executed
    // this function is defined in PHPUnit_TestCase and overwritten
    // here
    function setUp() {
        // create a new instance of String with the
        // string 'abc'
        $this->abc = 'abc';
    }

    // called after the test functions are executed
    // this function is defined in PHPUnit_TestCase and overwritten
    // here
    function tearDown() {
        // delete your instance
        unset($this->abc);
    }

    // test the toString function
    function testToString() {
        $result = $this->abc->toString('contains %s');
        $expected = 'contains abc';
        $this->assertTrue($result == $expected);
    }

    // test the copy function
    function testCopy() {
      $abc2 = $this->abc->copy();
      $this->assertEquals($abc2, $this->abc);
    }

  }
?> 

On Jan 10, 2012, at 7:18 PM, Jeremy Cook wrote:

RE: PhpUnit on Windows

Jeremy Cook — 2012-01-10T17:18:23

Hi,

 

Are you definitely extending PHPUnit_Framework_TestCase (or one of the other
PHPUnit test classes) in your test class and following the correct naming
convention? It sounds like PHPUnit is properly installed but it's not seing
any test classes for some reason.

 

Jeremy.

 

From: Voronetskyy Yevgen [mailto:voronetskyy< at >gmail.com] 
Sent: January-10-12 12:14 PM
To: user< at >phpunit.de
Cc: Demian Katz
Subject: Re: [phpunit-user] PhpUnit on Windows

 

No, the output is empty.

 

 

On Jan 10, 2012, at 7:04 PM, Demian Katz wrote:





Does adding the "--verbose" or "--debug" switch give you any additional
information?

- Demian




-----Original Message-----

From: Voronetskyy Yevgen [mailto:voronetskyy< at >gmail.com]

Sent: Tuesday, January 10, 2012 11:54 AM

To: user< at >phpunit.de

Subject: [phpunit-user] PhpUnit on Windows

 

Hi,

 

I'm novice in PHP.

I've installed the PHPUnit with Pear.

When I run the following command from CLI : phpunit --help , I see the

correct help message from PHPUnit.

 

But when I give the argument which is a TestCase file or a folder with

tests, there is nothing. Any errors. Nothing.

 

Could you help me to figure out what is wrong with my PhpUnit?

 

Thanks in advance,

Yevgen

Re: PhpUnit on Windows

Voronetskyy Yevgen — 2012-01-10T17:14:14

No, the output is empty.


On Jan 10, 2012, at 7:04 PM, Demian Katz wrote:

RE: PhpUnit on Windows

Demian Katz — 2012-01-10T17:04:20

Does adding the "--verbose" or "--debug" switch give you any additional information?

- Demian

PhpUnit on Windows

Voronetskyy Yevgen — 2012-01-10T16:54:05

Hi,

I'm novice in PHP.
I've installed the PHPUnit with Pear.
When I run the following command from CLI : phpunit --help , I see the correct help message from PHPUnit.

But when I give the argument which is a TestCase file or a folder with tests, there is nothing. Any errors. Nothing.

Could you help me to figure out what is wrong with my PhpUnit?

Thanks in advance,
Yevgen

RE: "Aborted" when requesting coverage

Demian Katz — 2012-01-10T14:36:04

Thanks for the suggestion; unfortunately, it doesn't seem to have helped.

There are no die() or exit() calls in the code I am requesting coverage reporting for.  There are a few such calls in library code outside of the area where I am requesting coverage, but commenting out these calls makes no apparent difference.  I also tried switching the "addUncoveredFilesFromWhitelist" setting to false in case some unwanted logic was being pulled in from somewhere else, but it didn't solve the problem.

I did make two other discoveries which may be significant:


1.)    The "Aborted" message does not seem to be sent to either stdout or stderr!  If I run "phpunit --coverage-text=/tmp/junk.txt > stdout.out 2> stderr.out", neither of the *.out files gets populated, and the word "Aborted" still appears on screen!

2.)    The error seems to be related to the number of files being covered, but not to a specific file.  I tried drastically scaling down the size of my coverage whitelist.  If I request coverage of a single file, everything works correctly.  If I request two files, I get the "Aborted" error.  I was careful about which files I tested - i.e. I can get coverage of either Options.php or Params.php alone, but I CANNOT get coverage of both Options.php and Params.php at the same time.  There is no reason that these two files should conflict with one another, as they are used together in normal operation.

Very mysterious - any other ideas greatly appreciated!  Also, if anyone is interested in trying to reproduce this problem on their own systems, my code and tests are in a public SVN repository, and I'd be happy to provide instructions on setting up an appropriate environment.

thanks,
Demian

From: Erick Dovale [mailto:edovale< at >gmail.com]
Sent: Monday, January 09, 2012 4:13 PM
To: user< at >phpunit.de
Subject: Re: [phpunit-user] "Aborted" when requesting coverage

Look for calls to die() in the code been covered.
On Mon, Jan 9, 2012 at 3:46 PM, Demian Katz <demian.katz< at >villanova.edu<mailto:demian.katz< at >villanova.edu>> wrote:
This problem is still driving me a bit crazy.  I've made a small amount of progress:


1.)    I've found another report of the same (or at least a very similar) problem: http://stackoverflow.com/questions/3065563/phpunit-reporting-aborted-no-matter-what-tests-are-run (unfortunately, there is no satisfactory solution here).

2.)    I realized that part of the reason I was getting so little feedback is that my test suite is output-buffering to allow testing of session-related code, and the "Aborted" message gobbles up the output buffer without displaying any of it.  If I comment out my ob_start() call, I can see the normal PHPUnit messages now...  but that doesn't really tell me anything I didn't already know.  Now, rather than just seeing "Aborted" I see the usual test output, followed by "Generating code coverage report, this may take a moment.Aborted"

3.)    I've tried digging into the PHP_CodeCoverage libraries and putting in debug messages.  As far as I can tell, whatever is triggering the problem is happening in the middle of PHP_CodeCoverage::processUncoveredFilesFromWhitelist()...  but if I comment out the call to that function, the processing still aborts somewhere else - so it's a slippery problem and may not be directly related to the specifics of the code.

4.)    I'm suspicious that it's some sort of resource-related problem, but my memory limit is set to -1 and execution timeouts shouldn't apply in CLI mode.  I'm not sure what else I can do.

Any advice on further troubleshooting?  Any idea where the "Aborted" is even coming from?  I've searched the source of PHPUnit, PHP_CodeCoverage, PHP itself AND the xdebug module, and NONE of these use the word "Aborted" anywhere...  must be something really low level, but I'm not sure how to pin it down.

thanks,
Demian

From: Demian Katz
Sent: Wednesday, December 21, 2011 3:17 PM
To: user< at >phpunit.de<mailto:user< at >phpunit.de>
Subject: RE: [phpunit-user] "Aborted" when requesting coverage

Yes, I do have XDebug installed (version 2.1.0 on Ubuntu, version 2.1.2 on RedHat).  I have successfully generated code coverage reports in the past on the RedHat box, though the last time I managed to do it, I was running earlier versions of everything (I recently upgraded from PHP 5.2.11, which also required updates to PHPUnit and XDebug).

- Demian

From: Jeremy Cook [mailto:jeremycook0< at >gmail.com<mailto:jeremycook0< at >gmail.com>]
Sent: Wednesday, December 21, 2011 3:12 PM
To: user< at >phpunit.de<mailto:user< at >phpunit.de>
Subject: RE: [phpunit-user] "Aborted" when requesting coverage

Do you have the XDebug extension installed? PHPUnit requires that to generate code coverage reports.

Regards,

Jeremy.

From: Demian Katz [mailto:demian.katz< at >villanova.edu<mailto:demian.katz< at >villanova.edu>]
Sent: December-21-11 3:10 PM
To: user< at >phpunit.de<mailto:user< at >phpunit.de>
Subject: [phpunit-user] "Aborted" when requesting coverage

First of all, I'm a new list member, and I couldn't find a searchable archive, so apologies if I'm asking a duplicate question.  Feel free to point me in the right direction if I'm missing something obvious.

My problem is that PHPUnit is refusing to export coverage reports for me.  When I run my tests with no coverage parameters, they work fine.  When I try --coverage-clover or --coverage-html parameters, PHPUnit dies with the simple message:

Aborted

Turning on verbose mode with the -v switch makes no difference.  All I get is the word "Aborted," which is not very helpful for troubleshooting!

I'm experiencing this problem on two different servers:

Server 1: Ubuntu, PHP 5.3.2, PHPUnit 3.5.15
Server 2: RedHat, PHP 5.3.8, PHPUnit 3.6.5

Any idea what's going wrong or how I could start narrowing down the cause?

thanks,
Demian

Re: "Aborted" when requesting coverage

Erick Dovale — 2012-01-09T21:12:52

Look for calls to die() in the code been covered.

On Mon, Jan 9, 2012 at 3:46 PM, Demian Katz <demian.katz< at >villanova.edu>wrote:

RE: "Aborted" when requesting coverage

Demian Katz — 2012-01-09T20:46:55

This problem is still driving me a bit crazy.  I've made a small amount of progress:


1.)    I've found another report of the same (or at least a very similar) problem: http://stackoverflow.com/questions/3065563/phpunit-reporting-aborted-no-matter-what-tests-are-run (unfortunately, there is no satisfactory solution here).

2.)    I realized that part of the reason I was getting so little feedback is that my test suite is output-buffering to allow testing of session-related code, and the "Aborted" message gobbles up the output buffer without displaying any of it.  If I comment out my ob_start() call, I can see the normal PHPUnit messages now...  but that doesn't really tell me anything I didn't already know.  Now, rather than just seeing "Aborted" I see the usual test output, followed by "Generating code coverage report, this may take a moment.Aborted"

3.)    I've tried digging into the PHP_CodeCoverage libraries and putting in debug messages.  As far as I can tell, whatever is triggering the problem is happening in the middle of PHP_CodeCoverage::processUncoveredFilesFromWhitelist()...  but if I comment out the call to that function, the processing still aborts somewhere else - so it's a slippery problem and may not be directly related to the specifics of the code.

4.)    I'm suspicious that it's some sort of resource-related problem, but my memory limit is set to -1 and execution timeouts shouldn't apply in CLI mode.  I'm not sure what else I can do.

Any advice on further troubleshooting?  Any idea where the "Aborted" is even coming from?  I've searched the source of PHPUnit, PHP_CodeCoverage, PHP itself AND the xdebug module, and NONE of these use the word "Aborted" anywhere...  must be something really low level, but I'm not sure how to pin it down.

thanks,
Demian

From: Demian Katz
Sent: Wednesday, December 21, 2011 3:17 PM
To: user< at >phpunit.de
Subject: RE: [phpunit-user] "Aborted" when requesting coverage

Yes, I do have XDebug installed (version 2.1.0 on Ubuntu, version 2.1.2 on RedHat).  I have successfully generated code coverage reports in the past on the RedHat box, though the last time I managed to do it, I was running earlier versions of everything (I recently upgraded from PHP 5.2.11, which also required updates to PHPUnit and XDebug).

- Demian

From: Jeremy Cook [mailto:jeremycook0< at >gmail.com]
Sent: Wednesday, December 21, 2011 3:12 PM
To: user< at >phpunit.de
Subject: RE: [phpunit-user] "Aborted" when requesting coverage

Do you have the XDebug extension installed? PHPUnit requires that to generate code coverage reports.

Regards,

Jeremy.

From: Demian Katz [mailto:demian.katz< at >villanova.edu]
Sent: December-21-11 3:10 PM
To: user< at >phpunit.de
Subject: [phpunit-user] "Aborted" when requesting coverage

First of all, I'm a new list member, and I couldn't find a searchable archive, so apologies if I'm asking a duplicate question.  Feel free to point me in the right direction if I'm missing something obvious.

My problem is that PHPUnit is refusing to export coverage reports for me.  When I run my tests with no coverage parameters, they work fine.  When I try --coverage-clover or --coverage-html parameters, PHPUnit dies with the simple message:

Aborted

Turning on verbose mode with the -v switch makes no difference.  All I get is the word "Aborted," which is not very helpful for troubleshooting!

I'm experiencing this problem on two different servers:

Server 1: Ubuntu, PHP 5.3.2, PHPUnit 3.5.15
Server 2: RedHat, PHP 5.3.8, PHPUnit 3.6.5

Any idea what's going wrong or how I could start narrowing down the cause?

thanks,
Demian

phpUnit with eclipse and PTI

Motyka, Axel — 2012-01-06T09:01:09

Hi there,

i hope i can find some help here!

Iam trying to use phpunit with the PHP Tools Integration(PTI) - i know this is not a PTI mailing list. But maybe someone can help me.

I installed the PTI package - everytime i try to execute phpunit (or any other PHP Tool like copy paste detector) i get :
Fatal error: Class 'ezcConsoleInput' not found in C:\IDE\eclipse\plugins\org.phpsrc.eclipse.pti.library.pear_1.2.2.R20111119000000\php\library\PEAR\PHPCPD\TextUI\Command.php on line 62

Seems to be a mistake in my configuration!

I am using Windows 7 with eclipse Indigo Service Release 1.

Thanks for your help!

Re: "Aborted" when requesting coverage

Erick Dovale — 2012-01-09T21:12:52

Look for calls to die() in the code been covered.

On Mon, Jan 9, 2012 at 3:46 PM, Demian Katz <demian.katz< at >villanova.edu>wrote:

RE: "Aborted" when requesting coverage

Demian Katz — 2012-01-09T20:46:55

This problem is still driving me a bit crazy.  I've made a small amount of progress:


1.)    I've found another report of the same (or at least a very similar) problem: http://stackoverflow.com/questions/3065563/phpunit-reporting-aborted-no-matter-what-tests-are-run (unfortunately, there is no satisfactory solution here).

2.)    I realized that part of the reason I was getting so little feedback is that my test suite is output-buffering to allow testing of session-related code, and the "Aborted" message gobbles up the output buffer without displaying any of it.  If I comment out my ob_start() call, I can see the normal PHPUnit messages now...  but that doesn't really tell me anything I didn't already know.  Now, rather than just seeing "Aborted" I see the usual test output, followed by "Generating code coverage report, this may take a moment.Aborted"

3.)    I've tried digging into the PHP_CodeCoverage libraries and putting in debug messages.  As far as I can tell, whatever is triggering the problem is happening in the middle of PHP_CodeCoverage::processUncoveredFilesFromWhitelist()...  but if I comment out the call to that function, the processing still aborts somewhere else - so it's a slippery problem and may not be directly related to the specifics of the code.

4.)    I'm suspicious that it's some sort of resource-related problem, but my memory limit is set to -1 and execution timeouts shouldn't apply in CLI mode.  I'm not sure what else I can do.

Any advice on further troubleshooting?  Any idea where the "Aborted" is even coming from?  I've searched the source of PHPUnit, PHP_CodeCoverage, PHP itself AND the xdebug module, and NONE of these use the word "Aborted" anywhere...  must be something really low level, but I'm not sure how to pin it down.

thanks,
Demian

From: Demian Katz
Sent: Wednesday, December 21, 2011 3:17 PM
To: user< at >phpunit.de
Subject: RE: [phpunit-user] "Aborted" when requesting coverage

Yes, I do have XDebug installed (version 2.1.0 on Ubuntu, version 2.1.2 on RedHat).  I have successfully generated code coverage reports in the past on the RedHat box, though the last time I managed to do it, I was running earlier versions of everything (I recently upgraded from PHP 5.2.11, which also required updates to PHPUnit and XDebug).

- Demian

From: Jeremy Cook [mailto:jeremycook0< at >gmail.com]
Sent: Wednesday, December 21, 2011 3:12 PM
To: user< at >phpunit.de
Subject: RE: [phpunit-user] "Aborted" when requesting coverage

Do you have the XDebug extension installed? PHPUnit requires that to generate code coverage reports.

Regards,

Jeremy.

From: Demian Katz [mailto:demian.katz< at >villanova.edu]
Sent: December-21-11 3:10 PM
To: user< at >phpunit.de
Subject: [phpunit-user] "Aborted" when requesting coverage

First of all, I'm a new list member, and I couldn't find a searchable archive, so apologies if I'm asking a duplicate question.  Feel free to point me in the right direction if I'm missing something obvious.

My problem is that PHPUnit is refusing to export coverage reports for me.  When I run my tests with no coverage parameters, they work fine.  When I try --coverage-clover or --coverage-html parameters, PHPUnit dies with the simple message:

Aborted

Turning on verbose mode with the -v switch makes no difference.  All I get is the word "Aborted," which is not very helpful for troubleshooting!

I'm experiencing this problem on two different servers:

Server 1: Ubuntu, PHP 5.3.2, PHPUnit 3.5.15
Server 2: RedHat, PHP 5.3.8, PHPUnit 3.6.5

Any idea what's going wrong or how I could start narrowing down the cause?

thanks,
Demian

phpUnit with eclipse and PTI

Motyka, Axel — 2012-01-06T09:01:09

Hi there,

i hope i can find some help here!

Iam trying to use phpunit with the PHP Tools Integration(PTI) - i know this is not a PTI mailing list. But maybe someone can help me.

I installed the PTI package - everytime i try to execute phpunit (or any other PHP Tool like copy paste detector) i get :
Fatal error: Class 'ezcConsoleInput' not found in C:\IDE\eclipse\plugins\org.phpsrc.eclipse.pti.library.pear_1.2.2.R20111119000000\php\library\PEAR\PHPCPD\TextUI\Command.php on line 62

Seems to be a mistake in my configuration!

I am using Windows 7 with eclipse Indigo Service Release 1.

Thanks for your help!