testing-blocks

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

Updated Mar 12, 2026
One-click install
npx skills add https://github.com/adobe-summit2026-l613/las-vegas-events --skill testing-blocks-adobe-summit2026-l613
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: testing-blocks
Source: https://github.com/adobe-summit2026-l613/las-vegas-events/tree/main/.skills/testing-blocks
Command: npx skills add https://github.com/adobe-summit2026-l613/las-vegas-events --skill testing-blocks-adobe-summit2026-l613

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Guides developers to validate code changes in AEM Edge Delivery projects by performing browser tests, lint checks, and unit tests before submitting a pull request.

Core Features & Use Cases

  • Comprehensive testing workflow guidance for blocks, scripts, and styles.
  • Mandatory browser validation to catch UI and interaction issues.
  • Linting and unit testing guidance to maintain code quality before PRs.
  • Integration with Building Blocks workflow for end-to-end validation.

Quick Start

Run lint, perform browser validation, then run tests before creating 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 validate code changes in AEM Edge Delivery projects before creating a PR?

To validate code changes in AEM Edge Delivery projects, run linting checks, perform mandatory browser validation using Playwright, and execute unit tests before submitting your pull request. This workflow ensures blocks, scripts, and styles function correctly.

What is the process for running browser tests on modified blocks and styles?

Browser testing on modified blocks and styles involves executing Playwright browser validation to catch UI and interaction issues. This process is mandatory and integrates with the Building Blocks workflow to verify visual and functional correctness before PR submission.

When do I need to run Playwright browser validation in the Building Blocks workflow?

You need to run Playwright browser validation whenever blocks, scripts, or styles are modified in AEM Edge Delivery projects. It is a mandatory step in the Building Blocks workflow to prevent UI and interaction issues from reaching production.

Does unit testing replace browser validation for AEM Edge Delivery scripts?

Unit testing does not replace browser validation for AEM Edge Delivery scripts. Unit testing provides code quality guidance, while mandatory Playwright browser validation catches actual UI and interaction issues. Both are required before creating a PR.

What's the best way to ensure linting and unit-test coverage for AEM Edge Delivery code?

The best way to ensure linting and unit-test coverage is to follow the integrated testing workflow: run lint checks first, perform browser validation with Playwright, then execute unit tests before submitting your pull request for AEM Edge Delivery changes.