我们刚开始对我们的CI申请进行单元测试;我们编写的第一个测试运行完毕,但PHPUnit总是在最后抛出错误信息:
user@server:~/public$ phpunit -c app/ --strict src/Acme/Bundle/SomeBundle/Tests/Controller/SomeControllerTest.php
PHPUnit 3.6.11 by Sebastian Bergmann.
Configuration read from /var/www/user/htdocs/public/app/phpunit.xml.dist
..
Time: 5 seconds, Memory: 130.00Mb
OO (2 tests, 2 assertions)
PHP Fatal error: Exception thrown without a stack frame in Unknown on line 0
PHP Stack trace:
PHP 1. {main}() /usr/bin/phpunit:0
PHP 2. PHPUnit_TextUI_Command::main() /usr/bin/phpunit:46
PHP 3. PHPUnit_TextUI_Command->run() /usr/share/php/PHPUnit/TextUI/Command.php:133
Fatal error: Exception thrown without a stack frame in Unknown on line 0
Call Stack:
0.0001 629992 1. {main}() /usr/bin/phpunit:0
0.0023 1235832 2. PHPUnit_TextUI_Command::main() /usr/bin/phpunit:46
0.0023 1236848 3. PHPUnit_TextUI_Command->run() /usr/share/php/PHPUnit/TextUI/Command.php:133
到目前为止唯一的提示是,只有当一个(或多个)测试使用[见下文]在页面上发出请求时才会出现,因此它可能在某种程度上与会话相关。
$client = static::createClient();
$container = $client->getContainer();
$uri = $container->getParameter('url_frontend') . '/';
$client->request('GET', $uri);
以下是我们phpunit.xml.dist
的链接更新:
我设法获得有关错误本身的更多信息:
1) Acme\Bundle\SomeBundle\Tests\Controller\SomeControllerTest::testIndexResponseStatusCode
RuntimeException: PHP Fatal error: Uncaught exception 'ErrorException' with message 'Warning: Unknown: Failed to write session data (user). Please verify that the current setting of session.save_path is correct (/tmp/sessions) in Unknown line 0' in /var/www/user/htdocs/public/vendor/symfony/src/Symfony/Component/HttpKernel/Debug/ErrorHandler.php:67
Stack trace:
#0 [internal function]: Symfony\Component\HttpKernel\Debug\ErrorHandler->handle(2, 'Unknown: Failed...', 'Unknown', 0, Array)
#1 {main}
thrown in /var/www/user/htdocs/public/vendor/symfony/src/Symfony/Component/HttpKernel/Debug/ErrorHandler.php on line 67
答案 0 :(得分:0)
我只是猜测,但我认为异常被抛出,因为phpunit尝试第二次运行(异常是在run()方法的开头抛出)。
在 phpunit.xml.dist 中尝试替换:
<testsuites>
<testsuite name="Project Test Suite">
<directory>../src/*/*Bundle/Tests</directory>
<directory>../src/*/Bundle/*Bundle/Tests</directory>
</testsuite>
</testsuites>
with:
<testsuites>
<testsuite name="Project Test Suite">
<directory>../src/*/*Bundle/Tests</directory>
</testsuite>
</testsuites>
我认为第一条规则匹配两条路径。
答案 1 :(得分:0)
我们的一位开发人员(经过多次咒骂和诅咒)解决了问题,但是错误是FOS\FacebookBundle\Facebook\FacebookSessionPersistence
确切地说构造函数启动了自己的会话:
public function __construct($config, Session $session, $prefix = self::PREFIX)
{
$this->session = $session;
$this->prefix = $prefix;
$this->session->start(); // he starts a session
parent::__construct($config);
}
所以我们刚刚编写了自己的FacebookSessionPersistence类:
namespace Acme\Bundle\UserBundle\Facebook;
use FOS\FacebookBundle\Facebook\FacebookSessionPersistence as BaseFacebookSessionPersistence;
use Symfony\Component\HttpFoundation\Session;
/**
* Quick (and dirty) fix for running tests using FosFacebookBundle.
* only use this class, while testing the application with phpunit
*
* @see https://github.com/FriendsOfSymfony/FOSFacebookBundle/issues/79
*/
class FacebookSessionPersistence extends BaseFacebookSessionPersistence
{
public function __construct($config, Session $session, $prefix = self::PREFIX)
{
$this->session = $session;
$this->prefix = $prefix;
// don't start session or call parent constructor
//$this->session->start();
//parent::__construct($config);
}
}
并将其添加到测试配置中:
# quick workaround as the fb class fails the test as it calls session->start in the construct
# @see https://github.com/FriendsOfSymfony/FOSFacebookBundle/issues/79
fos_facebook:
class:
api: Acme\Bundle\UserBundle\Facebook\FacebookSessionPersistence
希望这将有助于后代......