Module Laravel Laravel Package

Product Decisions This Supports

• Build vs buy on test infrastructure: this is the free OSS adapter that lets an existing Codeception suite drive a real Laravel app. Adopting it avoids writing/maintaining custom bootstrap glue or rewriting acceptance tests into another framework.
• QA roadmap and release gating: determines how much confidence we can claim for auth-protected flows, multi-guard setups (e.g. admin vs user), database state handling, mail/queue assertions, and pre-release CI checks.
• Tooling standardization: relevant if we run a mixed PHP estate and want one acceptance-test harness across Laravel and non-Laravel services instead of Laravel-only tooling.
• Migration sequencing: informs whether we move from PHPUnit-only tests to Codeception incrementally, or go the other way toward Pest/Dusk.
• Dependency cadence: 3.2.1 is a patch-level fix (implicit null guard name, PR #56) — evidence the module tracks Laravel auth internals and is safe to keep on latest patch with no migration work.

When to Consider This Package

Adopt when:

• Codeception is already (or is about to become) your acceptance/functional harness and you need Laravel-aware modules with framework bootstrapping, auth helpers, DB transactions/cleanup, and mail/queue fakes.
• You have apps using named guards, which is exactly the edge case 3.2.1 fixes — upgrading is low risk and directly removes a failure mode.
• You need one consistent test tool across mixed PHP services.

Look elsewhere when:

• You're greenfield on Laravel and have no Codeception investment — first-party Pest/PHPUnit HTTP tests plus Dusk cover most needs with less ceremony.
• You need browser-level JavaScript E2E coverage.
• You require a commercial SLA, vendor support, or long-term support guarantees.
• The team has no Codeception experience; the learning cost will outweigh the glue-code savings.

How to Pitch It (Stakeholders)

Executives: This is a free, actively maintained adapter that lets our existing Codeception test suite exercise Laravel applications realistically, so we get release confidence on authentication and data flows without a test-framework rewrite. Release 3.2.1 is a small bug fix to guard-name handling — no API changes, no deprecations, no migration work. Safe to take on the next routine dependency bump; the only cost is engineer time already budgeted, not licensing.

Engineering: Patch release only. Fixes an implicit null guard name issue in the Laravel module (PR #56); no breaking changes, no deprecations. Keep the constraint at ^3.2, run the acceptance suite against a multi-guard configuration to confirm the fix, and treat 3.x as a maintenance track — revisit if we standardize on Pest/Dusk.