Weave Code
Laravel Database Migrate Test Listener Laravel Package
softonic/laravel-database-migrate-test-listener
A small Laravel package that listens for database migration events, letting you run custom logic or tests whenever migrations are executed. Use it to trigger test suites, notifications, or other post-migration tasks in development and CI workflows.
Laravel database migrate test listener
Frequently asked questions about Laravel Database Migrate Test Listener
- How do I install softonic/laravel-database-migrate-test-listener?
- Install it with Composer using composer require softonic/laravel-database-migrate-test-listener. Because it is a Laravel package, check whether Laravel package auto-discovery registers the service provider or whether you need to add it manually. Review the package README and release notes for the version that matches your Laravel version before installing.
- Which Laravel versions does this package support?
- The supplied assessment only documents a 3.1.0 baseline tied to Laravel 9 and PHP 8.0+, and it does not provide a full compatibility matrix. Treat Laravel 9 as the documented baseline and verify the exact Composer constraints in the package's composer.json before adopting it. If you need Laravel 8 or PHP 7.4, confirm support or pin an older compatible release.
- What does softonic/laravel-database-migrate-test-listener actually do?
- It listens for Laravel database migration events and lets you run custom logic when migrations are executed. Typical uses include triggering test suites, sending notifications, or running post-migration checks in development and CI workflows. It is a small integration package, not a migration generator or database management tool.
- How do I configure it to run tests after Laravel migrations?
- Configuration details are not fully documented in the supplied data, so first confirm how the package registers its listener and whether it publishes a config file. In a typical Laravel package you would publish the config, choose the migration events to listen for, and point the listener at your test command or callback. Check the package README and release notes for the exact config keys before relying on it in CI.
- Can I use this package in production?
- The package is aimed at development and CI workflows, such as running tests or post-migration tasks after database migrations. Automatically running test suites in production is usually unsafe, but the listener could trigger non-test logic if configured carefully. The assessment data is too thin to confirm production hardening, so evaluate it in staging before any production use.
- Is softonic/laravel-database-migrate-test-listener actively maintained?
- The assessment is a baseline based only on release notes for 3.1.0 and does not describe the maintenance policy or support window. It appears to be an internal Laravel baseline package for laravel-base projects rather than a broadly documented public library. Check the repository's release history, issue activity, and support matrix before depending on it long term.
- What are alternatives to this package for running tests after Laravel migrations?
- You can implement a Laravel event listener for migration events yourself in an application service provider. Other options include running tests in CI after the migrate command, using database test traits, or calling artisan commands from your deployment scripts. This package mainly packages that listener pattern for reuse.
- Does it work with Laravel 8 or PHP 7.4?
- The supplied assessment describes 3.1.0 as aligned with Laravel 9, which requires PHP 8.0+ and updated Symfony components. It does not provide evidence that Laravel 8 or PHP 7.4 are supported by that release. If you must stay on older versions, verify Composer constraints or pin an earlier package version.
- How do I test that the migration event listener works?
- Write a Laravel feature test that dispatches or triggers a migration event and asserts your callback ran. Since the package listens to migration events, you can also verify behavior by running php artisan migrate in a test environment and inspecting the side effects. The supplied data does not include the package's own test matrix, so add your own integration coverage.
- What are the risks of upgrading to version 3.1.0?
- The assessment flags 3.1.0 as a Laravel 9 baseline shipped as a minor version, which can understate breakage. Risks include Composer dependency conflicts, PHP version mismatches, config or service-provider changes, migration failures, storage or Flysystem behavior changes, and insufficient test coverage. Treat it as a platform update, pilot it on one project, and keep rollback points.
Weaver
How can I help you explore Laravel packages today?