Testing Blocks FAQs

Question 1

What does the Testing Blocks skill do?

Accepted Answer

This skill provides a structured framework for Claude Code to validate changes in AEM Edge Delivery projects. It balances automated unit testing for complex logic with browser-based UI validation for DOM transformations, ensuring high-quality code without unnecessary maintenance overhead.

Question 2

When should I use this skill?

Accepted Answer

You should invoke this skill after implementing or modifying AEM blocks, core scripts, or styles. It is designed to be the final step in your local development workflow before pushing code or opening a pull request.

Question 3

What is the 'Value vs. Cost' testing philosophy?

Accepted Answer

It is a pragmatic approach where you create 'keeper' tests for logic-heavy utilities and API integrations that provide long-term value, while using 'throwaway' browser tests for UI elements that change frequently, reducing the burden of maintaining brittle tests.

Question 4

What testing tools does this skill support?

Accepted Answer

The skill provides guidance and scripts for Vitest (unit testing), Playwright or Puppeteer (browser testing), and the AEM CLI for local development and performance validation through GitHub checks.

Question 5

How does this skill improve my development workflow?

Accepted Answer

It automates repetitive tasks like linting and performance checks while providing specific patterns for unit and browser testing. By integrating with the 'building-blocks' skill, it ensures that every new feature is verified for responsive design and cross-device functionality automatically.

Testing Blocks

Testing Blocks

Key Features

Use Cases

Key Features

Use Cases