Testing Blocks

Testing AEM Edge Delivery projects involves unit testing logic-heavy utilities with vitest, browser testing for DOM validation with playwright, linting for code style, and running performance validation via GitHub checks before merging changes.

The best way to unit test AEM blocks is targeting logic-heavy utility functions with vitest, applying a value-versus-cost philosophy to prioritize tests that provide the most validation value relative to their maintenance cost.

Playwright is used for browser testing in AEM Edge Delivery to perform visual and DOM validation. This ensures that code changes render correctly and meet functional standards before being merged into the main branch.

Linting and performance checks are required before deploying AEM code to ensure code style consistency and validate performance. Running these checks via GitHub helps maintain robust code quality before changes are merged.

You should prioritize tests in your AEM testing workflow using a value-driven approach. Evaluate the maintenance cost of each test against the validation value it provides, focusing on logic-heavy utilities and critical visual DOM validation.