AEM UI testing using Selenium via Cloud manager in AEM as a Cloud Service | Community
Skip to main content
V
VidyaGa1
December 17, 2024
Solved

AEM UI testing using Selenium via Cloud manager in AEM as a Cloud Service

  • December 17, 2024
  • 2 replies
  • 926 views

Hi Everyone,

 

I am new to Selenium UI testing using cloud manager in AEM. We have a new requirement wherein we would like to have the UI testing integrated as part of the cloud manager pipelines during deployment.

 

I went through the following documentations:

https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/implementing/using-cloud-manager/test-results/functional-testing/ui-testing#selenium-specific-details

 

aem-test-samples/ui-selenium-webdriver at aem-cloud · adobe/aem-test-samples · GitHub

 

But unable to understand how to integrate this with docker since I am unable to start the testing framework after following the above steps.

 

Is there any video tutorial or samples to help me understand the same and configure.

Can you please share any sample test cases for writing Selenium scripts using locators and testNG ?

Observed that the sample provided in github is limited to only the authoring interface UI.

Share if any use cases where we have used AEM UI tests using Selenium for End sites testing?

 

Thanks in Advance for your inputs. Appreciate your help.

@arunpatidar @divanshug @estebanbustamante @asutosh_jena_ @hrishikeshkagne @mukeshyadav_ @albinis1 @pulkitvashisth @kautuk_sahni 

 

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by EstebanBustamante

Hi,

 

The current preference is to use Cypress; however, you can still use Selenium if you need or want to. One of the older versions of the AEM archetype used Selenium as the default E2E framework. This is the commit that introduced cypress as the preferred framework: https://github.com/adobe/aem-project-archetype/commit/dd01179483134cae121558ef45e407cc1e2a649c. I would suggest downloading the archetype <=43 and running it locally. This will provide you with a fully working example of Selenium and E2E tests.

 

Hope this helps!

2 replies

EstebanBustamante
Community Advisor and Adobe Champion
EstebanBustamanteCommunity Advisor and Adobe ChampionAccepted solution
Community Advisor and Adobe Champion
December 23, 2024

Hi,

 

The current preference is to use Cypress; however, you can still use Selenium if you need or want to. One of the older versions of the AEM archetype used Selenium as the default E2E framework. This is the commit that introduced cypress as the preferred framework: https://github.com/adobe/aem-project-archetype/commit/dd01179483134cae121558ef45e407cc1e2a649c. I would suggest downloading the archetype <=43 and running it locally. This will provide you with a fully working example of Selenium and E2E tests.

 

Hope this helps!

Esteban Bustamante
    kautuk_sahni
    Community Manager
    kautuk_sahniCommunity Manager
    Community Manager
    January 7, 2025

    @vidyaga1 Did you find the suggestion helpful? Please let us know if you require more information. Otherwise, please mark the answer as correct for posterity. If you've discovered a solution yourself, we would appreciate it if you could share it with the community. Thank you!

    Kautuk Sahni
    Terms & ConditionsAccessibility statement

    Loading footer...