Ref: https://filamentphp.com/docs/3.x/tables/testing

• Removing filters #153
• Actions with Url #135
• Pre-filled data
• Summaries #153
• Extra Attributes #120
• Select Columns #119
• Resetting filters #115
• Descriptions #95

https://filamentphp.com/docs/3.x/panels/resources/relation-managers#relation-pages

Eliminating the step to manually add the stubs to the getStubs() would be nice

This would require some sort of ordering (perhaps by group + abc)

Need to add a check that it will only be applied to text columns. Otherwise errors like this:

Method Filament\Tables\Columns\ImageColumn::getDescriptionAbove does not exist. will be thrown.

https://filamentphp.com/docs/3.x/tables/testing#state

Running as stated in the readme: php artisan filament:make-test UserResource will generate a new file named UserTest.php with content of:

use App\Filament\Resources\UserResource\Pages\ListUserResources;

use function Pest\Livewire\livewire;

it('can render the userresource list page', function () {
    livewire(ListUserResources::class)->assertSuccessful();
});

I think the expected result should be:

UserResourceTest.php with content:

use App\Filament\Resources\UserResource\Pages\ListUsers;

use function Pest\Livewire\livewire;

it('can render the UserResource list page', function () {
    livewire(ListUsers::class)->assertSuccessful();
});

• Login #170
• Register #171
• Forgot password #172
• Logout

• EditAction
• ViewAction
• RestoreBulkAction #74
• ForceDeleteAction #76
• ForceDeleteBulkAction #77
• ReplicateAction #71
• RestoreAction #72
• DeleteAction #65
• BulkDeleteAction #65

Setting up a local project that satisfies every single possible test.

This should be high priority to confirm quality for upcoming PR's and reduce the time to actually review.

There is so much variability already -> with soft deletes, pages, actions, header actions, bulk actions, filters etc...That testing features manually seems very improbable.

• simple pagination
• cursor pagination
• extreme

If your table uses pagination, assertCanSeeTableRecords() will only check for records on the first page. To switch page, call call('gotoPage', 2).

https://filamentphp.com/docs/3.x/tables/testing#render

If the resource uses the User::class model (UserResource), the count and therefor the assertions are mismatched because of the user we generate in the beforeEach

Need to add an additional stub for the UserResource

Should probably add tests for isFiltered

Perhaps have an empty textfile generated the first time a test was generated and check if the file already exists?!

• regular stub
• todo stub

Ask the user if they want to run the generated tests

vendor/bin/pest --group="filament-tests"

It should be opt-out'able

php artisan make:filament-test --dontRun (or something similar)

https://filamentphp.com/docs/3.x/tables/testing#columns

If you were to generate a test for the UserResource (or any resource) that uses App\Models\User as the underlying model, that would cause the use App\Models\User; to be used twice, which would cause a fatal error at runtime.

For better readability we should add helper methods to get rid off ->isNotEmpty() calls.

Example:

public function getShouldGenerate(): bool
{
    return $this->getResourceTableFilters($this->getResourceTable($this->resource))->isNotEmpty();
}

to

public function getShouldGenerate(): bool
{
    return $this->hasTableFilters();
}

Additionally we could add hasAnyTableFilter(array $filters) ... and similar

Similar to #171 but after #164

([URI: blogs/{record}/process] [Missing parameter: record].)

We should add sanity checks like

expect({{ MODEL_SINGULAR_NAME }}::count())->toBe(X);

at the beginning of the test and throughout (where applicable)

Note: beforeEach's user