Cover the recent fixes with tests #279
No reviewers
Labels
No labels
bug
documentation
duplicate
enhancement
good first issue
help wanted
invalid
missing information
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
pxlrbt/filament-excel!279
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "tests/recent-fixes"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Adds regression tests for the fixes merged over the last few PRs, which all went in untested.
tests/PruneExportsTest.phptests/DownloadExportTest.phptests/ExportDiskTest.phpfilament-exceldisk survives boottests/ExportFinishedTest.php#278 is already covered by
TableColumnsTest, #275 by the provider list inTestCase.I checked the prune and disk tests against the pre-fix code and they do fail there, so they are real regression tests.
Fix needed to make the suite runnable
The suite was red on
main: every test failed withTarget class [filament] does not exist.bootingPackage()guardedFilament::serving()withclass_exists(Filament::class), but the facade class being autoloadable does not mean thefilamentbinding is registered — which is exactly whatTestCasesets up (tables-only providers, panel package present in vendor). Switched toapp()->bound('filament'), the same guardFilamentExport::sendDatabaseNotificationForPanel()already uses.tests/TestCase.phpalso needed an array cache store and anapp.key, since the download route runs through thewebandsignedmiddleware.🤖 Generated with Claude Code