Test Automation on AEMaaCS (part 1)

[#1]

Test Automation on AEMaaCS (part 1)

by @daniel-strmecki

Introduction

AEM as a Cloud Service (AEMaaCS) shifts Adobe Experience Manager from a release-based model to a continuously delivered, cloud-native platform. Manual testing simply can't keep up with the pace of deployments, so test automation is now even more important to ensure quality, performance, and stability. Therefore, the move from on-prem AEM to AEMaaCS also demands a shift in testing strategy.An important consideration is that Adobe-developed code is continuously updated and merged with customer code, which needs to keep up with it in every release. This shared responsibility model increases the risk of unintended side effects or regressions, making automated regression testing even more essential.In this post, we'll explore different test types recommended for use on AEMaaCS projects. In part one, we'll examine unit, user interface (UI), and frontend vs backend performance testing. Then, in part two, we'll demonstrate how to automate test execution and reporting.

Key points

A solid testing strategy is essential for any AEMaaCS project, where rapid, automatic updates and shared code delivery require constant validation. Four key types of tests form the foundation of this strategy:

1. Unit Tests are the first line of defense, ensuring that business logic, Sling Models, and OSGi services work correctly in isolation. Developers should test at least the happy paths, use AEM Mocks instead of manually mocking everything, and keep test code clean and reusable. While Adobe’s SonarQube requires only 50% test coverage, aiming for 80% or more leads to better reliability and confidence during frequent deployments.

2. UI Tests safeguard both the authoring experience and end-user interface. These tests ensure components render as expected and dialogs behave correctly. To optimize UI testing, each component should be tested in isolation on dedicated pages across environments. Proper cleanup after tests is critical for reusability. Automated UI tests also help catch visual regressions and usability issues before they reach production.

3. Lighthouse Tests focus on frontend performance, SEO, and accessibility. Integrating Lighthouse testing early in the project lifecycle helps maintain high standards across all environments. Pages should be tested in isolation with realistic, content-rich scenarios. Setting performance budgets and failing builds on regressions keeps the user experience consistently strong.

4. Performance Tests validate that the backend can handle real-world usage, including traffic spikes and heavy data loads. These tests should target custom APIs and services, not Adobe’s out-of-the-box features. Running performance tests on the staging environment, which mirrors production scaling, ensures more accurate results. Ideally, performance metrics should feed into observability tools to correlate slowdowns with specific changes.

Automated testing in AEMaaCS is not a luxury; it's a necessity. With Adobe pushing frequent updates, relying on manual QA is no longer viable. Teams that build automation into their workflow from the start gain faster feedback, fewer regressions, and the ability to adapt quickly to platform changes. Testing needs be treated as a continuous quality guardrail that supports innovation without compromising stability.

Full Article

Read the full article on https://meticulous.digital/blog/f/test-automation-on-aemaacs-part-1 to find out more.

Q&A

Please use this thread to ask questions relating to this article