skills.rest
Royincog
RoyincogCOMMUNITY
Explore all skills by this author →
GitHub

testing-blocks

Standardize pre-PR browser validation, linting, and test execution for AEM Edge Delivery projects.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Testing across AEM Edge Delivery projects often lacks a standardized, documented workflow, leading to PR delays due to missing browser validation and inconsistent linting. This skill provides a structured guide to perform browser validation, unit testing where applicable, and linting before merging.

Core Features & Use Cases

  • Provides a repeatable browser testing workflow (Playwright) to validate blocks, scripts, and styles in a real browser environment.
  • Documents linting, optional unit testing, and test execution steps to catch issues early.
  • Supports integration with building-blocks by describing outputs and evidence required, ensuring PR readiness.

Quick Start

Run linting and perform browser validation locally before opening a PR to ensure all checks pass.

Frequently Asked Questions about testing-blocks

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

FAQPage Schema
How do I set up pre-PR validation workflows for AEM Edge Delivery blocks?▼

Pre-PR validation for AEM Edge Delivery blocks is standardized by running linting, optional unit tests, and browser validation locally before merging. This workflow enforces documented steps and evidence collection to ensure PR readiness.

What is the best way to perform browser validation on AEM blocks before a pull request?▼

Browser validation on AEM blocks is best performed using Playwright to test scripts and styles in a real browser environment. This approach catches issues early and provides the documented evidence required for PR approval.

Does the building-blocks workflow require linting and unit testing with Vitest?▼

The building-blocks workflow requires linting and supports optional unit testing with Vitest to catch issues early. Running these checks ensures your blocks meet the acceptance criteria before opening a pull request.

How do I standardize browser testing across multiple AEM Edge Delivery projects?▼

Browser testing across AEM Edge Delivery projects is standardized by applying a repeatable Playwright workflow to validate blocks, scripts, and styles. This enforces consistent linting and documented evidence collection for every PR.

Can I use Playwright to validate styles and scripts for AEM blocks?▼

Playwright can validate styles and scripts for AEM blocks by executing repeatable browser testing workflows. This ensures your code functions correctly in a real browser environment before merging.

Why do my pull requests face delays when submitting AEM blocks?▼

Pull requests for AEM blocks face delays due to missing browser validation and inconsistent linting. Applying a standardized pre-PR workflow with documented steps and evidence collection resolves these merge blockers.

Related Skills

Explore More Software Engineering Skills→
initialyzeinitialyze

Testing Blocks

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

Official
Advanced
DevelonautDevelonaut
3

merge-pr

Verify CI checks, detect conflicts, and squash-merge approved pull requests.

Community
Advanced
valithedgevalithedge

testing-blocks

Automate linting, unit tests, and Playwright browser validation for AEM Edge Delivery code changes.

Community
Advanced
petenelsonpetenelson
87

10up-testing

Automate WordPress end-to-end testing workflows with PHPUnit, Jest, and Cypress for plugins and themes.

Community
Advanced