find-test-content

To find pages containing a specific AEM block, you can query the AEM query index and parse the HTML using jsdom. This reports all page URLs and identifies block variants to streamline development testing.

Yes, you need a running local development server with an accessible query index to search for AEM block content. The search queries this index to locate pages and uses jsdom to parse the returned HTML for block elements.

Yes, you can detect different variants of an AEM block across pages. The search identifies block elements and reports their associated CSS classes, allowing you to see which variants are currently implemented for comprehensive testing.

The best way to locate test cases for AEM block modifications is to search the query index for pages using that block. This discovers existing implementations and their variants, ensuring your changes are tested against real content.

No, this content discovery search requires jsdom as a dependency. It utilizes jsdom specifically for HTML parsing to accurately identify block elements and extract their associated CSS classes for variant detection.

You should search for existing content before modifying an AEM block to ensure comprehensive testing. Locating all pages and variants using the block prevents regressions by validating your changes across current implementations found in the query index.