Testing Blocks

What problem does it solve?

Managing the end-to-end testing workflow for AEM Edge Delivery projects can be error-prone and time-consuming if teams rely on ad-hoc checks. This skill consolidates unit testing, browser testing, linting, and performance validation into a repeatable process that guards PR quality.

Core Features & Use Cases

• Keeper tests for logic-heavy utilities and data processing to prevent regressions.
• Browser testing patterns for block decoration, rendering, and user interactions using console-tested scenarios.
• Guidance on when to use unit vs browser tests and how to structure test artifacts and PR checks.
• Integrated linting and performance checks to ensure code quality before PRs.

Quick Start

Execute the recommended testing workflow locally: write keeper unit tests for core utilities, add browser tests for rendering, run lint, and validate all checks before opening a PR.