- How do I install sakanjo/filament-easy-testings?
- Install it as a development dependency with Composer, so it never affects your production dependency graph or runtime. Because it is a test-support package, it belongs in require-dev alongside Pest or PHPUnit rather than in require. Once installed, you consume its Filament-aware helpers and assertions directly from your feature test cases.
- Which Laravel, PHP, and Filament versions does v3.0.0 require?
- The minimum PHP, Laravel, and Filament versions for v3 are not stated in the supplied release information, so verify them in the package's composer.json and the v2.0.0...v3.0.0 diff before upgrading. A semver-major bump frequently raises these floors and may implicitly require a newer Filament major. If either your Filament major or your PHP/Laravel floor does not match, stay on v2.x rather than forcing an application framework upgrade for a test helper.
- What breaking changes are in v3.0.0 and how do I migrate from v2?
- The release notes contain only a diff link with no changelog or migration guide, so treat the diff as the specification. Budget roughly an hour to enumerate renamed, removed, or signature-changed helpers before touching Composer. Then upgrade on a dedicated branch with the lockfile committed, so rolling back is a single revert.
- Is sakanjo/filament-easy-testings safe to use in a production application?
- Yes, in the sense that it is a require-dev test-support package and is not a runtime dependency. It does not touch production request paths, the service container at runtime, or your data layer, which makes it low-risk to adopt and low-cost to remove. The blast radius of a bad version is your CI pipeline, not your users.
- Should I upgrade to v3.0.0 or stay on v2.x?
- Verify two axes first: your Filament major against the package's supported range, and your PHP/Laravel floor. If either mismatches, the correct move is to stay on v2.x, because a major test-helper upgrade is not worth forcing an application framework upgrade. Also confirm whether v2.x still receives fixes and for how long before you commit to either path.
- How does this package help me test Filament resources, pages, forms, tables, and actions?
- It extends Laravel's test harness with Filament-aware helpers and assertions, so you write less boilerplate in feature tests that exercise admin panel resources, pages, forms, tables, and actions. The goal is reliable, readable tests for your Filament UI without hand-rolling every interaction assertion. Check the diff or source for the exact helper names available in v3, since these are the APIs most likely to have changed.
- Does it work with both Pest and PHPUnit?
- Yes. It is designed to be consumed from Pest or PHPUnit test cases in a standard Laravel and Filament application. Compatibility is about shape rather than a specific runner, so your existing test suite structure should carry over.
- Why are my tests failing after upgrading to v3.0.0 and how do I triage them?
- Expect mechanical failures such as undefined methods or changed namespaces, since a major bump signals API drift in the helpers. Classify each failure as a rename, a behaviour change, or genuinely broken code. Note that if v3 changed assertion semantics rather than just names, green tests passing is not proof of equivalent coverage, so backfill assertions where needed.
- Is sakanjo/filament-easy-testings actively maintained?
- That is the weakest signal in the supplied information: v3.0.0 ships with a one-line changelog that is just a diff link, which is worth weighing for a package sitting in the critical path of your CI confidence. Ask the maintainer directly about the v2.x support window and whether a migration guide is planned. Because the package is dev-only, maintenance issues never surface in incident reviews and tend not to get prioritised until CI breaks.
- What are the alternatives to this package for testing Filament admin panels?
- The main alternatives are Filament's own testing utilities, plain Livewire test helpers, or a small in-house trait with your own panel assertions. Writing your own helpers keeps you free of third-party version coupling but costs ongoing maintenance as Filament internals change. This package is essentially a convenience layer over that same surface, so evaluate it on how much boilerplate it actually removes from your suite.