Recent changes to bugs

PHPUnit_Util_Printer::write writes HTTP headers before unit tests run

Daniel Barrett — Tue, 19 Nov 2013 18:15:13 -0000

When I call header() inside a unit test, I am told that phpunit has already set HTTP headers:

Cannot modify header information - headers already sent by (output started at /usr/share/pear/PHPUnit/Util/Printer.php:172)

Full report is at: http://stackoverflow.com/questions/20076467/why-does-phpunit-interfere-with-setting-http-headers-in-this-code

This is phpunit 3.7.19 on CentOS 6.

runtimeexception phpunit does not like "die()"

Hayden Virtue — Tue, 27 Dec 2011 06:35:28 -0000

my unit tests use the database layer, which is bad however please read on...

when using functionality that is NYI I put "die()" in there to make it die horribly,

The die causes strange runtimeexpcetion with no error msg to tests that do not invoke the die(), and it's hard to pinpoint the cause.

phpunit CLI

Anonymous — Wed, 01 Jun 2005 00:19:14 -0000

PHP Unit does not work for Command Line based PHP scrtips.

class Exception is a predefined one in php 5.0.2

Anton Kovalenko — Wed, 15 Sep 2004 14:12:45 -0000

Hello, I was trying to use your phpUnit with php 5.0.2
and met a name
resolution conflict. Exception class is predefined in
php 5.0.0, as you know. So, I've managed to fix the
problem.
Here's the patch that works fine in my case --
runtests2.php runs completely as it should.

Index: phpunit.php

RCS file: /cvsroot/phpunit/phpunit/phpunit.php,v
retrieving revision 1.20
diff -u -r1.20 phpunit.php
--- phpunit.php 31 Jul 2004 07:35:03 -0000 1.20
+++ phpunit.php 14 Sep 2004 09:36:38 -0000
@@ -53,11 +53,11 @@
}
}

-class Exception {
+class phpUnitException {
/* Emulate a Java exception, sort of... */
var $message;
var $type;
- function Exception($message, $type = 'FAILURE') {
+ function phpUnitException($message, $type = 'FAILURE') {
$this->message = $message;
$this->type = $type;
}
@@ -260,13 +260,13 @@
//printf("TestCase::fail(%s) \n", ($message) ?
$message : '');
/* JUnit throws AssertionFailedError here. We
just record the
failure and carry on */
- $this->fExceptions[] = new Exception($message,
'FAILURE');
+ $this->fExceptions[] = new
phpUnitException($message, 'FAILURE');
}

function error($message) {
/* report error that requires correction in the
test script
itself, or (heaven forbid) in this testing
infrastructure */
- $this->fExceptions[] = new Exception($message,
'ERROR');
+ $this->fExceptions[] = new
phpUnitException($message, 'ERROR');
$this->fResult->stop(); // [does not work]
}

--
With best regards, Anton Kovalenko.

set_error_handler complains with NULL arugment

Ralfoide — Fri, 27 Feb 2004 08:34:22 -0000

I used to get this error message in phpunit's HTML output:

PHP ERROR: set_error_handler() expects argument 1, '', to be a valid callback in phpunit.php at line 241

The problem originates from $old_handler being NULL and PHP 4.3.3 complains when set_error_handler is used with a NULL argument 1, so I fix it by changing this line:

[241] set_error_handler($old_handler); // revert to prior error handler

by this:

if ($old_handler != NULL)
set_error_handler($old_handler); // revert to prior error handler
else
restore_error_handler();

SHUTTING DOWN crash

Anonymous — Thu, 26 Feb 2004 11:23:33 -0000

I had a bug where runtests worked without any tests,
but with one trivial test something would crash, output
a lot of high-bit text, then the text: "SHUTTING DOWN".

Not sure what it is crashing - PHP or Apache - but by
removing all flush() calls in PHPunit it no longer
occurred.

Version information follows:

PHPunit:
// $Id: phpunit.php,v 1.11 2002/10/31 18:44:12 fredy Exp $

Apache: 2.0.47

PHP 4.3.4 (cgi) (built: Feb 11 2004 10:18:49)
Copyright (c) 1997-2003 The PHP Group
Zend Engine v1.3.0, Copyright (c) 1998-2003 Zend
Technologies
with Zend Extension Manager v1.0.1, Copyright (c)
2003, by Zend Technologies
with Zend Optimizer v2.1.1, Copyright (c)
1998-2003, by Zend Technologies
with DISABLED Zend Performance Suite v3.6.0,
Copyright (c) 1999-2003, by The Accelerator presently
supports only Apache, ISAPI and FastCGI SAPIs

Operator '@' not supported

Anonymous — Mon, 14 Jul 2003 22:15:37 -0000

PHPunit throws an error when I try to access an unset
element of an array, even if I use '@' in front of the
code to suppress errors.

PHP implements '@' by temporarily setting error_reporting
() to equal E_NONE, so the fix is simply to add a check
whether error_reporting() is on in the function
PHPUnit_error_handler().

This is the fixed function, adapted from 1.11:

function PHPUnit_error_handler($errno, $errstr, $errfile,
$errline) {
global $PHPUnit_testRunning;
if(error_reporting()){
$PHPUnit_testRunning[0]->fail("PHP ERROR: ".
$errstr." in ".$errfile." at line ".$errline);
}
}

My email: tom, at, meansandends, dot, com.

More Detailed Error Message

Anonymous — Thu, 01 May 2003 15:05:14 -0000

on line 149/150:

If you change:
$htmlValue = "<code class=\&quot;$class\&quot;>"
. htmlspecialchars($translateValue)
. "</code>";

to:
$htmlValue = "<code class=\&quot;$class\&quot;>"
. strtoupper($class) . ": "
. htmlspecialchars($translateValue)
. "</code>";

it will print out EXPECTED: and ACTUAL: before the
erroneous values. It makes it more readable.

Segmentation faults from runtests.php

Last Obelus — Thu, 27 Mar 2003 21:19:31 -0000

Apache/1.3.26 (Unix) Debian GNU/Linux PHP/4.1.2

runtests.php & runtests2.php cause segmentation faults on the above system (but, oddly, not all the time -- on about 2/3 of requests.

Segmentation faults also occurs when I tested a test suite containing a single test with $this->assert (true, "test")

error when restoring error_handler

Fred Yankowski — Sat, 28 Dec 2002 18:49:55 -0000

Per note from Ian Smith <iansmithca@yahoo.com>:

I think that in phpunit.php on line 241 you should use

restore_error_handler();

instead of trying to reset the value with
set_error_handler($old_handler);

At least on my box (win xp, apache2, php4.3RC4) this
produces an error because old_handler is ''. I changed
my copy to use the restore...() above and it works ok.