testing in Laravel 5.5 : Class env does not exist

Question

i am starting tests in laravel

i created a ".env.testing" file with this

APP_NAME=myApp
APP_ENV=testing
APP_DEBUG=true
APP_LOG_LEVEL=debug
APP_URL=http://myApp.localhost

DB_CONNECTION=sqlite_testing

i added this in the "connections" part of config/database.php file

...
'sqlite_testing' => [
    'driver'   => 'sqlite',
    'database' => ':memory:',
    'prefix'   => '',
],
...

in the phpunit.xml file, i added :

<env name="DB_CONNECTION" value="sqlite_testing" />

and i created a UserTest feature :

class UserTest extends TestCase
{

    public function setUp()
    {
        parent::setUp();
        Artisan::call('migrate');
        Artisan::call('db:seed');
    }

    public function tearDown()
    {
        parent::tearDown();
        Artisan::call('migrate:reset');
    }


    public function testCanAccessUserSpace()
    {
        $user = factory(User::class)->create();

        $response = $this->actingAs($user)
            ->get('/home');


        $response->assertStatus(200);
    }
}

But when i run the tests, i have this :

ReflectionException: Class env does not exist

What's wrong with my config ?

thanks

Answer 1

I had same error while running the phpunit:

ReflectionException: Class env does not exist

Here was another problem, I've installed package telescope and phpunit tried to load it while testing:

ReflectionException: Class env does not exist
/var/www/html/mat2/vendor/laravel/telescope/src/Telescope.php:263
/var/www/html/mat2/vendor/laravel/telescope/src/Telescope.php:222

and so on. I've added to phpunit.xml:

<env name="TELESCOPE_ENABLED" value="false"/>

Afterwards, tests are running fine.
So, it may be package testing related error.

Answer 2

In my case, set TELESCOPE_ENABLED to false doesn't solve my problem. I have to issue

php artisan config:clear

I use Laravel 7.

Answer 3

If you are using php artisan test --env=testing, add TELESCOPE_ENABLED=false to your .env.testing file and run php artisan config:cache --env=testing.

Answer 4

Looks like this exception is thrown for a variety of reasons. In your case the issue is with the tearDown function, in specific order of operations within this function. You should call the parent tearDown at the bottom. So this:

public function tearDown()
{
    parent::tearDown();
    Artisan::call('migrate:reset');
}

Should be refactored as follows:

public function tearDown()
{
    Artisan::call('migrate:reset');
    parent::tearDown();
}

I suspect the reason is that the app instance gets destroyed inside Illuminate\Foundation\Testing\TestCase. here is the code from Laravel 5.5:

if ($this->app) {
    foreach ($this->beforeApplicationDestroyedCallbacks as $callback) {
        call_user_func($callback);
    }

    $this->app->flush();

    $this->app = null;
}

Answer 5

This error can be caused by telescope being turned on in a unit testing environment.

I change the default behaviour of telescope to be off and explicitly turn it on in my .env file.

You can change the default to false for telescope by updating your config/telescope.php file.

    /*
    |--------------------------------------------------------------------------
    | Telescope Master Switch
    |--------------------------------------------------------------------------
    |
    | This option may be used to disable all Telescope watchers regardless
    | of their individual configuration, which simply provides a single
    | and convenient way to enable or disable Telescope data storage.
    |
    */

    'enabled' => env('TELESCOPE_ENABLED', false), // Change from true to false here.

You will then have to set: TELESCOPE_ENABLED=true in your .env file. This will ensure that you don't have it accidentally turned on in environments you don't want such as production and unit testing.

Answer 6

Might be a bit late for a reply, but the below line in phpunit.xml solved the issue.

<server name="TELESCOPE_ENABLED" value="false"/>

Answer 7

I faced this issue and found issue in config folder > constants file I was wrote "asset('/')" function in config file, we can't write such functions in config.

Hope this answer will help someone who stuck like this errors.

Answer 8

You need to rename .env.testing to .env, you already set APP_ENV to testing so there is no need to change your .env to .env.testing

EDIT:

Also try to update your dependencies with composer update and try again, it's not a usual bug, so it's something related to your setup of testing environment

Answer 9

I have the same problem in my config/services.php file, my error was calling the route() method in array. I just removed the method and back to works.

Answer 10

For laravel version 8 change app()->environment() to env('ENV_NAME') like

env('SMS_SERVICE_ENDPOINT')

Example:

Previous: app()->environment() === 'production'

New Format should be env('DEV_ENV') === 'production')

Note: Don't forget to add DEV_ENV=production in your .env file

Answer 11

In laravel 8, don't try to use laravel global helper function or Facade after TestCase::tearDown:

class MyTestCase extends TestCase
{
  public function tearDown(): void
  {
    parent::tearDown();
    // This will case this exception:  Target class [env] does not exist
    echo app()->environment();
  }
}

Instead, move method BEFORE parent::tearDown, it will work:

public function tearDown(): void
{
   echo app()->environment();
   parent::tearDown();
}