Testing Blocks

Automate validation of AEM Edge Delivery code changes with unit and browser tests.

Updated Mar 7, 2026
One-click install
npx skills add https://github.com/trieloff/trrrrdt --skill testing-blocks-trieloff
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Testing Blocks
Source: https://github.com/trieloff/trrrrdt/tree/main/.claude/skills/testing-blocks
Command: npx skills add https://github.com/trieloff/trrrrdt --skill testing-blocks-trieloff

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Validating code changes in AEM Edge Delivery projects can be error-prone without a structured testing approach. This guide provides a clear framework for unit testing, browser testing, linting, and performance checks to prevent regressions before PRs and deployments.

Core Features & Use Cases

  • Unit testing for utilities and logic to catch regressions early.
  • Browser testing with Playwright/Puppeteer to validate decorations, rendering, and interactions.
  • Linting and performance checks to ensure code quality and performance.

Quick Start

Install dependencies and run the full test workflow to validate your changes locally.

Frequently Asked Questions about Testing Blocks

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate code validation for AEM Edge Delivery projects?

Automating code validation in AEM Edge Delivery involves running unit tests, browser checks, and linting workflows. This framework applies Vitest and Playwright to validate block, script, and style changes before pull requests and deployments to prevent regressions.

What is the best way to run unit tests and browser checks for AEM blocks?

The best way to run unit and browser tests for AEM blocks is combining Vitest for utility logic and Playwright for rendering validation. This approach catches early regressions and verifies decorations and interactions during local development.

How do I set up Vitest and Playwright for AEM Edge Delivery testing?

Setting up Vitest and Playwright requires installing the necessary dependencies and executing the full test workflow. This validates block and script changes locally, ensuring unit tests, browser interactions, and linting pass before integration.

Do I need Vitest and Playwright to validate AEM block changes?

Vitest and Playwright are required to satisfy full validation requirements for AEM block changes. Vitest handles unit testing for logic regressions, while Playwright executes browser testing to validate decorations and user interactions.

Why does linting fail during pre-deploy checks for AEM Edge Delivery?

Linting fails during pre-deploy checks when code quality standards are not met in block, script, or style changes. Running the validation framework locally before pull requests identifies and resolves linting errors to ensure performance checks pass.