skills.rest
easingthemes
easingthemesCOMMUNITY
Explore all skills by this author →
Website𝕏@draganfillGitHub

aem-qa

Validate AEM stories with end-to-end QA checks across backend content and frontend rendering.

6|3|Updated Mar 21, 2026
Search Tags:#automation#qa#rendering#aem#chrome-devtools#bug-triage#mcp-api
One-click install
npx skills add https://github.com/easingthemes/dx-aem-flow --skill aem-qa
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: aem-qa
Source: https://github.com/easingthemes/dx-aem-flow/tree/main/plugins/dx-aem/skills/aem-qa
Command: npx skills add https://github.com/easingthemes/dx-aem-flow --skill aem-qa

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Validates AEM stories by performing end-to-end QA checks across backend content and frontend rendering to ensure acceptance criteria are met.

Core Features & Use Cases

  • BE verification checks JCR properties and component registrations using MCP API.
  • FE verification captures screenshots and validates rendering on author and publisher environments.
  • Workflow readiness requires AEM running locally and after deployment to enable autonomous QA.

Quick Start

Run the QA agent against your deployed AEM story to verify dialog fields, rendering, and bug creation.

Frequently Asked Questions about aem-qa

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

FAQPage Schema
How do I automate AEM QA across author and publisher instances?▼

Automate AEM QA by running end-to-end checks that validate backend JCR properties and frontend rendering across author and publisher environments to ensure story acceptance criteria are met.

What does end-to-end AEM story validation involve?▼

AEM story validation verifies backend component registrations and JCR properties using MCP API, while capturing screenshots and validating frontend rendering on author and publisher instances.

Do I need a locally deployed AEM instance to run automated QA checks?▼

Yes, automated AEM QA requires a locally deployed AEM instance running with access to author and optional publisher instances to verify dialogs, component registration, and page rendering.

Can I use Chrome DevTools to validate AEM frontend rendering?▼

Yes, the QA workflow uses Chrome DevTools checks to capture screenshots and validate frontend rendering on AEM author and publisher environments during the verification process.

How do I generate bug tickets from failed AEM acceptance criteria?▼

Generate bug tickets by running the QA agent against your deployed AEM story; it automatically creates bug tickets according to plan when dialog fields, rendering, or registration checks fail.

What's the best way to verify AEM component registration and dialog fields?▼

Verify AEM component registration and dialog fields by applying the QA workflow that uses the AEM MCP API to check backend JCR properties and validate component setup locally and post-deployment.

Related Skills

Explore More Software Engineering Skills→
adobeadobe

Workflow Launchers Skill — AEM as a Cloud Service

Configure and deploy AEM Cloud Service Workflow Launchers for JCR events.

Official
Advanced
petrkindlmannpetrkindlmann
64

ai-bug-triage

Classify CI failures and draft tickets using fingerprinting and LLM analysis.

Community
Advanced
easingthemeseasingthemes
6

aem-fe-verify

Screenshot AEM components in wcmmode=disabled and compare against Figma references.

Community
Advanced
easingthemeseasingthemes
6

aem-doc-gen

Automate AEM demo documentation generation with dialog captures and previews.

Community
Advanced