skills.rest
juricamigac-from-hr
juricamigac-from-hrOFFICIAL
Explore all skills by this author →
GitHub

testing-blocks

Validate AEM Edge Delivery code changes with browser-based checks and linting.

Updated Apr 5, 2026
Search Tags:#testing#linting#playwright#unit-testing#blocks#browser-testing#aem-edge-delivery
One-click install
npx skills add https://github.com/juricamigac-from-hr/svemojestrane --skill testing-blocks-juricamigac-from-hr
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: testing-blocks
Source: https://github.com/juricamigac-from-hr/svemojestrane/tree/main/.agents/skills/testing-blocks
Command: npx skills add https://github.com/juricamigac-from-hr/svemojestrane --skill testing-blocks-juricamigac-from-hr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Testing code changes in AEM Edge Delivery projects can be time-consuming and error-prone without a structured browser-validation workflow, linting, and test guidance.

Core Features & Use Cases

  • Provides a repeatable framework for linting, browser validation, and testing of blocks, scripts, and styles.
  • Guides how to validate changes across environments and ensures consistency before PRs.
  • Supports integration with existing testing workflows and suggests steps for validating core utilities and logic.

Quick Start

Run browser validation on your latest changes before opening a PR.

Frequently Asked Questions about testing-blocks

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

FAQPage Schema
How do I run browser tests for AEM Edge Delivery blocks before a PR?▼

Run browser validation on modified blocks, scripts, or styles using the provided framework to ensure changes pass linting and behavior checks before PR submission across local and CI environments.

What is the best way to validate code changes in AEM Edge Delivery projects?▼

Validating AEM Edge Delivery changes requires browser-based validation and structured test practices, applying specifically when blocks, scripts, styles, or configuration changes impact behavior.

Do I need unit tests for browser validation in AEM Edge Delivery?▼

Unit tests are optional for browser validation in AEM Edge Delivery, but the framework supports them alongside mandatory linting and browser testing to validate core utilities and logic.

Does this testing framework work with Playwright for AEM blocks?▼

Yes, the framework supports Playwright for browser testing, guiding how to validate AEM Edge Delivery blocks and scripts across local and CI environments before opening a PR.

Why does my AEM Edge Delivery configuration change need browser testing?▼

Configuration changes impact behavior, so browser testing enforces structured validation and linting to ensure your AEM Edge Delivery project remains consistent and error-free before PR submission.

Related Skills

Explore More Software Engineering Skills→
thojavathojava

testing-blocks

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

Community
Intermediate
ddttomddttom
7

Testing Blocks

Validate AEM Edge Delivery code changes with unit, browser, lint, and performance tests.

Community
Intermediate
adobe-summit2026-l613adobe-summit2026-l613

testing-blocks

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

Official
Intermediate
initialyzeinitialyze

Testing Blocks

Validate code changes in AEM Edge Delivery projects with Vitest and Playwright.

Official
Advanced