Testing Blocks

Unit testing for AEM Edge Delivery blocks uses Vitest with jsdom environment. Place test files alongside source code, write tests for logic-heavy utilities and data processing, and configure npm scripts to run tests before PR submission to catch regressions early.

Yes, Playwright enables browser testing of block decoration and responsive design. Run visual and functional validation tests to capture screenshots across devices, ensuring your blocks render correctly before pushing code through CI/CD checks.

Before PR submission, run unit tests with Vitest, execute browser tests with Playwright to validate rendering and interactions, and pass all linting and performance checks. This workflow ensures code quality and prevents regressions across blocks, scripts, and styles.

Linting and performance validation run as automated GitHub checks in your CI/CD pipeline. These checks maintain code standards and catch issues before review, working alongside unit and browser tests to streamline the path from development to merged code.

Keeper tests validate core functionality and prevent regressions; throwaway tests explore behavior during development but aren't retained. Testing Blocks guidance helps classify which tests to maintain, balancing comprehensive coverage with practical maintenance costs.

Yes, Testing Blocks covers testing guidance that integrates with content-driven development in AEM Edge Delivery. It specifies test file placement, naming conventions, and the end-to-end workflow from implementation through review for content-driven projects.