I've got this problem too. But i'm using sfPhpunitPlugin.
I solved this problem by running tests is isolated php processes with
PHPUnit 3.4
Also, read this thread:
http://groups.google.com/group/symfony-devs/browse_thread/thread/db7833df51238ba7
My fork of sfPhpunitPlugin:
http://github.com/ma
Nice to see someone, who uses the sfPhpunitPlugin :)
I'll take the isolate option over to the upcoming release, which has
much more functional testing support, than the 1.0.4 version.
Frank
Am 10.09.2009 um 08:56 schrieb Максим Олейник:
>
> I've got this problem too. But i'm using sfPhpunitP
Be careful with isolation. It requires PHPUnit 3.4 and I've patch it
to use with symfony.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"symfony users" group.
To post to this group, send email to symfony-users@googl
I did not want to switch to PHPUnit. So I made my own ugly solution
with Symfonys Lime:
passed + $this->failed + $this->skipped;
$this->output->echoln("process: $this->passed $this->failed
$this-
>skipped" );
flush();
}
public static function run(
