Configuration

Testbench utilised phpunit.xml configuration to setup environment variables value as global value for every tests.

• Application Key
• In-Memory SQLite Connection
• Application Timezone
• Using .env Environment Variables
• Using Custom Laravel Skeleton

Application Key

Most application would require APP_KEY to be defined in order to use encryption:

<phpunit>

    // ...

    <php>
        <env name="APP_KEY" value="AckfSECXIvnK5r28GVIWUAxmbBSjTsmF"/>
    </php>

</phpunit>

In-Memory SQLite Connection

To reduce setup configuration, you could use testing database connection (:memory: with sqlite driver) via setting it up under defineEnvironment() or by defining it under PHPUnit Configuration File:

<phpunit>

    // ...

    <php>
        <env name="DB_CONNECTION" value="testing"/>
    </php>

</phpunit>

Application Timezone

You can also easily override application default timezone, instead of the default "UTC":

/**
 * Get application timezone.
 *
 * @param  \Illuminate\Foundation\Application  $app
 * @return string|null
 */
protected function getApplicationTimezone($app)
{
    return 'Asia/Kuala_Lumpur';
}

Using .env Environment Variables

By default Testbench doesn't load .env file when booting the application. You can change this by setting TestCase::$loadEnvironmentVariables property to true:

class TestCase extends \Orchestra\Testbench\TestCase
{
    protected $loadEnvironmentVariables = true;

    // 
}  

Using Custom Laravel Skeleton

By default Testbench provide a basic Laravel Skeleton, however you may have a requirement to use custom skeleton, you can do that using getBasePath() method.

/**
 * Get base path.
 *
 * @return string
 */
protected function getBasePath()
{
    return __DIR__.'/../skeleton';
}