Any agency maintaining custom Magento 2 modules across several client projects cannot avoid a private Composer repository. Instead of distributing modules manually via FTP or a zip file, a private Composer repository makes them installable through composer require, versioned through git tags and with full dependency resolution against magento/framework. This article shows how to build a solid distribution infrastructure, from the repositories configuration through a self hosted Satis instance to a secured CI pipeline.

Implement ArgumentInterface, move logic out of Block classes, inject it via Layout XML, unit test it, and use it to full effect in the Hyva Theme, explained in full.

Configurable products are the standard tool in Magento 2 for representing size, color or material as independent, stock-managed variations. Anyone who understands the data model built from catalog_product_super_attribute and catalog_product_super_link, generates variations programmatically instead of manually in the admin grid, and designs indexers and Full Page Cache for large combination counts avoids the typical performance traps that slow down configurable catalogs with 10,000 or more SKUs.

The builder pattern creates complex objects step by step. In Magento 2 it matters most for SearchCriteria, filters, sort orders and stable configuration objects for services.

Magento 2 · Tests

Unit Tests in Magento 2
fast and effective without bootstrap

Unit tests in Magento 2 feel heavy to many teams because they are built too close to the framework or too far away from real value. Good tests, by contrast, are small, fast and placed exactly where custom logic actually creates risk.

17 min read PHPUnit Magento 2.4.8

Table of Contents

1. 1. What makes a good Magento 2 unit test
2. 2. Why unit tests without bootstrap are faster
3. 3. Cutting your own logic so it is testable
4. 4. Mocking with restraint instead of mocking as an end in itself
5. 5. Where unit tests in Magento really pay off
6. 6. Typical mistakes
7. 7. Unit tests vs. integration tests
8. 8. Magento 2 support
9. 9. Summary
10. 10. FAQ

1. What makes a good Magento 2 unit test

A good Unit Tests Magento 2 approach checks your own logic in isolation and quickly. That sounds trivial, but in practice it is often missed. Either pure getters, framework configuration or trivial delegations get tested,

A misconfigured Magento 2 store view configuration often goes unnoticed for weeks, until a customer on the wrong domain sees the wrong price displayed. The scope hierarchy of default, website and store view decides which value actually wins, and anyone who has not internalized this order produces configuration errors that only show up in production.

Static tests in Magento 2 catch exactly the class of problems that neither PHPStan nor PHPUnit see: violations of the Magento Coding Standard, undeclared dependencies between modules, and legacy patterns quietly reintroduced into the codebase. Whoever takes the suite under dev/tests/static seriously prevents exactly the kind of structural failure that only becomes visible at the next major upgrade or when module load order changes.

Magento 2 · MSI

Understanding MSI properly
Custom Source and reservations

Multi Source Inventory solves a real problem in Magento 2, but in everyday practice it is often misunderstood. Anyone who mixes up sources, stocks and reservations quickly ends up building inventory logic that is either factually wrong or operationally unstable.

18 min read MSI Magento 2.4.8

Table of Contents

1. 1. What MSI actually models in Magento 2
2. 2. Creating and thinking about a Custom Source in Magento 2
3. 3. Understanding reservations in Magento 2
4. 4. Data flow between Source Items, Stocks and Salable Quantity
5. 5. Typical extension scenarios with MSI
6. 6. Common mistakes
7. 7. MSI versus classic single-stock thinking
8. 8. Magento 2 support
9. 9. Summary
10. 10. FAQ

1. What MSI actually models in Magento 2

MSI Magento 2 stands for Multi Source Inventory and, for the first time, cleanly separates physical sources, logical stocks and salable quantity. This matters because in real projects,

Magento 2 already ships with a working caching solution in the form of its built-in full page cache, yet many projects put Varnish in front of the shop anyway without checking whether the actual requirements call for it. This article compares both approaches based on traffic volume, hosting setup and team skills, and uses VCL examples, purge strategies and monitoring commands to show when the extra operational effort of Varnish really pays off.