e2e-filament-multitenant

E2E Testing — Laravel + Filament (multi-tenant, per-role)

Build a Playwright E2E suite that proves each role can do what it should and cannot do what it shouldn't, across every Filament panel — including tenant isolation. Work phase by phase; do not jump to writing specs before the discovery and infrastructure phases are done.

Phase 1 — Discover the app's shape

Before writing any test, map the surface from source (never guess labels):

1. Panels & roles — read app/Providers/Filament/*PanelProvider.php to list panels, their path prefixes, and whether they are tenant-scoped (->tenant(...)). Read the roles/permissions source of truth (e.g. database/permissions.yaml + the RolesAndPermissionsSeeder), and the seeders for the test users/workspaces.
2. Login forms — there are usually two shapes:
   • Standard Filament login (email + password) for the admin panel.
   • Custom tenant login (e.g. a workspace Select + email + password) for tenant-scoped panels. Read the custom Login page class to learn the exact field label and any post-auth membership check (and its error message).
3. Resources & actions per panel — for each role's resource list page and ViewRecord/EditRecord page, read getHeaderActions() and the resource's canCreate()/canEdit()/canViewAny() overrides. Record the literal ->label() strings, notification titles (Notification::make()->title(...)), form field labels, and the ->visible(fn () => $state->is(...)) guards. These literals are the contract your assertions check.
4. State machine (if using spatie/laravel-model-states) — note the state order and which transition each action performs. Watch for cross-role gates: a single role often cannot drive the whole lifecycle because the next action is only visible in a state that a different role produces. Plan to test transitions in isolation, not as one long chain.

Summarize findings as a per-role table before proceeding.