Writing integration tests for AEM (part 3) | AEM Community Blog Seeding

Avatar

Avatar

kautuk_sahni

Community Manager

Total Posts

5.7K

Likes

1.0K

Correct Reply

1.1K

Avatar

kautuk_sahni

Community Manager

Total Posts

5.7K

Likes

1.0K

Correct Reply

1.1K
kautuk_sahni
Community Manager

04-01-2021

BlogImage.jpg

Writing integration tests for AEM (part 3) by Jörg Hoh

Abstract

In the last post on writing integration tests with AEM I quickly walked you through a simple test case for authoring instances, but I didn’t provide much context, what is going on exactly, and how it will be executed in Cloud Manager. That’s what I want to talk about today.

As we have seen, some relevant parameters for integration tests are provided are provided externally, most notable the URLs for the environment plus credentials.

Here you can see defaults, but you can simply override them by providing the exact values with the command line, as you already did in the previous post with overriding the URL of the authoring instance. The POM just introduces another indirection via properties which is technically not really necessary.

CloudManager works the same way: It invokes the maven-failsafe-plugin to execute the integration tests and provides overrides these default values with the correct data specific for that environment (including the admin credentials).

In detail, the urls are configured like this:

sling.it.instance.url.1 = https://author-pxxxxx-eyyyyy.adobeaemcloud.net
sling.it.instance.url.2 = https://publish-pxxxxx-eyyyyy.adobeaemcloud.net
This means that your tests acess the loadbalanced author cluster and the loadbalanced publish farm (including dispatcher!).

Read Full Blog

Writing integration tests for AEM (part 3)

Q&A

Please use this thread to ask the related questions.

AEM AEMEBlogSeeding Experience Manager