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, in developer mode, and with Magewire's Playwright fixtures enabled. The fixture routes are served only outside production mode.

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.

Test an application component

A component needs one browser check in addition to its isolated PHP tests: the layout must bind it, its script must initialize, and its action must complete a request. The quickstart counter has a data-testid="magewire-counter" root so a Playwright test can stay independent of theme markup:

import { test, expect } from '@playwright/test'

test('counter updates without a page reload', async ({ page }) => {
    await page.goto('/')

    const counter = page.getByTestId('magewire-counter')
    await expect(counter).toContainText('Count: 0')
    await counter.getByRole('button', { name: 'Increase' }).click()
    await expect(counter).toContainText('Count: 1')
})

Run this against a Magento installation with your module and theme integration enabled. For an action that writes data, also test an unauthorized request and a browser-controlled ID or value; a successful button click does not prove the server-side guard.

Compatibility matrix

Magewire 3.7'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.