testing-blocks

Name: testing-blocks
Availability: InStock
Author: thojava

Guide linting, unit testing, and browser validation for AEM Edge Delivery code changes.

Updated Apr 8, 2026

Search Tags:#testing #qa #playwright #lint #browser-testing #aem-edge-delivery #block-testing

Ready to run

npx skills add https://github.com/thojava/baco --skill testing-blocks-thojava

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: testing-blocks
Source: https://github.com/thojava/baco/tree/main/.skills/testing-blocks
Command: npx skills add https://github.com/thojava/baco --skill testing-blocks-thojava

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill guides teams through thorough testing of code changes in AEM Edge Delivery projects, covering blocks, scripts, and styles, and emphasizes validating changes before PRs through linting, unit tests, and browser validation.

Core Features & Use Cases

Guidance for linting, unit testing, and browser validation to catch issues early.
Step-by-step workflows for testing blocks, scripts, and styles across environments.
Real-world use: verify changes to blocks and related assets before merging code.

Quick Start

Run npm run lint, perform browser validation in a real browser, and run the existing tests before opening a pull request.

Frequently Asked Questions about testing-blocks

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

FAQPage Schema

How do I test blocks in AEM Edge Delivery projects before opening a pull request?▼

To test blocks in AEM Edge Delivery projects, run npm run lint, execute existing unit tests, and perform browser validation in a real browser before opening a pull request. This ensures code changes to blocks, scripts, and styles pass browser-based validation.

What is the best way to validate changes to scripts and styles in AEM Edge Delivery?▼

The best way to validate changes to scripts and styles in AEM Edge Delivery is through a combination of linting, unit testing, and real browser validation. This workflow catches issues early and ensures compliance with browser-based validation practices before merging code.

Do I need Playwright to perform browser testing for AEM Edge Delivery blocks?▼

Browser testing is mandatory for validating AEM Edge Delivery blocks, and Playwright is supported as a browser-testing framework. You must verify changes in a real browser environment to ensure compliance with validation practices before merging.

Can I use this workflow to verify changes to blocks and related assets across environments?▼

Yes, this workflow provides step-by-step guidance for testing blocks, scripts, and styles across environments. It ensures thorough validation of blocks and related assets through linting, unit tests, and browser validation before merging code changes.

Why does browser validation fail even after passing lint and unit tests?▼

Browser validation can fail after lint and unit tests pass because browser testing checks real-world rendering and interaction behavior that static analysis and unit tests do not cover. Mandatory browser validation ensures blocks, scripts, and styles function correctly in actual browser environments.

What are the limitations of relying only on linting for AEM Edge Delivery block testing?▼

Relying only on linting for AEM Edge Delivery block testing misses runtime and rendering issues. Linting checks code style and static errors, but mandatory browser validation and unit tests are required to verify actual block behavior, script execution, and style application before pull requests.