Using Mockito with JUnit 5

[@arvinttrigger4501]

Simple , Quick , Effective and Informative ...👏👏

[@codewitharho]

Thank you!

[@robinmathur5807]

Thanks for making good content for us, I would appreciate if you make some content on internal of JUnit Framework and how different annotations on class level like @JsonTest/@MockitoExtension works with JUnit framework.

[@codewitharho]

Looks like I have forgotten to reply, but that sounds like a good idea for better understanding.

[@z00lus]

Quick , informative video. Nothing more than need. Just perfect! Subscribe

[@codewitharho]

Thanks! I try to keep it short :)

[@anunymous7]

100th subscriber. Yay!

[@sangtv_AK]

Hi Arho, thank you for sharing your knowledge. I appreciate your time and consideration. P.S: I suggest you upload a video to tell the audience about your channel's content on your KZbin's home page.

[@codewitharho]

Thanks for the suggestion! I will surely look into it.

[@mohankumarc2605]

Kindly do a video on private method refactoring , so it can be unit tested concept. Greatly appreciate your time and help

[@codewitharho]

Appreciate the feedback, I will definitely put this into my list of possible videos. Thanks!

[@sohrabsheykhmohammadi1909]

awesome

[@codewitharho]

Thanks!

[@sanu7611]

When I run whole test class some methods are failing, when I run single test in class then it is passing.why so??

[@codewitharho]

Some tests leave behind state that affects the other tests.

[@Hawkeeye747]

Can u elaborate as to why is it bad practice to mock private methods?

[@codewitharho]

The main reason is that the test becomes more coupled to the implementation. When we mock private methods (or test private methods), every time we want to change the implementation, the test will break. One of the biggest reasons why people think that unit testing suck is when they have coupled the tests too tightly to the implementation. We should focus on testing the behaviour of the class, but mocking a private method means that we alter the internal behaviour. So we should apply mocking only to external dependencies and not the class itself. If there is a "bad" dependency in a private method, we should consider refactoring so that it becomes an external dependency.

[@evanderstewart2320]

Is there a way to mock private methods using JUnit 5 as I'm trying with PowerMock, but with no success?

[@codewitharho]

I usually suggest refactoring the code so that you don’t have to. For example, if a private method is calling something that you want to mock, make that a dependency of the class instead.

[@Hawkeeye747]

@@codewitharho okay so when the private method is run in the test it would run the mocked method inside its body?

[@codewitharho]

@@Hawkeeye747 yes, the class would have a dependency to another class, and the private method would call a method in that other class, which would then be mocked.

[@mangethegamer]

Please don't use music while you talk in the video.

[@codewitharho]

Yeah, I have received similar feedback. Fixed in newer videos!