Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Repair Windows errors before they cause bigger problems3Fix the driver behind crashes, sound loss and screen glitchesSet up CI for an n98-magerun2 plugin in the plugin’s own repository: define the PHP and platform versions it supports, install dependencies from its Composer lockfile, and run the checks its own configuration defines. n98-magerun2 provides a module API and developer commands, but the official documentation reviewed here does not provide a ready-made CI workflow, PHPUnit command, or standard fixture for independent plugins. Treat the workflow below as a practical approach—not an official project recipe.
What CI needs to verify
n98-magerun2 is a Magento 2 command-line tool whose commands can be extended through a module API, as described in the project README. That makes a plugin’s CI responsibility distinct from building or testing n98-magerun2 itself: the plugin maintainer must check that their module’s code, declared dependencies, and supported environments work together.
As an Amazon Associate I earn from qualifying purchases.
The official development documentation lists module-development commands such as dev:module:create and dev:module:detect-composer-dependencies. It does not specify a third-party plugin CI workflow or a universal test command. The README’s composer install and ./build.sh steps are for building the core project, not a plugin’s CI job.
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Choose a matrix from your support claims
Start with the combinations your plugin actually claims to support, rather than testing every possible pairing of PHP, n98-magerun2, and Magento or Mage-OS. Include the minimum supported PHP version and a current supported version, then add tool or application versions when the plugin depends on their behavior. Each CI matrix row should represent a compatibility promise you are prepared to maintain.
#1 Best Overall
The core project’s compatibility guidance covers n98-magerun2, PHP, and platform combinations, but it is guidance for the core tool—not a guarantee that a particular plugin supports them all. The table below records version boundaries shown on that documentation page as displayed on October 4, 2026; check the live table before setting or updating a workflow because these boundaries can change.
| Compatibility point | Documented boundary | How to use it in plugin CI |
|---|---|---|
| PHP 8.1 | n98-magerun2 v9.5.1 is the last compatible version. | Include this pairing only if your plugin claims support for PHP 8.1 and that n98-magerun2 line. |
| PHP 8.4 and 8.5 | n98-magerun2 v9.0.0 or later is required. | Use a compatible core-tool version if testing these PHP versions, and confirm your plugin supports the pairing. |
| n98-magerun2 v10.0.0 | Raises the minimum PHP version to 8.2. | Do not pair v10.0.0 with a PHP version below its documented minimum. |
| Adobe Commerce/Magento OS 2.4.9+ and 2.4.8+ | n98-magerun2 v9.0.0 or later. | Keep the product and platform version explicit in the plugin’s own support claims; do not treat editions as interchangeable. |
| Mage-OS 1.2.x+ | n98-magerun2 v9.0.0 or later. | Represent Mage-OS separately where your plugin supports or depends on it. |
| Adobe Commerce/Magento OS 2.4.4 | n98-magerun2 v7.5.0 is the last compatible version. | Test this older pairing only if it remains within your plugin’s declared support. |
These are core-tool compatibility boundaries, not plugin support guarantees. The documentation says the tool is automatically tested against multiple PHP versions and runs on Linux distributions and macOS; that does not establish an operating-system matrix or test outcome for your plugin.
Build the workflow around the plugin repository
- Document support. Read the plugin’s
composer.jsonand any existing documentation. Record the PHP, n98-magerun2, and Magento or Mage-OS combinations the plugin intends to support, then compare relevant core-tool pairings with the official compatibility table. - Choose a focused matrix. Cover the minimum and a current supported PHP version, with additional tool or platform rows only where they represent a real support claim. Avoid a full Cartesian product if many combinations add cost without testing distinct behavior.
- Install the plugin’s dependencies. Use the dependency configuration committed in the plugin repository, including its Composer lockfile when present. Do not copy the core repository’s build steps as a substitute for installing or testing the plugin.
- Run the checks the plugin actually defines. Inspect Composer scripts and the test configuration before choosing a command. The official n98-magerun2 documentation does not establish a universal PHPUnit invocation, so do not assume one.
- Separate test types. Run fast checks that need no full Magento installation as a smaller, routine job. Add integration jobs requiring a real application only when the plugin’s behavior depends on it, and document the environment and setup that job needs.
- Run checks on changes. Configure the CI host to run the appropriate jobs for pull requests and pushes. Add secrets or external services only if the plugin genuinely needs them; their requirements cannot be inferred from the n98-magerun2 module API alone.
- Review compatibility periodically. Recheck the core compatibility table when changing supported versions, upgrading dependencies, or updating the workflow. Keep the relevant support documentation close to the matrix so maintainers can explain why each row exists.
Decide whether a test needs Magento installed
A module can have checks that validate code or isolated behavior without booting a commerce application, while other behavior may depend on Magento or Mage-OS classes, configuration, or runtime services. The right split depends on the plugin. Determine it from the code and existing tests rather than adding an assumed fixture or installation process: the official development documentation does not prescribe a standard third-party plugin fixture.
Quick Recap
Rank #4
- Unit or static checks: use the plugin’s configured tools and dependencies; keep these independent of a full application when the code permits.
- Integration checks: use an installed platform only where needed to verify behavior that isolated checks cannot cover. Record the supported platform version and any setup or service requirements.
Common CI mistakes to avoid
- Copying core build instructions:
composer installand./build.shin the README describe building n98-magerun2 itself, not a ready-made plugin test job. - Inventing a universal test command: PHPUnit and other checks depend on the plugin’s own Composer scripts and test configuration.
- Testing unsupported pairings: a core tool’s compatibility does not automatically mean the plugin supports the same combination.
- Combining distinct platform labels: distinguish Adobe Commerce, Magento Open Source, and Mage-OS in support claims where the plugin’s compatibility differs.
- Leaving a stale matrix in place: core compatibility changes by release, so validate version boundaries against the current official documentation.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
