Jo Comments - Answer Overflow

Topics

Jo

•Created by Jo on 4/17/2024 in #❓┊help

Testing a Livewire component that is has been added to an Infolist

Thank you for replying. Yes, after writing a bunch of tests following this method it seeems to be working quite well. I also read on the Livewire site that testing components in isolation is the way to go, so it was obviously wrong for me to be essentially trying to test one component through another. Thanks again for your help!

14 replies

•Created by Jo on 4/17/2024 in #❓┊help

Testing a Livewire component that is has been added to an Infolist

So maybe I misunderstood how testing is supposed to be conducted? Is it good enough just to test the Resource for assertSeeLivewire() in one test and then for the next test test the actual Component for the behaviour of actions?

14 replies

•Created by Jo on 4/17/2024 in #❓┊help

Testing a Livewire component that is has been added to an Infolist

Yes, that assertion works for me.

14 replies

•Created by Jo on 4/17/2024 in #❓┊help

Testing a Livewire component that is has been added to an Infolist

I put some info in the README file of the repo to show which tests are currently failing and which are passing.

14 replies

•Created by Jo on 4/17/2024 in #❓┊help

Testing a Livewire component that is has been added to an Infolist

Ok, so I've been tinkering about today to create a mini repo as you mentioned, and in doing so I have actually made some progress because the mindset behind making a mini repo is forcing me to go back to basics! What I have discovered is that can do effective testing if I target the Livewire component directly. But I just can't do it from the resource. I have to do it in 2 steps. One step test canSeeLivewire() on the resource and then another test to do all the assertions for the actions on the Livewire component itself. Anyway, I created the mini repo as you mentioned yesterday. If you have time, please take a look at the tests tests/Feature/PostTest.php and let me know if you think this is the best way to do it or if there's a better way? https://github.com/joseph-d/filament-livewire-test My biggest concern doing it this way is that I'm not truly testing if the action works when nested in the resource, because I'm testing the two things separately. So I'd like to find an integrated way to accomplish this if it's possible?

14 replies

•Created by Jo on 4/17/2024 in #❓┊help

Testing a Livewire component that is has been added to an Infolist

Ok, I'll put one together and then let you know! Thanks!

14 replies

•Created by Jo on 4/17/2024 in #❓┊help

Testing a Livewire component that is has been added to an Infolist

No, using call doesn't seem to make any difference. I also dumped out the entire output of the test and I can see from the HTML that it's telling the truth, the component really isn't there! So I think it must be something I'm missing in the way I'm doing livewire(ViewJob::class ... etc that isn't including the Livewire component from the schema for some reason. I don't know what though.

14 replies

•Created by Jo on 4/9/2024 in #❓┊help

Testing actions defined within extraModalFooterActions()

Thank you for your help!

15 replies

•Created by Jo on 4/9/2024 in #❓┊help

Testing actions defined within extraModalFooterActions()

Yeah, it's fine now that I know to do it 🙂

15 replies

•Created by Jo on 4/9/2024 in #❓┊help

Testing actions defined within extraModalFooterActions()

Yes, that passes too.

15 replies

•Created by Jo on 4/9/2024 in #❓┊help

Testing actions defined within extraModalFooterActions()

Also, something very weird which I don't understand is that this does pass:

it('displays the 2nd modal again', function () {
    livewire(ViewJob::class, [
        'record' => $this->job->getRouteKey(),
    ])
        ->call('mountInfolistAction', 'action1', '.action1Action', 'infolist')
        ->call('mountInfolistAction', 'action2', '.action1Action', 'infolist')
        ->assertSee('Action 2');
});

it('displays the 2nd modal again', function () {
    livewire(ViewJob::class, [
        'record' => $this->job->getRouteKey(),
    ])
        ->call('mountInfolistAction', 'action1', '.action1Action', 'infolist')
        ->call('mountInfolistAction', 'action2', '.action1Action', 'infolist')
        ->assertSee('Action 2');
});

Note that I'm using .action1Action for both of them and that I've switched the name and component arguments around in call() compared to the order they're in when using mountInfolistAction() as it seems to require them in the opposite order. So two weird things here: 1) It works with call() but not mountInfolistAction() and 2) It necessary to swap the order of the arguments. Do you think it could be a bug?

15 replies

•Created by Jo on 4/9/2024 in #❓┊help

Testing actions defined within extraModalFooterActions()

(also, I did try .action2Action and it made no difference, the test fails in the same way)

15 replies

•Created by Jo on 4/9/2024 in #❓┊help

Testing actions defined within extraModalFooterActions()

No description

15 replies

•Created by Jo on 4/9/2024 in #❓┊help

Testing actions defined within extraModalFooterActions()

Well that's what I thought at first, yes, but Filament actually renders the HTML as .action1Action for the 2nd one too.

15 replies

•Created by Jo on 4/9/2024 in #❓┊help

Testing actions defined within extraModalFooterActions()

Well that was a cut-down example because my real code is quite long. I guess it wasn't clear though so I've written a complete new example which is just the Infolist and the Tests to be more clear: Infolist:

    public static function infolist(Infolist $infolist): Infolist
    {
        return $infolist
            ->schema([
                Actions::make([
                    Action::make('action1')
                        ->modalHeading('Action 1')
                        ->requiresConfirmation()
                        ->action(function () {
                            dd('action1');
                        })    
                        ->extraModalFooterActions([
                            Action::make('action2')
                                ->modalHeading('Action 2')
                                ->requiresConfirmation()
                                ->action(function () {
                                    dd('action2');
                                })
                        ]),
                ])
            ]);
    }

    public static function infolist(Infolist $infolist): Infolist
    {
        return $infolist
            ->schema([
                Actions::make([
                    Action::make('action1')
                        ->modalHeading('Action 1')
                        ->requiresConfirmation()
                        ->action(function () {
                            dd('action1');
                        })    
                        ->extraModalFooterActions([
                            Action::make('action2')
                                ->modalHeading('Action 2')
                                ->requiresConfirmation()
                                ->action(function () {
                                    dd('action2');
                                })
                        ]),
                ])
            ]);
    }

Test:

use App\Filament\Resources\JobResource\Pages\ViewJob;
use App\Models\Job;

use function \Pest\Livewire\livewire;

beforeEach(function () {
    $this->job = Job::factory()->create();
});

it('displays the 1st modal', function () {
    livewire(ViewJob::class, [
        'record' => $this->job->getRouteKey(),
    ])
        ->mountInfolistAction('.action1Action', 'action1', infolistName: 'infolist')
        ->assertSee('Action 1');
});

it('displays the 2nd modal', function () {
    livewire(ViewJob::class, [
        'record' => $this->job->getRouteKey(),
    ])
        ->mountInfolistAction('.action1Action', 'action2', infolistName: 'infolist')
        ->assertSee('Action 2');
});

use App\Filament\Resources\JobResource\Pages\ViewJob;
use App\Models\Job;

use function \Pest\Livewire\livewire;

beforeEach(function () {
    $this->job = Job::factory()->create();
});

it('displays the 1st modal', function () {
    livewire(ViewJob::class, [
        'record' => $this->job->getRouteKey(),
    ])
        ->mountInfolistAction('.action1Action', 'action1', infolistName: 'infolist')
        ->assertSee('Action 1');
});

it('displays the 2nd modal', function () {
    livewire(ViewJob::class, [
        'record' => $this->job->getRouteKey(),
    ])
        ->mountInfolistAction('.action1Action', 'action2', infolistName: 'infolist')
        ->assertSee('Action 2');
});

The 1st test passes, the 2nd test fails.

15 replies

•Created by Jo on 3/22/2024 in #❓┊help

Testing relation managers

Anyone have any idea about this? It seems like I'm inadvertently testing whether the relationmanager works, when what I am really trying to do is test to see whether it's being displayed on a given page. This is because I have logic to hide the relation manager when the record has a certain status. So I want to test for that.

3 replies

•Created by Jamie Cee on 2/20/2024 in #❓┊help

http instead of https production issue

With the latest Laravel 11 update, the way to do this has changed slightly, see https://laravel.com/docs/11.x/requests#configuring-trusted-proxies

7 replies

•Created by Avriant on 3/1/2024 in #❓┊help

How to remove these inline styles (copy location returns undefined)

@Avriant Great! Thanks for sharing. I'll use that in my project now!

20 replies

•Created by Laurens on 3/1/2024 in #❓┊help

Overwrite table widget label

To make it translatable you'll have to define it as a method though:

    protected function getTableHeading(): string
    {
        return __('Translatable Custom Heading');
    }

    protected function getTableHeading(): string
    {
        return __('Translatable Custom Heading');
    }

5 replies

•Created by Laurens on 3/1/2024 in #❓┊help

Overwrite table widget label

By label, do you mean the heading of the table? If so, it's just this at the top of your table widget file:

protected static ?string $heading = 'Custom Heading';

protected static ?string $heading = 'Custom Heading';

5 replies