find-test-content

Locate pages containing a specified AEM block via query-index and jsdom.

1|6|Updated Feb 10, 2026
One-click install
npx skills add https://github.com/aemsites/summit-portal --skill find-test-content-aemsites
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: find-test-content
Source: https://github.com/aemsites/summit-portal/tree/main/skills/aem/edge-delivery-services/find-test-content
Command: npx skills add https://github.com/aemsites/summit-portal --skill find-test-content-aemsites

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires jsdom, and includes scripts (resource) components.

What problem does it solve?

Quickly locating existing pages that use a particular AEM block can be slow and error-prone when done manually; this Skill automates discovery so developers can identify suitable test pages and variants during development.

Core Features & Use Cases

  • Queries the site's query-index with pagination to gather page paths.
  • Fetches and parses each page's HTML using jsdom to detect block instances and extract CSS-class-based variants.
  • Use case: When updating a block's styling or behavior, run this Skill to list pages with instances and variant coverage for targeted testing.

Quick Start

Run the included find-block-content script with the block name and optional host to list pages, instance counts, and variants for testing.

Frequently Asked Questions about find-test-content

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

FAQPage Schema
How do I find all pages containing a specific AEM block in Edge Delivery Services?

Locating specific AEM block instances across an Edge Delivery Services site involves querying the query-index with pagination and parsing page HTML with jsdom to report matching URLs and instance counts.

How can I detect CSS-class variants of AEM blocks during local development?

Detecting CSS-class variants of AEM blocks requires fetching and parsing page HTML using jsdom, which extracts variant information to help developers identify suitable test pages during local development or preview environments.

Does this block discovery approach work with paginated query-index retrieval?

Yes, this block discovery approach handles paginated query-index retrieval, automatically fetching and parsing each page's HTML to detect block instances and extract CSS-class-based variants across large AEM Edge Delivery Services sites.

What is the best way to identify test pages for AEM block modifications?

The best way to identify test pages for AEM block modifications is to automate discovery by scanning the query-index and parsing HTML to list pages containing the block, instance counts, and variant coverage for targeted testing.

Do I need jsdom to extract block instances and variants from AEM pages?

Yes, jsdom is required to fetch and parse each page's HTML, enabling the detection of block instances and the extraction of CSS-class-based variants across the queried AEM Edge Delivery Services content.