Testing Blocks FAQs

Question 1

When should I use this Claude Code skill?

Accepted Answer

You should use this skill after implementing or modifying blocks, scripts, or styles. It is specifically designed to be run before opening a pull request to ensure all functionality, performance, and linting requirements are met.

Question 2

Does this skill integrate with other Claude Code capabilities?

Accepted Answer

Yes, it is tightly integrated. It can be automatically invoked by the 'building-blocks' skill and utilizes test content patterns established during 'content-driven-development' (CDD) to streamline the validation process.

Question 3

What does the Testing Blocks skill do?

Accepted Answer

This skill guides developers through validating code changes in AEM Edge Delivery Services projects. it uses a 'value-versus-cost' philosophy to balance durable unit tests for logic with efficient browser-based validation for UI components.

Question 4

How does this skill improve my development workflow?

Accepted Answer

It automates the creation of testing checklists, provides quick-start templates for Playwright and Vitest, and ensures that you don't waste time maintaining low-value UI tests while still capturing essential visual validation through screenshots.

Question 5

What capabilities does it provide for browser testing?

Accepted Answer

The skill provides workflows for browser automation using Playwright or Puppeteer. It helps set up temporary test content, validates block decoration logic, captures responsive UI screenshots across different viewports, and manages local development server configurations.

Testing Blocks

Testing Blocks

主要功能

使用场景

主要功能

使用场景