"java.lang.NoSuchFieldError: FACTORY" while running Junit test in AEM codebase

 I was implementing Unit testing for a already running AEM project. After adding all the dependencies and after creation of basic structure for Sling model test class my test gets executed as expected.


@ExtendWith({ AemContextExtension.class, MockitoExtension.class })
class DummyComponentImplTest {

@BeforeEach
void setUp() {
}

@Test
public void testGetHeading() {
}

}

But soon as I add below line at line #25 in the above running test case


private final AemContext aemContext = new AemContext();

and try to run the test in terminal getting below error in the terminal's maven console.


Running com.myproject.aem.models.impl.DummyComponentImplTest
[ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 2.258 s <<< FAILURE! - in com.myproject.aem.models.impl.DummyComponentImplTest
[ERROR] testGetHeading Time elapsed: 0.007 s <<< ERROR!
java.lang.NoSuchFieldError: FACTORY

after doing so much google did some changes at the dependency level based on the solutions, from google search, but things didn't changed for me.

Problem was very simple but as I was not getting much stack trace either in console or in surefire-report.txt file,  not able to identify the actual cause for the problem.

When I run the same test case in eclipse, same error but the good thing was the stack trace for the error.


java.lang.NoSuchFieldError: FACTORY
at com.google.gson.Gson.<init>(Gson.java:200)
at com.google.gson.Gson.<init>(Gson.java:174)
at com.myproject.aem.models.feed.FeedVariationModel.<clinit>(FeedVariationModel.java:43)

Here I got to know the name and the location of the existing Sling model. In the particular sling model there were an unused Gson object in class scope, which was the culprit.


private static final Gson gson = new Gson();

So I had only few options like either remove the private static modifier for the object or remove this entire line since the Gson object was unused so I commented it out and finally got my easy test ride 😄


Thank you.



Comments

Post a Comment

Popular posts from this blog

Common cause for NullPionterException or Null value in Junit test case for sling model in aem

Image
  Below are the common cause for NullPointerException and Null value in Junit test for Sling model: Problem with the adaptables Let say your sling model is adaptables to sling Resource and in your test class you are trying to get the instance of your respective Object by adapting request of aemContext. In this case you will end up with NullPointerException.  For example: Sling Model : @Model ( adaptables = { Resource .class}, adapters = { SolutionHeroComponent .class}, resourceType = { SolutionHeroComponentImpl .RESOURCE_TYPE}, defaultInjectionStrategy = DefaultInjectionStrategy .OPTIONAL ) @Exporter ( name = "jackson" , selector = "solutionhero" , extensions = "json" ) public class SolutionHeroComponentImpl implements SolutionHeroComponent { protected static final String RESOURCE_TYPE = "myproject/components/solutionhero" ; @Inject @Named (SOLUTION_HERO_TITLE)
Read more

@Inject : A discouraged sling-model annotation

Image
"I just copy and paste it from somewhere and since it was working so I keep it like this. 😎"           @ Model (adaptables = Resource . class )      public class ExampleModel { @ Inject private MyService myService ; @ Inject private String title ; // ... rest of the class } I got this reply from the developer while reviewing his code above so thought of writing one extension post of my previous blog  Common Myths Around Sling Model .  So lets dive into the working mechanism of @Inject annotation but before that I would like to explain the injector first.                                                                      An OOB injector      @ Component (property= Constants . SERVICE_RANKING + ":Integer=3000" ,                service={ Injector . class , InjectAnnotationProcessorFactory2 . class }) public class ChildResourceInjector extends AbstractInjector implements Injector ,      Inject
Read more