Database migrations aren't run when using the trait

[mstnorris]

Using the dev version of Laravel (namely the yet-to-be-released 5.4) I've done as the docs state, but the migrations are not being run.

I'm following along Adam Wathan's TDD course so using the previous ->visit and ->see methods.

[splatEric]

I am having the same problem ... am having a poke around to see if I can work out why ...

[splatEric]

Okay, looks like you need to switch the DatabaseMigrations use statement as well. Looking at the code in the Laravel\BrowserKitTesting\TestCase, the setupTraits is expecting Traits to be in the Laravel\BrowserKitTesting namespace, so this will apply for any Illuminate\Foundation\Testing\* traits you might be using.

In this particular case, instead of

use Illuminate\Foundation\Testing\DatabaseMigrations;

you need

use Laravel\BrowserKitTesting\DatabaseMigrations;

If you have a lot of tests and don't want to have to change your use statements, an alternative workaround would be to add the following to your BrowserKitTestCase

protected function setUpTraits()
{
    parent::setUpTraits();

    if (method_exists($this, 'runDatabaseMigrations')) {
         $this->runDatabaseMigrations();
    }
}

[splatEric]

The latest commit:

a038083

has addressed this issue by using the core traits instead. So you can ignore my previous suggestion going forward!

[amochohan]

@taylorotwell looks like this issue can be closed