Testing

Magewire uses complementary checks rather than relying on browser tests alone:

• PHPUnit covers isolated PHP behavior such as the application container and registries.
• Playwright exercises Magewire in a running Magento storefront.
• The production-build matrix installs Magewire into supported Magento Open Source and Mage-OS versions and runs setup:di:compile.
• Static analysis and formatting workflows cover the PHP source separately.

Unit tests

From a Magewire source checkout with Composer dependencies installed:

phpunit --bootstrap vendor/autoload.php --do-not-cache-result tests/Unit

The repository workflow currently runs this suite on PHP 8.2. Application modules can use their own PHPUnit integration and mock component dependencies as normal Magento services.

Playwright

The browser suite requires a Magento installation with sample data and Magewire's Playwright fixtures enabled.

From the Magewire source checkout:

cd tests/Playwright
npm install

Create tests/Playwright/.env:

BASE_URL=https://local.test/
ENVIRONMENT=local
ACCOUNT_FIRSTNAME=Veronica
ACCOUNT_LASTNAME=Costello
ACCOUNT_EMAIL=roni_cost@example.com
ACCOUNT_PASSWORD=roni_cost3@example.com

Run the suite or open Playwright's interactive UI:

npm run test
npm run test:ui

Do not commit real customer credentials or a local .env file.

Compatibility matrix

Magewire 3.6's production workflow verifies these representative builds:

This matrix demonstrates tested combinations, not every theoretically installable permutation. Check the workflow in the tag you deploy.