Running feature tests in a separate process in PHP 8.3 fails

[PHLAK]

Laravel Version

10.39.0

PHP Version

8.3.1

Database Driver & Version

No response

Description

Running a feature test with the RunInSeparateProcess attribute (or @runInSeparateProcess annotation) on PHP 8.3 fails immediately.

Steps To Reproduce

Create a feature test that uses the RunInSeparateProcess attribute (or @runInSeparateProcess annotation).

namespace Tests\Feature;

use PHPUnit\Framework\Attributes\RunInSeparateProcess;
use PHPUnit\Framework\Attributes\Test;
use Tests\TestCase;

class ExampleTest extends TestCase
{
    #[Test, RunInSeparateProcess]
    public function it_can_run_in_a_separate_process(): void
    {
        $this->assertTrue(true);
    }
}

Run the test.

$ artisan test tests/Feature/ExampleTest.php

   FAIL  Tests\Feature\ExampleTest
  ⨯ it can run in a separate process                                                                                                     3199.78s  
  ───────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────  
   FAILED  Tests\Feature\ExampleTest > it can run in a separate process                                                     AssertionFailedError   
  Test was run in child process and ended unexpectedly

NOTE: The above does not fail on PHP 8.2 and the following unit test does not fail on PHP 8.3.

namespace Tests\Unit;

use PHPUnit\Framework\Attributes\RunInSeparateProcess;
use PHPUnit\Framework\Attributes\Test;
use PHPUnit\Framework\TestCase;

class ExampleTest extends TestCase
{
    #[Test, RunInSeparateProcess]
    public function it_can_run_in_a_separate_process(): void
    {
        $this->assertTrue(true);
    }
}

[SimplyCorey]

I'm having the same issues when moving my projects over to PHP 8.3.

#49237 seems like a duplicate but I think this should be revisited as it backwards breaking.

[websitevirtuoso]

I have the same problem. Temporary I had to disable flag
processIsolation="false"
in phpunit config

[crynobone]

Laravel Framework never officially supports using this flag as mentioned in the other issue and instead suggest using php artisan test --parallel option.

[websitevirtuoso]

Then why does it work with php8.2? I never used flag --parallel
it require extra package

[crynobone]

Then why does it work with php8.2?

When we say "it's not officially supported" that's mean that whether it is working or not it not something that we provide or guarantee support for, and any breaking to what we don't officially support are not consider as breaking changes.

[SimplyCorey]

Is this lack of support listed anywhere? This feature has been working for years within Laravel and a recent update broke it. Some repos, including mine have thousands of tests that will need rethinking which the --parallel flag doesn't provide equity for.

[arclw]

In the same boat!! Any solutions ?

[adrianodias8]

On the same boat!!
from Laravel 9 / PHP 8.1 with processIsolation="true" everything work

on Laravel 10 / PHP 8.2 fails with either #[RunInSeparateProcess] or processIsolation="true"
on Laravel 11 / PHP 8.3 fails with either #[RunInSeparateProcess] or processIsolation="true"

From what I see in my case seems related with tests that make use of Mockery::mock()

Any ideas??

I see reference of this issue here:
#49237
#49791 (was at this point that i decided to go directly to Laravel 11 hoping for some fix)

sebastianbergmann/phpunit#5677

Hey @siketyan, have you reached any conclusions on this? Can you shed some light on the matter?

[siketyan]

@adrianodias8 IIRC Laravel 11 already supports PHPUnit 11, and PHPUnit 11 has a detector of remained error handler settings; this issue should be resolved in Laravel 11. Did you tried PHPUnit 11 to see any error handler is detected after tests? If so, your code might set an error handler without removing it, not an issue of pure Laravel. I still don't know why this issue occurs on PHP >= 8.3 only. I am going to close the PR as the issue is considered as resolved in Laravel 11 or PHPUnit 11.

(I am no longer in any Laravel/PHP project for now so cannot check this issue still reproducible in Laravel 11, sorry)