skills.rest
ComwrapUkReply
ComwrapUkReplyCOMMUNITY
Explore all skills by this author →
GitHub

Testing Blocks

Automate unit, browser, lint, and performance validation for AEM Edge Delivery projects.

Updated Sep 12, 2025
Search Tags:#vitest#testing#linting#playwright#unit-testing#ci#browser-testing
One-click install
npx skills add https://github.com/ComwrapUkReply/ue-multitenant-root --skill testing-blocks-comwrapukreply
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Testing Blocks
Source: https://github.com/ComwrapUkReply/ue-multitenant-root/tree/main/.claude/skills/testing-blocks
Command: npx skills add https://github.com/ComwrapUkReply/ue-multitenant-root --skill testing-blocks-comwrapukreply

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Managing the end-to-end testing workflow for AEM Edge Delivery projects can be error-prone and time-consuming if teams rely on ad-hoc checks. This skill consolidates unit testing, browser testing, linting, and performance validation into a repeatable process that guards PR quality.

Core Features & Use Cases

  • Keeper tests for logic-heavy utilities and data processing to prevent regressions.
  • Browser testing patterns for block decoration, rendering, and user interactions using console-tested scenarios.
  • Guidance on when to use unit vs browser tests and how to structure test artifacts and PR checks.
  • Integrated linting and performance checks to ensure code quality before PRs.

Quick Start

Execute the recommended testing workflow locally: write keeper unit tests for core utilities, add browser tests for rendering, run lint, and validate all checks 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 automate testing for AEM Edge Delivery blocks and pull requests?▼

Automate AEM Edge Delivery testing by applying a cohesive workflow of unit tests, browser tests, linting, and performance checks to validate code changes before opening pull requests.

When should I use unit testing versus browser testing for block rendering?▼

Use unit testing for logic-heavy utilities and data processing to prevent regressions, and apply browser testing for validating block decoration, rendering, and user interactions.

Does this testing workflow integrate linting and performance validation into CI checks?▼

Yes, the workflow integrates linting and performance checks alongside unit and browser tests to ensure code quality and provide reliable, repeatable pull request checks.

What's the best way to structure vitest and playwright tests for AEM projects?▼

Structure tests by creating keeper unit tests for core utilities and organizing browser tests for console-tested rendering scenarios, ensuring artifacts and PR checks are maintainable.

Why do I need guardrails for my AEM Edge Delivery testing workflow?▼

Guardrails specify the structure for repeatable, maintainable tests, preventing error-prone ad-hoc checks and ensuring reliable validation across blocks, scripts, and styles.

Related Skills

Explore More Software Engineering Skills→
initialyzeinitialyze

Testing Blocks

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

Official
Advanced
TalonT-OrgTalonT-Org
5

merge-pr

Merge GitHub pull requests into the integration branch with conflict reports.

Official
Advanced
veilkeyveilkey
7

rust-ci

Automate Rust CI build, test, lint, format, and security checks.

Official
Intermediate
hkcm91hkcm91

testing-widgets

Test StickerNest widgets with Playwright E2E and Vitest unit tests.

Community
Intermediate