Getting Null pointer exception while mocking resourceResolver | Community
Skip to main content
New Participant
April 9, 2025
Solved

Getting Null pointer exception while mocking resourceResolver

In my SImple.java class inside workflow

I am having 

try(ResourceResolver resourceResolver = getResolver(resourceResolverFactory)) {.......}

 

In my SImpleTest.java class

Resource resource = context.resourceResolver().getResource("/content/........");

cu.excute(workItem, workflowSession, processArguments);

 

 

getting null pointer exception test class for cu.excute method.

Any other approach to handle resourceResolverFactory ? 

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
daniel-strmecki
daniel-strmeckiAccepted solution
New Participant
April 11, 2025

Do not mock the Resource Resolver yourself; the mocks from AEM Mocks work great.

Use org.apache.sling.testing.resourceresolver.MockResourceResolverFactory.

 

Good luck,

Daniel

3 replies

kapil_rajoria
New Participant
April 10, 2025

Hi @dhananjayku5 ,
Did you try using mockito to mock the required things: import org.mockito.Mockito;

ResourceResolverFactory resourceResolverFactory = mock(ResourceResolverFactory.class);
ResourceResolver resourceResolver = mock(ResourceResolver.class);
Resource resource = mock(Resource.class);
Translate
daniel-strmecki
daniel-strmeckiAccepted solution
New Participant
April 11, 2025

Do not mock the Resource Resolver yourself; the mocks from AEM Mocks work great.

Use org.apache.sling.testing.resourceresolver.MockResourceResolverFactory.

 

Good luck,

Daniel

Translate
muskaanchandwani
Employee
April 9, 2025

@dhananjayku5 you can try to mock ResourceResolverFactory and inject a working ResourceResolver in your test using AEM Mocks :
https://experienceleague.adobe.com/en/docs/experience-manager-learn/getting-started-wknd-tutorial-develop/project-archetype/unit-testing#setting-up-aem-test-context

Translate