unrecognized option --env about dusk

[sgitkene]

sorry to necro such an old issue, but:

It seems like dusk should actually take --env as a parameter and not let it fall through to phpunit: (see" <----")

C:\x\x\PhpstormProjects\x>php artisan dusk --help
Usage:
  dusk [options]

Options:
      --without-tty     Disable output to TTY
  -h, --help            Display this help message
  -q, --quiet           Do not output any message
  -V, --version         Display this application version
      --ansi            Force ANSI output
      --no-ansi         Disable ANSI output
  -n, --no-interaction  Do not ask any interactive question
      --env[=ENV]       The environment the command should run under   <---- 
  -v|vv|vvv, --verbose  Increase the verbosity of messages: 1 for normal output, 2 for more verbose output and 3 for debug

Help:
  Run the Dusk tests for the application



C:\Users\sgitkene\PhpstormProjects\IP34-17vt_Leseportal>

But the output I get is:

C:\x\x\PhpstormProjects\x>php artisan dusk --env=dusk.remote
Warning: TTY mode is not supported on Windows platform.
PHPUnit 7.1.4 by Sebastian Bergmann and contributors.

unrecognized option --env

[splatEric]

The initial environment settings are driven by the contents of the .env file.

If .env is not present, it defaults to production.

I think your env option is being picked up by artisan, but the call to phpunit that the DuskCommand makes passes the arguments through to phpunit ... I wonder if there would be any benefit to stripping out options that artisan can consume?

[mstnorris]

This doesn't work for me. I cannot get Dusk to adhere to the .env.dusk.testing or .env.dusk.local environments by either using a MySQL or SQLite database:

http://stackoverflow.com/questions/41908118/set-up-laravel-5-4-with-dusk-using-phpunit-xml-env-dusk-local-and-an-sqlite-i

[melihovv]

unrecognized option --env it is from phpunit

You can extend DuskCommand and override arguments, which are passed to phpunit.

class DuskCommand extends \Laravel\Dusk\Console\DuskCommand
{
    protected function phpunitArguments($options)
    {
        $arguments = parent::phpunitArguments($options);

        for ($i = 0, $count = count($arguments); $i < $count; ++$i) {
            if (Str::startsWith($arguments[$i], '--env')) {
                unset($arguments[$i]);
            }
        }

        return $arguments;
    }
}

[deleugpn]

Any value you set as your APP_ENV in your .env will be used to load a .env.dusk.{YOUR_ENV}. You can combine Dusk with Serve:

php artisan serve --env=dusk.local &
php artisan dusk

PHP Internal Server will provide you an application with .env.dusk.local file and if you set .env's APP_ENV to local, when running dusk it will default to the same .env.dusk.local.

[driesvints]

Closing this issue because it's already solved, old or not relevant anymore. Feel free to reply if you're still experiencing this issue.