You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
PHPUnit suffer from its legacy architecture, because we have to wait final tests count, before starting at least first of them.
In my case, I've one hundred of *Test.php files that produced about 4800 unit tests (using data provider).
When I run full tests suite, I've to wait a long time before to see any dot in stdout (default printer results), time while PHPUnit count all tests, then after results come quickly.
My suggestion will be to implement a generator solution that will proceed to each *Test.php file ASAP !
Hope my explains are enough.
The text was updated successfully, but these errors were encountered:
llaville
added a commit
to llaville/php-compatinfo-db
that referenced
this issue
Oct 21, 2015
Just to let you know that I've implemented in Phing PHPUnitTask an alternative solution based on PHP 5.5 generator feature. It will be proposed next week. See http://www.phing.info/trac/ticket/1222
PHPUnit suffer from its legacy architecture, because we have to wait final tests count, before starting at least first of them.
In my case, I've one hundred of *Test.php files that produced about 4800 unit tests (using data provider).
When I run full tests suite, I've to wait a long time before to see any dot in stdout (default printer results), time while PHPUnit count all tests, then after results come quickly.
My suggestion will be to implement a generator solution that will proceed to each *Test.php file ASAP !
Hope my explains are enough.
The text was updated successfully, but these errors were encountered: