testing-blocks

Validate AEM Edge Delivery code changes with linting, unit tests, and browser testing.

Updated Feb 20, 2026
One-click install
npx skills add https://github.com/mhaack/sewjaland --skill testing-blocks-mhaack
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: testing-blocks
Source: https://github.com/mhaack/sewjaland/tree/main/.claude/skills/testing-blocks
Command: npx skills add https://github.com/mhaack/sewjaland --skill testing-blocks-mhaack

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The skill helps teams verify code changes to AEM Edge Delivery projects by ensuring blocks, scripts, and styles work correctly in a real browser before merging.

Core Features & Use Cases

  • Browser validation is mandatory and emphasises real-browser testing to confirm functionality.
  • Linting and unit testing guidance for utilities and logic accompany browser tests.
  • Step-by-step workflows and best practices to validate changes prior to PRs.

Quick Start

Run linting with npm run lint and then execute the recommended browser validation workflow against your test content.

Frequently Asked Questions about testing-blocks

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

FAQPage Schema
How do I validate AEM Edge Delivery code changes in a real browser before merging?

You validate AEM Edge Delivery changes by running linting checks and executing browser-enabled testing workflows against blocks, styles, and scripts to confirm functionality before opening a PR.

What is the best way to run browser tests for code blocks before a pull request?

The best way to test code blocks before a PR is enforcing mandatory real-browser validation, running linting via npm run lint, and applying a step-by-step browser testing workflow to verify edits.

Does browser testing replace unit testing for utility logic in my project?

Browser testing does not replace unit testing; it complements it by validating end-to-end functionality, while unit testing covers individual utility logic and linting enforces code quality standards.

Can I use Playwright for end-to-end browser validation of scripts and styles?

Yes, Playwright supports end-to-end browser validation by executing real-browser tests to confirm that your edited scripts, styles, and blocks render and function correctly across the application.

Why do I need real-browser testing for code block modifications?

Real-browser testing is mandatory because it confirms that code block modifications work correctly in actual rendering environments, catching visual and functional issues that linting and unit tests miss.

What are the limitations of relying only on linting without browser validation?

Relying only on linting without browser validation misses runtime errors and visual regressions, because linting checks syntax and style standards but cannot confirm actual functionality in a rendering environment.