Access 2 values from .env in phpunit.xml (without a new .env.testing file)

Try it with <php><env> see https://github.com/laravel/framework/blob/7.x/phpunit.xml.dist

in your phpunit.xml

<php>
  <env name="DB_CONNECTION" value="YOUR-VALUE-HERE" force="true" />
</php

@click I dont think you're understanding the question.

<server name="DB_DATABASE" value="abc" />

works fine.

I am trying to get 'value' of DB_DATABASE from a DIFFERENT .env variable that I have defined in my .env file, called DB_DATABASE_PHPUNIT.

The idea is that I can't have different versions of my phpunit.xml file on dev/staging/production. So I am trying to read from my .env file - is this possible? I really would like to avoid a new .env.testing file - it becomes a maintenance burden.

@connecteev Maybe this could work https://stackoverflow.com/a/35228697

Why would it be "maintenance burden" isn't it only 1 file you have to add on each server once?

Another option you could try is to change the .env variables in the bootstrap.php of phpunit.xml itself or in the setUp / setUpBeforeClass methods as long as you do it before Laravel is setup and the database connection is made. I'm not sure if this a good idea but I had it working once in the past with: https://www.php.net/manual/en/function.putenv.php

@michaloravec it's an interesting idea, but it doesn't quite work..

config/database.php:

        'testing' => [
            'driver' => env('DB_DRIVER_PHPUNIT'),
            'url' => env('DATABASE_URL'),
            'host' => env('DB_HOST', '127.0.0.1'),
            'port' => env('DB_PORT', '3306'),
            'database' => env('DB_DATABASE_PHPUNIT'),
            'username' => env('DB_USERNAME_PHPUNIT'),
            'password' => env('DB_PASSWORD_PHPUNIT'),
        ],

.env file:

DB_CONNECTION_PHPUNIT=testing
DB_DRIVER_PHPUNIT=mysql
DB_DATABASE_PHPUNIT=my_laravel_testing_db
DB_USERNAME_PHPUNIT=root
DB_PASSWORD_PHPUNIT=root

phpunit.xml:

    <php>
        <server name="APP_ENV" value="testing"/>
        <server name="BCRYPT_ROUNDS" value="4"/>
        <server name="CACHE_DRIVER" value="array"/>
        <server name="DB_CONNECTION" value="testing"/>
        <server name="MAIL_MAILER" value="array"/>
        <server name="QUEUE_CONNECTION" value="sync"/>
        <server name="SESSION_DRIVER" value="array"/>
    </php>

This is what I have in my Feature/Api/PostsApiTest.php:

<?php
// See more sample TDD / Unit Test code in /Users/kunalpunjabi/Code/KEENBRAIN_NUXT/TDD/devlob_apis_in_laravel_using_tdd/tests/Feature/Http/Controllers/

namespace Tests\Feature\Api;

use Illuminate\Foundation\Testing\RefreshDatabase;
use Illuminate\Foundation\Testing\WithFaker;

use Tests\TestCase;
use App\User;
use Symfony\Component\HttpFoundation\Response;

class PostsApiTest extends TestCase
{
    use RefreshDatabase; // cleans out the entire database

    public function setUp(): void
    {
        // parent::setUp();
        // $this->artisan('passport:install');
    }

    public function tearDown(): void
    {
        // parent::tearDown();
    }


    /**
     * Can do something
     * @test
     */
    public function can_do_something()
    {
        $user = \App\User::find(['id' => 1]);
        $this->assertTrue($user->email == "[email protected]");
    }

This is the error I see on running phpunit:

There was 1 error:

1) Tests\Feature\Api\PostsApiTest::can_do_something
Error: Call to a member function connection() on null

@click thanks for the tips, appreciate you responding. The maintenance burden comes from updating the .env.testing file for local, dev, staging, production with every addition of an env variable... I have these .env files for these environments and it's already starting to get unweildy..

@connecteev regarding your code sample in the comment above, you are overwriting the setUp() in this sample without doing a parent::setUp() which is necessary to setup the Laravel application and everything that comes with it.

@click @michaloravec thank you