blocks|key|2898037|text|问题是PHPUnit会在屏幕上打印一个标题，此时你不能添加更多的标题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2898038|解决办法是在一个独立的进程中运行测试。下面是一个例子|2898039|<?php

class+FooTest+extends+PHPUnit_Framework_TestCase
{
++++/**
+++++*+@runInSeparateProcess
+++++*/
++++public+function+testBar()
++++{
++++++++header('Location+:+http://foo.com');
++++}
}|code-block|syntax|javascript|2898040|这将导致：|2898041|$+phpunit+FooTest.php
PHPUnit+3.6.10+by+Sebastian+Bergmann.

.

Time:+1+second,+Memory:+9.00Mb

OK+(1+test,+0+assertions)|2898042|关键是@runInSeparateProcess注释。|2898043|如果您使用的是PHPUnit+~4.1或更高版本，并收到以下错误：|2898044|PHP+Fatal+error:++Uncaught+Error:+Class+'PHPUnit_Util_Configuration'+not+found+in+-:378
Stack+trace:
#0+{main}
++thrown+in+-+on+line+378

Fatal+error:+Uncaught+Error:+Class+'PHPUnit_Util_Configuration'+not+found+in+-+on+line+378

Error:+Class+'PHPUnit_Util_Configuration'+not+found+in+-+on+line+378

Call+Stack:
++++0.0013+++++582512+++1.+{main}()+-:0|2898045|尝试将以下内容添加到您的引导程序文件中以修复它：|2898046|<?php
if+(!defined('PHPUNIT_COMPOSER_INSTALL'))+{
++++define('PHPUNIT_COMPOSER_INSTALL',+__DIR__+.+'/path/to/composer/vendors/dir/autoload.php');
}|2898047|entityMap^0|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Y|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Z|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|10|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|11|8|@]|9|@]|A|$]]|$1|K|3|L|5|F|7|12|8|@]|9|@]|A|$G|H]]|$1|M|3|N|5|6|7|13|8|@]|9|@]|A|$]]|$1|O|3|P|5|6|7|14|8|@]|9|@]|A|$]]|$1|Q|3|R|5|F|7|15|8|@]|9|@]|A|$G|H]]|$1|S|3|T|5|6|7|16|8|@]|9|@]|A|$]]|$1|U|3|V|5|F|7|17|8|@]|9|@]|A|$G|H]]|$1|W|3|-4|5|6|7|18|8|@]|9|@]|A|$]]]|X|$]]

The issue is that PHPUnit will print a header to the screen and at that point you can't add more headers.

The work around is to run the test in an isolated process. Here is an example

<pre><code>&lt;?php

class FooTest extends PHPUnit_Framework_TestCase
{
 /**
 * @runInSeparateProcess
 */
 public function testBar()
 {
 header('Location : http://foo.com');
 }
}
</code></pre>

This will result in:

<pre><code>$ phpunit FooTest.php
PHPUnit 3.6.10 by Sebastian Bergmann.

.

Time: 1 second, Memory: 9.00Mb

OK (1 test, 0 assertions)
</code></pre>

The key is the @runInSeparateProcess annotation. 

If you are using PHPUnit ~4.1 or something and get the error:

<pre><code>PHP Fatal error: Uncaught Error: Class 'PHPUnit_Util_Configuration' not found in -:378
Stack trace:
#0 {main}
 thrown in - on line 378

Fatal error: Uncaught Error: Class 'PHPUnit_Util_Configuration' not found in - on line 378

Error: Class 'PHPUnit_Util_Configuration' not found in - on line 378

Call Stack:
 0.0013 582512 1. {main}() -:0
</code></pre>

Try add this to your bootstrap file to fix it:

<pre><code>&lt;?php
if (!defined('PHPUNIT_COMPOSER_INSTALL')) {
 define('PHPUNIT_COMPOSER_INSTALL', __DIR__ . '/path/to/composer/vendors/dir/autoload.php');
}
</code></pre>

blocks|key|2898103|text|尽管在单独的进程中运行测试确实解决了这个问题，但在运行大型测试套件时会产生明显的开销。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2898104|我的解决方法是将phpunit的输出定向到stderr，如下所示：|2898105|phpunit+--stderr+<options>|code-block|syntax|javascript|2898106|这应该会解决这个问题，而且这也意味着您不必创建包装器函数并替换代码中出现的所有内容。|2898107|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|N|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|O|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|P|8|@]|9|@]|A|$]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

Although running the test in a separate process does fix the problem, there's a noticeable overhead when running a large suite of tests.

My fix was to direct phpunit's output to stderr, like so:

<pre><code>phpunit --stderr &lt;options&gt;
</code></pre>

That should fix the problem, and it also means that you don't have to create a wrapper function and replace all occurrences in your code.

blocks|key|232103|text|我有一个更激进的解决方案，为了在我的tested/included文件中使用$_SESSION。我在../PHPUnit/Utils/Printer.php上编辑了一个PHPUnit文件，使其在命令"print+$buffer"之前拥有一个"session_start();"。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|CODE|entityRanges|data|232104|它对我来说就像一个护身符。但我认为"joonty“用户的解决方案是到目前为止最好的。|232105|entityMap^0|I|F|1E|S|2C|7|2P|H|12|9|3C|I|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@$9|L|A|M|B|C]|$9|N|A|O|B|C]|$9|P|A|Q|B|C]|$9|R|A|S|B|C]|$9|T|A|U|B|D]|$9|V|A|W|B|D]]|E|@]|F|$]]|$1|G|3|H|5|6|7|X|8|@]|E|@]|F|$]]|$1|I|3|-4|5|6|7|Y|8|@]|E|@]|F|$]]]|J|$]]

I had a more radical solution, in order to use <code>$_SESSION</code> inside my tested/included files.
I edited one of the PHPUnit files at ../PHPUnit/Utils/Printer.php to have a <code>"session_start();"</code> before the command "print $buffer". 

It worked for me like a charm. But I think "joonty" user's solution is the best of all up to now.

blocks|key|237599|text|@runInSeparateProcess的另一个解决方案是在运行PHPUnit时指定--process-isolation选项：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|237600|name@host+[~/test]#+phpunit+--process-isolation+HeadersTest.php|code-block|syntax|javascript|237601|这类似于在phpunit.xml中设置processIsolation="true“选项。|237602|此解决方案与指定--stderr选项具有类似的优缺点，但在我的示例中不起作用。基本上不需要更改代码，即使在单独的PHP进程中运行每个测试可能会影响性能。|237603|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|N|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|O|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|P|8|@]|9|@]|A|$]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

An alternative solution to @runInSeparateProcess is to specify the --process-isolation option when running PHPUnit:

<pre><code>name@host [~/test]# phpunit --process-isolation HeadersTest.php
</code></pre>

That is analogous to set the processIsolation="true" option in phpunit.xml.

This solution has similar advantages/disadvantages to specifying the --stderr option, which however did not work in my case. Basically no code changes are necessary, even though there may be a performance hit due to running each test in a separate PHP process.

blocks|key|2898213|text|顺便说一句:对我来说，headers_list()一直返回0个元素。我注意到了@titel对这个问题的评论，并认为它值得在这里特别提到：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2898214|2898215|只是想在其他人也对此感兴趣的情况下报道这一点。在运行PHPunit+(使用PHP+)时，headers_list()不起作用，但xdebug_get_headers()起作用。|blockquote|2898216|2898217|2898218|HTH|2898219|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/questions/9745080/test-php-headers-with-phpunit#comment12418887_9745080^0|B|E|13|6|0|0|0|18|E|1S|K|0|0|0|0^^$0|@$1|2|3|4|5|6|7|V|8|@$9|W|A|X|B|C]]|D|@$9|Y|A|Z|1|10]]|E|$]]|$1|F|3|-4|5|6|7|11|8|@]|D|@]|E|$]]|$1|G|3|H|5|I|7|12|8|@$9|13|A|14|B|C]|$9|15|A|16|B|C]]|D|@]|E|$]]|$1|J|3|-4|5|6|7|17|8|@]|D|@]|E|$]]|$1|K|3|-4|5|6|7|18|8|@]|D|@]|E|$]]|$1|L|3|M|5|6|7|19|8|@]|D|@]|E|$]]|$1|N|3|-4|5|6|7|1A|8|@]|D|@]|E|$]]]|O|$P|$5|Q|R|S|E|$T|U]]]]

As an aside: For me <code>headers_list()</code> kept returning 0 elements. I noticed <a href="https://stackoverflow.com/questions/9745080/test-php-headers-with-phpunit#comment12418887_9745080">@titel</a>'s comment on the question and figured it deserves special mention here:

<blockquote>
 Just wanted to cover this if there are some other people interested
 in this as well. <code>headers_list()</code> doesn't work while running PHPunit
 (which uses PHP CLI) but <code>xdebug_get_headers()</code> works instead.
</blockquote>

HTH

blocks|key|3112400|text|正如在评论中提到的，我认为在XML配置文件中定义processIsolation是更好的解决方案，如下所示|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3112401|+++++<?xml+version="1.0"+encoding="UTF-8"?>
+++++<phpunit
++++++++processIsolation++++++++++++=+"true"
++++++++//+...+
+++++>
+++++</phpunit>|code-block|syntax|javascript|3112402|这样，您就不必传递--stderr选项，这可能会激怒您的同事。|3112403|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|L|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

As already mentioned in a comment, I think it's a better solution to define processIsolation in the XML config file like 

<pre><code> &lt;?xml version="1.0" encoding="UTF-8"?&gt;
 &lt;phpunit
 processIsolation = "true"
 // ... 
 &gt;
 &lt;/phpunit&gt;
</code></pre>

Like this, you don't have to pass the --stderr option, which might irritate your co-workers.

blocks|key|232162|text|使用--stderr参数在测试后从PHPUnit获取标头。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|232163|phpunit+--stderr|code-block|syntax|javascript|232164|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

Use --stderr parameter for getting headers from PHPUnit after your tests.

<pre><code>phpunit --stderr
</code></pre>

blocks|key|232168|text|如果您正在使用Laravel，并且在路由文件中添加了一些标头|type|unstyled|depth|inlineStyleRanges|entityRanges|data|232169|然后，您需要在测试过程中忽略headers_sent|232170|下面是示例：|232171|if+(!headers_sent())+{
++++header('Access-Control-Allow-Methods:+GET,+POST,+PATCH,+PUT,+DELETE,+OPTIONS');
++++header('Access-Control-Allow-Headers:+Origin,+Access-Control-Allow-Origin,++Content-Type,+X-Authorization,+Authorization,+Accept,charset,boundary,Content-Length');
++++header('Access-Control-Allow-Origin:+*');
}|code-block|syntax|javascript|232172|然后再试一次单元测试，它会通过的。|232173|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|P|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|Q|8|@]|9|@]|A|$]]|$1|F|3|G|5|H|7|R|8|@]|9|@]|A|$I|J]]|$1|K|3|L|5|6|7|S|8|@]|9|@]|A|$]]|$1|M|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|N|$]]

if you're using Laravel and you're adding some headers in route file
then you need to surround with headers_sent to ignore during tests
this is example:
<pre><code>if (!headers_sent()) {
 header('Access-Control-Allow-Methods: GET, POST, PATCH, PUT, DELETE, OPTIONS');
 header('Access-Control-Allow-Headers: Origin, Access-Control-Allow-Origin, Content-Type, X-Authorization, Authorization, Accept,charset,boundary,Content-Length');
 header('Access-Control-Allow-Origin: *');
}
</code></pre>
then try unit test again it will pass..

I'm trying to use PHPunit to test a class that outputs some custom headers.

The problem is that on my machine this:

<pre><code>&lt;?php

class HeadersTest extends PHPUnit_Framework_TestCase {

 public function testHeaders()
 {
 ob_start();

 header('Location: foo');
 $headers_list = headers_list();
 header_remove();

 ob_clean();

 $this-&gt;assertContains('Location: foo', $headers_list);
 }
}
</code></pre>

or even this:

<pre><code>&lt;?php

class HeadersTest extends PHPUnit_Framework_TestCase {

 public function testHeaders()
 {
 ob_start();

 header('Location: foo');
 header_remove();

 ob_clean();
 }
}
</code></pre>

return this error:

<pre><code>name@host [~/test]# phpunit --verbose HeadersTest.php 
PHPUnit 3.6.10 by Sebastian Bergmann.

E

Time: 0 seconds, Memory: 2.25Mb

There was 1 error:

1) HeadersTest::testHeaders
Cannot modify header information - headers already sent by (output started at /usr/local/lib/php/PHPUnit/Util/Printer.php:173)

/test/HeadersTest.php:9

FAILURES!
Tests: 1, Assertions: 0, Errors: 1.
</code></pre>

This looks as if there is something else outputting to the terminal before the test runs even though there is no other file included and there is no other character before the beginning of the PHP tag. Could it be something inside PHPunit that is causing this?

What could the issue be?

Test PHP headers with PHPUnit

单元测试

路由

我正在尝试使用PHPunit来测试一个输出一些自定义标头的类。问题是在我的机器上是这样的：<?phpclass HeadersTest extends PHPUnit_Framework_TestCase { public function testHeaders() { ob_start()...

问使用PHPUnit测试PHP头
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问使用PHPUnit测试PHP头EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问使用PHPUnit测试PHP头
EN