Livewire Dusk Testbench Laravel Package

Product Decisions This Supports

• Testing strategy & CI investment: Decides whether package teams standardize on real-browser (Dusk) coverage for Livewire components versus lighter unit/component tests.
• Build vs. buy for test harnesses: Avoids maintaining in-house glue between Orchestra Testbench, Laravel Dusk, and Livewire.
• Ecosystem upgrade planning: Informs readiness for Laravel 13 and Livewire 4 — v3.0.0-beta.9 explicitly tracks both, which matters when planning framework/Livewire upgrade roadmaps for package maintenance.
• Use cases: Package authors shipping Livewire components; internal platform teams exposing reusable Livewire UI kits; QA of browser-level interactions (wire:model, clicks, polling) inside package repos.
• Dependency lifecycle decisions: Signals whether this package is a safe, actively maintained dev dependency versus one that will lag major framework releases.

When to Consider This Package

• You maintain a Laravel package (not an application) that ships Livewire components and want Dusk browser tests without bootstrapping a full Laravel app.
• You already use Orchestra Testbench for package testing and need Livewire Dusk integration in that harness.
• You're tracking Laravel 13 / Livewire 4 adoption and need your test harness to keep pace — this release adds both.
• Look elsewhere if: you're building a standard Laravel application (use Livewire's native Dusk helpers directly); you don't need real-browser tests; you require stable (non-beta) dependencies in your toolchain; or your team is pinned to older Laravel/Livewire versions and can't absorb v3 major-version churn.

Caveat: v3.0.0 is still in beta. Validate stability and review v2→v3 breaking changes before broad rollout; pin versions and pilot on a non-critical package first.

How to Pitch It (Stakeholders)

Executives: This is a low-cost, targeted developer-tooling dependency that keeps our Livewire component packages testable in real browsers and aligned with upcoming Laravel 13 and Livewire 4 releases. It reduces custom test infrastructure and upgrade risk. The main caveat is that it's currently a beta, so we should pilot it on a non-critical package before standardizing.

Engineering: Adopt for package repos that ship Livewire components tested under Orchestra Testbench. It removes glue code between Dusk, Livewire, and Testbench, and v3.0.0-beta.9 adds Laravel 13 (testbench-dusk 11) and Livewire 4 support — a strong maintenance signal. Because it's a major-version beta, pin versions, review the changelog for breaking changes from v2, and gate adoption behind CI green on a pilot package before rolling out broadly.