Debug mode and continuing on crash about paratest HOT 6 CLOSED

I think "--functional" is what you expect for (2).
It will "Run methods instead of suites in separate processes." so it's probably like process-isolation except for dataproviders.

from paratest.

@julianseeger Thanks for the reply. I thought about that and tried. But with and without -f, I get the following for a framework like assetic. Basically I crash at the 244th test or so.

hhvm ../../vendor/bin/paratest --functional

Running phpunit in 5 processes with /data/users/joelm/fbcode/hphp/test/frameworks/vendor/bin/phpunit. Functional mode is on

Configuration read from /data/users/joelm/fbcode/hphp/test/frameworks/frameworks/assetic/phpunit.xml.dist

...............................................................  63 / 269 ( 23%)
...............................F.......................E....... 126 / 269 ( 46%)
.............................................................EE 189 / 269 ( 70%)
E.EEEEEEEEEEEEEEEEEEEEEEEE.EEE.......


  [InvalidArgumentException]
  Log file /tmp/PT_Xii2HZ is empty. This means a PHPUnit process has crashed.



paratest [-p|--processes="..."] [-f|--functional] [--no-test-tokens] [-h|--help] [--phpunit="..."] [--runner="..."] [--bootstrap="..."] [-c|--configuration="..."] [-g|--group="..."] [--log-junit="..."] [--colors] [--path="..."] [path]

from paratest.

Hey guys. My time to support paratest has definitely been limited, so I apologize for explanation rather than solution at the moment.

Just to clarify on some of the phpunit configurations, paratest is pretty limited in what it can support at the moment. Some things just don't delegate to PHPUnit as nicely as we might hope.

The functional switch [-f|--functional] switch works best for methods that have no external dependencies; it was originally designed to speed up selenium tests.

from paratest.

Hi guys in Laravel 5.4 I installed paratest with composer but it crashes when I run my tests. Crash Log below

Log file C:\Users\SomUserName\AppData\Local\Temp\PT_9E76.tmp is empty. This means a PHPUnit process has crashed.
The process: C:\xampp\htdocs\project\project_project\some_project\vendor\bin\phpunit.bat --configuration C:\xampp\htdocs\project\project_project\some_project\phpunit.xml --log-junit C:\Users
SomUserName\AppData\Local\Temp\PT_9E76.tmp Tests\Feature\ExampleTest C:\xampp\htdocs\project\project_project\some_project\tests\Feature\ExampleTest.php
This means a PHPUnit process was unable to run "C:\xampp\htdocs\project\project_project\some_project\tests\Feature\ExampleTest.php"

from paratest.

@JoelMarcey

For

*** 1. Is there a way to run phpunit in --debug mode with paratest, so that I can see the name of each individual test running as paratest is executing? I tried:

I added a --verbose=1 option in #361 that will now output the underyling phpunit command.

from paratest.

This issue has gone two months without activity. In another two weeks, I will close it.

But! If you comment or otherwise update it, I will reset the clock, and if you label it Backlog or In Progress, I will leave it alone ... forever!

from paratest.