What is the best pratice for writing tests ?

@Nakov ok thank you ... that's true I have not seen any tutorial for Laravel ... only small MOOC about the theory

@Nakov Yes you suggested me to use factories, but I didn't understand where ... I will have a look at some tutorials using Laravel.

@Sinnbeck Ok ... effectively my tests are not independant ... so that means ... if I want to test deleting a row, it's necessary to create this row inside the test ? Or is it a good idea to create a lot of data with factories and work with them ?

@vincent15000 you can have a tearDown() method that cleans up after each test. And setUp() to prepare stuff. They are automatically called by phpunit

@Sinnbeck and @nakov Here is an example of what I have done according to your suggestions.

My tests are now independant but I'm not sure if it's a good idea how I test the update of an author. It works ... but ...

Same question for create test, perhaps it would be a better idea to use a factory with make() to create my model, then pass it to the Livewire component to be saved and then test if the model exists.

UPDATED WITHOUT THE PRIVATE PROPERTIES

class AdminTypeTest extends TestCase
{

    private User $user;

    protected function setUp(): void
    {
        parent::setUp();
        $this->user = User::factory()->admin()->create();
    }

    protected function tearDown(): void
    {
        parent::tearDown();
        $this->user->delete();
    }

    /** @test  */
    public function admin_can_access_table()
    {
        $response = $this->actingAs($this->user)->get('admin/types');
        $response->assertStatus(200);
    }

    /** @test  */
    public function admin_can_create()
    {
        $this->actingAs($this->user);
        $type = Type::factory()->make();
        Livewire::test(AdminTypeForm::class)
            ->set('updateMode', false)
            ->set('type.name', $type->name)
            ->set('type.description', $type->description)
            ->call('save');
        $type = Type::
            where('name', $type->name)
            ->where('description', $type->description)
            ->first();
        $this->assertModelExists($type);
        $type->delete();
    }

    /** @test  */
    public function admin_can_update()
    {
        $this->actingAs($this->user);
        $type = Type::factory()->create();
        $typeUpdated = Type::factory()->make();
        Livewire::test(AdminTypeForm::class)
            ->set('updateMode', true)
            ->call('initForm', $type->id)
            ->set('type.name', $typeUpdated->name)
            ->set('type.description', $typeUpdated->description)
            ->call('save');
        $doesntExist = Type::
            where('name', $type->name)
            ->where('description', $type->description)
            ->doesntExist();
        $exists = Type::
            where('name', $typeUpdated->name)
            ->where('description', $typeUpdated->description)
            ->exists();
        $this->assertTrue($doesntExist);
        $this->assertTrue($exists);
        $type->delete();
    }

    /** @test  */
    public function admin_can_delete()
    {
        $this->actingAs($this->user);
        $type = Type::factory()->create();
        Livewire::test(AdminTypes::class)
            ->call('delete', $type->id);
        $this->assertDeleted($type);
    }

    /** @test  */
    public function member_cannot_access_table()
    {
        $user = User::factory()->create();
        $response = $this->actingAs($user)->get('admin/types');
        $response->assertStatus(302);
        $user->delete();
    }

}

@vincent15000 Much better, you see you can do it.

As for your question, if you are creating a new user a proper test would be to fill in the fields in the livewire form without a factory but just with data from your test and run an expectation/assertion if a record with that data exists in the database afterwards.

And if you want test data, yes, use ->make() rather than create() because create also creates the record in the database directly, skipping your livewire component.

@Nakov Ok ... so what you mean is to simulate to fill the fields in the livewire form ... for the moment I just set the variables via simple set() methods. I'll have a look how to simulate to fill fields in a form.

That can be done with dusk isn't it ? It looks great.

@vincent15000 no, I meant using set as this is not a browser test, but you don't need a factory in order to set the variables, was my point. But yeah, you could use Dusk if you want to run browser tests.

@Nakov Ok thank you ;) ... I have changed some lines in my code in order to use make() to generate the datas via the factory, it's more easy to manage and then I pass them to the livewire component using set(), so I can test my livewire controller methods.

I try now the dusk package to test the form.