testing-blocks

To test code changes for AEM Edge Delivery projects, run a structured workflow that includes linting, mandatory browser validation, and optional unit tests to ensure code quality and functional correctness before submitting a pull request.

Validating modified blocks and scripts requires running linters for style checks, performing manual browser validation across viewports for visual accuracy, and executing available unit tests to confirm logic correctness.

Yes, browser validation is mandatory for every code modification in AEM Edge Delivery. You must test changes in a real browser environment and provide proof of validation to ensure visual and functional accuracy.

Playwright is utilized within the testing workflow for AEM Edge Delivery projects, alongside linting and browser validation, to guide the creation and execution of tests for logic-heavy block modifications.

The best way to run linting checks on AEM components is to execute the `npm run lint` command, which automatically checks your code for style and quality issues before proceeding to browser validation.

You should not skip unit tests when modifying logic-heavy code in AEM blocks. While optional, unit testing is highly recommended to confirm that existing logic passes and the change is robust before deployment.