Testing Blocks

Testing AEM Edge Delivery blocks involves unit testing with Vitest for core logic, browser testing with Playwright or Puppeteer for UI rendering, and linting for code quality. This Skill provides a comprehensive workflow covering block implementations, scripts (scripts.js, delayed.js, aem.js), and stylesheets to validate functionality before submitting pull requests.

Keeper tests are unit tests for critical business logic you maintain long-term; throwaway tests are browser tests for visual validation that verify a feature works once then can be discarded. This Skill guides you on which approach fits each scenario to balance testing value against implementation cost.

Yes. This Skill covers CI/linting integration and automated performance validation via GitHub checks. You can configure linting to enforce code quality standards and set up GitHub checks to validate performance metrics, ensuring all quality gates pass before merge.

This Skill provides guidance on structuring test content alongside your block implementations, scripts, and stylesheets. It covers best practices for organizing tests so they map clearly to the code they validate, supporting both unit and browser test workflows.

Not necessarily. This Skill teaches a pragmatic approach: use browser testing for UI/DOM validation and variant rendering, but rely on unit tests for core logic. The framework helps you decide which tool and testing method suits each type of code change.

This Skill covers automated performance validation integrated into GitHub checks, allowing you to measure and validate performance metrics for your blocks, scripts, and stylesheets. It ensures performance gates are met before code ships to production.