[4.x] Fixed ColumnTests Assertions with Custom Data Table

[Patabugen]

Description

The assertion methods listed below allow passing either an Eloquent Record or the the row index as the $record parameter.

The functionality works - but the phpunit messages use $record->getKey() which mean the assertions fail when used with an index instead of an Eloquent Record causing an error.

• assertTableColumnStateSet
• assertTableColumnStateNotSet
• assertTableColumnFormattedStateSet
• assertTableColumnFormattedStateNotSet
• assertTableColumnHasExtraAttributes
• assertTableColumnDoesNotHaveExtraAttributes
• assertTableColumnHasDescription
• assertTableColumnDoesNotHaveDescription
• assertTableSelectColumnHasOptions
• assertTableSelectColumnDoesNotHaveOptions

Visual changes

None

Functional changes

• Added assertTableRecordKeyExists to give a friendly error if an invalid index is passed
• Updated other assertions to use the passed $record as the $key if it is not an Eloquent Model
• Added a CustomDataTable fixture (based on the existing `PostsTable)

Workaround

In case anyone else needs a workaround before this is merged:

Add this to your TestCase:

namespace Tests;

use Illuminate\Foundation\Testing\TestCase as BaseTestCase;
abstract class TestCase extends BaseTestCase
{
    /**
     * Workaround for this bug: https://github.com/filamentphp/filament/pull/19092
     */
    protected function workaroundFilamentBug(\Closure $closure)
    {
        try {
            $closure();
        } catch(\Error $e) {
            if ($e->getMessage() !== "Call to a member function getKey() on array") {
                throw $e;
            }
        }
    }
}

And use it like this:

$page = Livewire::test(MyPage::class);
$this->workaroundFilamentBug(fn() => $page->assertTableColumnStateSet('column_name', 3, 1));

[Patabugen]

@danharrin Do I need to make another PR to apply this to Filament v5?

[danharrin]

No