Seems like you are not using Field setter methods in your test class and hence no failure.

@DPrakashRaj  That is good that worked for you. But can you confirm if you have aem context used in any of your junit classes to set objects? I tried with the same versions as you pinged above, but the failure is the same as below. I think the below class is deprecated.Please find my test class belo...

@Teja_G  Yes. this was done and there was no success.

@kautuk_sahni  I am not sure you got a chance to check through my full comments. This issue is still open and build is a failure after SP19. I was able to progress with some changes in dependencies, but it is back to the same state with errors. Do you have insights into any customers did SP19 upgrad...

@DPrakashRaj  I was able to progress a bit further with that error by creating a reflection class inside the class instead of using internal method as below, but still build is a failure and came back to original errors. Please find details below. We also opened a ticket with Adobe for the build iss...

@DPrakashRaj  Yes. Like I commented above using 4.9.0 now since I found mockito 5 and above doesn't work for java8, but still lot of errors as below and working through it 

@Teja_G  If you have been following my above comments. That didn't work and also mockito 5.0.0 and above will noy work for java 8

@DPrakashRaj Seeing the latest error I got and this post - https://stackoverflow.com/questions/60612488/error-class-file-has-wrong-version-55-0-should-be-52-0-when-building-alfresco.  and https://github.com/digital-preservation/droid/issues/914 It seems like some of the API compiles only in java 11....

Thanks @DPrakashRaj . Did this change as well. Now it's a different error, I am looking into after the change you mentioned.If, I comment the full class, it throws another mockito error with a different error in another class.Seems like some classes have changed with dependencies on uber jar update....

@kautuk_sahni  I have updated the reply to @DPrakashRaj . Unfortunately, build issue is still not fixed.