Factory FirstOrCreate

Hello,

In your test, you can choose to use RefreshDatabase to reset all your database or DatabaseTransactions to remove everything you added in your test.

I think you are doing some test with your Permission class which does not delete what you added previously, that's why you have the Permission… or not.

When you run php artisan test, it's not running sequentially, if a previous test is executed before your current test (with the firstOrCreate), the Permission already exists, then you can't create it.

I hope it helps you.

I've migration who create some permissions, that's why i wan't to use firstOrCreate, if doesn't exist he should create it using his factory, i thought there was a way to do it through factory itself

There is no firstOrCreate (or equivalent) on the FactoryBuilder class, but it is macroable, so you can implement that behaviour yourself.

Otherwise in your test setup, you could either (i) wrap the factory function call in a try/catch:

try {
	$viewPermission = factory(\App\Permission::class)->create(['name' => 'view_user']);
} catch (QueryException $e) {
	$viewPermission = \App\Permission::class)->where('name', 'view_user')->first;
}

or (ii) use the Model itself

$viewPermission = \App\Permission::firstOrCreate(factory(\App\Permission::class)->raw());

But with the Model i cannot pass the factory because he will create different model everytime, even if i specify the name other properties will be different. Probably i will go with the first

True. I don't have sight of your PermissionFactory, so I don't know if there is more attributes than the name!

If you take that second example again, you can use firstOrCreate on the name attribute like this:

$viewPermission = \App\Permission::firstOrCreate(
	$attributes = ['name' => 'view_user'],
	factory(\App\Permission::class)->raw($attributes)
);