- How do I install codeception/module-lumen for Lumen tests?
- Install it as a dev dependency with Composer, typically using composer require --dev codeception/module-lumen. Then enable the Lumen module in your Codeception suite configuration so it can bootstrap your Lumen application for each test. Keep it in your test toolchain rather than your production dependencies.
- Does codeception/module-lumen work with Laravel projects or only Lumen?
- The package is specifically a Codeception module for Lumen, Laravel's microframework. It is designed for Lumen application bootstrap and Lumen-aware testing helpers rather than as a general Laravel testing module. Laravel teams using Codeception should verify compatibility or use Laravel-specific test tooling.
- What Laravel, PHP, and Codeception versions are supported by codeception/module-lumen?
- The 3.0.1 release is a compatibility update for codeception/lib-innerbrowser v4. That release note does not list exact Laravel, PHP, or Codeception version ranges, so check the package's Composer constraints before upgrading. Validate against your project's existing test matrix and lockfile.
- How does the Lumen module bootstrap the application for each test?
- It automatically boots the Lumen application for each test, so you do not need to write manual bootstrap code in every test case. This gives functional and acceptance tests a running application context. The module also exposes the service container for test access.
- Can I use database transactions and cleanup between tests with codeception/module-lumen?
- Yes. The module provides database transaction and cleanup support between tests, which helps keep functional and database-backed tests isolated. This reduces leftover state between test runs. Confirm your database configuration and cleanup settings in the Codeception suite.
- How do I access the Lumen service container or app instance in Codeception tests?
- The module exposes the Lumen service container, facades, and app instances to your Codeception tests. That lets you resolve services or interact with application bindings directly from test code. Use the module's provided helpers rather than manually bootstrapping the app.
- Does codeception/module-lumen include authentication helpers for acting as users?
- Yes. The module includes authentication helpers for acting as users in functional and acceptance tests. This is useful for testing authenticated routes and user-specific behavior without repeating login steps. Pair it with your Lumen auth configuration and test fixtures.
- What can I assert with HTTP response and route assertions in the Lumen module?
- The module provides HTTP response and route assertions for functional and API-style tests. You can verify responses and routing behavior while the Lumen app is booted by the module. This keeps request-level checks inside the Codeception workflow.
- Is codeception/module-lumen a dev-only dependency or a production dependency?
- It is test tooling and should normally be installed as a dev dependency for Codeception suites. The technical assessment notes low production runtime risk if the dependency is dev/test-only. If your application exposes Codeception integration publicly, review how consumers depend on older lib-innerbrowser versions.
- What should I check before upgrading to codeception/module-lumen 3.0.1 with lib-innerbrowser v4?
- Version 3.0.1 adds support for codeception/lib-innerbrowser v4, so first audit your Composer constraints and lockfile. Update in a test or CI branch, run composer update for the package and lib-innerbrowser, then execute your Codeception suite. If resolution fails, align test dependencies with v4 or stay on the previous package version until the suite is ready.