Test error (only when running suite) - Target class [config] does not exist.

Thank you but that's not it (I was aware of the boot problems). My TestCase is empty

<?php

namespace Tests;

use Illuminate\Foundation\Testing\TestCase as BaseTestCase;

abstract class TestCase extends BaseTestCase
{
    use CreatesApplication;
}

Just to make it clearer ... the issue is not running the test2 method, it is calling the dump(config()) second time in it. If there is only a single call to dump(config()) the tests pass!

It is almost as if when the first test1 is done, it unbinds the app('config') and then second test2 doesn't manage to finish on time ..

Do you have a solution for this?

It seems that I am having almost the same problem, but in my case it is Redis.

I am checking an api route and the test passes in the console but not on my IDE (PHPStorm).

Hi!

I'm having the same issue. If I call dump(route('any')) twice in the same test I get the error: Target class [config] does not exist.

dump(route('route-a'));
dump(route('route-b'));

BUT, if I put the value in a variable, it works:

$a = route('route-a');
$b = route('route-b');
dump($a);
dump($b);

Any idea?

For my case this issue happens when a testsuite is finished and the second testsuite starts running.

Did you ever find a solution for this?

Have the same issue. My app output some content to buffer. To fix error with contents already sent, I've added a phpDoc notation @runInSeparateProcess. But then get new error with Sanctum and config, as described above.

    protected function setUp(): void
    {
        parent::setUp();

         \Laravel\Sanctum\Sanctum::actingAs(
           \App\Models\Customer::query()->find(1)
        );

        // @todo Заполнение БД
        \Illuminate\Support\Facades\Config::set('test.customer.id', 4119);
    }

    /**
     * @runInSeparateProcess
     */
    public function testSomeTest() {}

Fatal error: Uncaught ReflectionException: Class config does not exist in /var/www/vendor/laravel/framework/src/Illuminate/Container/Container.php on line 879

Illuminate\Contracts\Container\BindingResolutionException: Target class [config] does not exist. in /var/www/vendor/laravel/framework/src/Illuminate/Container/Container.php on line 879

Call Stack:
    0.0012     789312   1. {main}() Standard input code:0
    1.8366    8493664   2. require_once('/var/www/config/sanctum.php') Standard input code:678
    1.8429    8505720   3. Laravel\Sanctum\Sanctum::currentApplicationUrlWithPort() /var/www/config/sanctum.php:21
    1.8429    8505720   4. config($key = 'app.url', $default = ???) /var/www/vendor/laravel/sanctum/src/Sanctum.php:37
    1.8429    8505720   5. app($abstract = 'config', $parameters = ???) /var/www/vendor/laravel/framework/src/Illuminate/Foundation/helpers.php:275
    1.8429    8505720   6. Illuminate\Foundation\Application->make($abstract = 'config', $parameters = []) /var/www/vendor/laravel/framework/src/Illuminate/Foundation/helpers.php:119
    1.8429    8505720   7. Illuminate\Container\Container->make($abstract = 'config', $parameters = []) /var/www/vendor/laravel/framework/src/Illuminate/Foundation/Application.php:836
    1.8429    8505720   8. Illuminate\Foundation\Application->resolve($abstract = 'config', $parameters = [], $raiseEvents = ???) /var/www/vendor/laravel/framework/src/Illuminate/Container/Container.php:694
    1.8429    8505720   9. Illuminate\Container\Container->resolve($abstract = 'config', $parameters = [], $raiseEvents = TRUE) /var/www/vendor/laravel/framework/src/Illuminate/Foundation/Application.php:851
    1.8429    8506096  10. Illuminate\Container\Container->build($concrete = 'config') /var/www/vendor/laravel/framework/src/Illuminate/Container/Container.php:758

For anyone coming from Google, you can get this same error when using Pest, when using the skip() method or similar, if you are trying to evaluate a condition from somewhere in your app. If you run into this, you need to add a callable to access the underlying TestCase, so that

test(
)->skip( ! Features::hasApiFeatures() ,'API support is not enabled.');

becomes

test(
)->skip( fn() =>  ! Features::hasApiFeatures() ,'API support is not enabled.');

I hope this helps someone.

In my case, the problem was that the code in the destructor was not executing. I wrote $this->createApplication(); at the end of the test so that Laravel is running at the time the destructor is called.