eds-block-testing

EDS block testing uses test.html scaffold files in your block directory. Create a test.html file using the provided template, integrate the EDS core script, apply the .block class for decoration, and run it on the development server with hot-reload enabled to validate block functionality before deployment.

A standard test.html file requires the EDS core script integration, block markup decorated with the .block class, and test scenarios that mimic production behavior. The template scaffolds different layouts, responsive states, and edge cases to ensure your block loads and renders correctly.

Yes. EDS block testing integrates with the development server to enable local testing with hot-reload capabilities. This workflow lets you iterate on block functionality, debug issues in real-time, and validate behavior before pushing to production.

Test different layouts, responsive behavior across breakpoints, and boundary conditions specific to your block's data inputs. The testing methodology helps identify gaps in block decoration, script loading, and production parity that manual debugging alone would miss.

EDS block testing follows Adobe Edge Delivery Services core patterns and integrates with standard development servers. You need the EDS core script and a local development environment; no additional proprietary tools are required beyond your standard block development setup.

The .block class is required for EDS core to recognize and load your block correctly. Testing with proper decoration ensures your block behaves identically in test and production environments, preventing runtime failures after deployment.