testing-blocks

To test blocks in AEM Edge Delivery projects, run npm run lint, execute existing unit tests, and perform browser validation in a real browser before opening a pull request. This ensures code changes to blocks, scripts, and styles pass browser-based validation.

The best way to validate changes to scripts and styles in AEM Edge Delivery is through a combination of linting, unit testing, and real browser validation. This workflow catches issues early and ensures compliance with browser-based validation practices before merging code.

Browser testing is mandatory for validating AEM Edge Delivery blocks, and Playwright is supported as a browser-testing framework. You must verify changes in a real browser environment to ensure compliance with validation practices before merging.

Yes, this workflow provides step-by-step guidance for testing blocks, scripts, and styles across environments. It ensures thorough validation of blocks and related assets through linting, unit tests, and browser validation before merging code changes.

Browser validation can fail after lint and unit tests pass because browser testing checks real-world rendering and interaction behavior that static analysis and unit tests do not cover. Mandatory browser validation ensures blocks, scripts, and styles function correctly in actual browser environments.

Relying only on linting for AEM Edge Delivery block testing misses runtime and rendering issues. Linting checks code style and static errors, but mandatory browser validation and unit tests are required to verify actual block behavior, script execution, and style application before pull requests.