Testing Blocks

Testing blocks in AEM Edge Delivery requires running unit tests for utilities, browser tests with Playwright to validate block decoration and responsiveness, linting checks, and performance validation. This comprehensive approach ensures code quality and stability before review.

Keeper tests are maintainable unit tests for logic-heavy utilities and data processing that provide lasting value. Throwaway browser tests with Playwright validate block appearance and responsive design without being part of the permanent test suite.

Yes, Playwright is the recommended tool for browser testing in AEM Edge Delivery projects. It validates block decoration, visual appearance, and responsive behavior as part of the pre-PR testing strategy.

Testing blocks requires Vitest for unit testing, Playwright for browser automation, jsdom for DOM simulation, and coverage tools like @vitest/coverage-v8. The Testing Blocks guide specifies required workflows, file organization, and verification steps.

Linting ensures code quality standards are met, while performance validation integrates with GitHub checks for automated verification. Both are part of the comprehensive testing strategy before submitting changes for review.

The Testing Blocks guide offers troubleshooting solutions for common testing failures, linting issues, and CI/CD check failures. Review the specific error, validate your test implementation against best practices, and ensure file organization matches required structures.