Deploy migrations for test env only

You may want to refer to laravel factories for that matter. Look up the documentation! :)

Thank, I use factories for sure, but the term "Objects" i used was inappropriate in my case, the thing i wanted to do is something like this : https://laracasts.com/discuss/channels/testing/is-there-a-check-to-skip-a-specific-migration-for-unit-tests-in-a-migration-class

You can create a separate folder for these migrations and then override runDatabaseMigrations method from DatabaseMigrations trait by setting --path param to migration:fresh command to your main and testing migration folders. So that testing migrations would only run when migrating testing database.

https://github.com/laravel/framework/blob/6.x/src/Illuminate/Foundation/Testing/DatabaseMigrations.php#L16

You can check your .env file to run some migrations.

public function up()
{
    if (env('APP_ENV') == 'testing'){
        Schema::create('users', function (Blueprint $table) {
            $table->bigIncrements('id');
            $table->timestampsTz();
        });
    }
}

@taner that's not a clean solution, because these empty migrations will still run in the production.

Just came here after a little bit of Googling and can't believe I didn't think of it myself but @taner solution makes complete sense.

It'll only run when unit tests are being performed as the environment on production will match production

Thanks!

Instead of checking your env in the migration, add this to the boot method of your AppServiceProvider

 if($this->app->environment('testing')){
     $this->loadMigrationsFrom(base_path('tests/database/migrations'));
}

Then create a directory at /tests/database/migrations and add the migrations you want to only run in your test suite there.