JUnit Test Cases for Sling Models based on Delegation Pattern

[amirk63597623]

I am trying to write jUnit test cases for custom teaser component which extends the core Teaser component using the Delegation Pattern for Sling Models using "@Self @Via(type=ResourceSuperType.class)" as specified here: https://github.com/adobe/aem-core-wcm-components/wiki/Delegation-Pattern-for-Sling-Models
When I try to set the context (io.wcm.testing.mock.aem.junit5.AemContext) and adapt the context's request (I've tried resource as well) to the model I have created (like the "PageHeadline" from the example), I am getting a NullPointerException.

I am using AEM 6.5.2.0 and trying to run test cases in JUnit 5

[amirk63597623]

Hello! Have you resolved the issue? I mean the case when we use one of the core component Teaser's methods? I also have a NullPointer.

[gomatis80521865 · Accepted solution]

Hi,

You need to use one more adaptable to adapt Teaser Component 

e.g.

@Model(adaptables = SlingHttpServletRequest.class, adapters = {Teaser.class, CustomTeaser.class}, resourceType = TeaserImpl.RESOURCE_TYPE)

Use CustomeTaeser to adapt to Junit test cases.

It will not cover 100% coverage but you will be able to write test cases for custom functionality.

[gomatis80521865 · Accepted solution]

I tried adding that additional adapter class and I'm still getting null when I try to adapt the context request to my CustomTeaser

[Arun_Patidar · Accepted solution]

Please check demo code:

https://github.com/arunpatidar02/aem63app-repo/blob/master/java/CustomTeaser.java

https://github.com/arunpatidar02/aem63app-repo/blob/master/java/CustomTeaserTest.java

There might be issue with init function inside your model class.

[gomatis80521865 · Accepted solution]

Thank you Arun! I resolved the issue with the help of your sample code. I had missed out the "defaultInjectionStrategy=DefaultInjectionStrategy.OPTIONAL" option in my custom model which in turn caused an error during init when being initialised through the test case.

[thienm92844762 · Accepted solution]

Thank you so much! You saved my life.

[gomatis80521865 · Accepted solution]

Hi Arun. Is it possible to create JUnit test cases even if we use one of the core component Teaser's methods (say like isActionsEnabled or getActions) inside our CustomTeaser's @PostConstruct method? Because when I try to do that I am not able adapt the context without encountering a NullPointer inside the method annotated with @PostConstruct in CustomTeaser.

[pjcalvo · Accepted solution]

Hi.

[pjcalvo · Accepted solution]

Hi. I am having the same problem here. The core component property is always null in the custom implementation. And making it Optional just skips the instantiation of it.

[#11]

Anyway, next to the working solution this seems to be a short-coming of the mocking libraries. Can you create a minimal testcase (at best without any AEM dependency) and post it to the sling-developer list?

[#12]

I have the same issue. I needed to declare the delegate proxy core component (Page in my case) as optional in my sling model as it is not resolved in the unit test (should not be optional in the real use case). Is a pity because my custom logic is simply a fallback of the core component one. I would like to have the object not null in my unit test so I will drop the Optional annotation for the field.

[#13]

Thank you so much!

[gomatis80521865]

have you registered the Sling model for the core teaser component as well to the context?

Jörg

[gomatis80521865]

Yes. I have included it in the context as follows: context.addModelsForClasses(com.adobe.cq.wcm.core.components.models.Teaser.class);

[gomatis80521865]

Yes. I have included it in the context as follows:context.addModelsForClasses(com.adobe.cq.wcm.core.components.models.Teaser.class);