Скачать или смотреть How to Mock Exceptions in Java for Effective Testing

Discover how to effectively `mock` exceptions in Java using Mockito and avoid null errors in your tests.
---
This video is based on the question https://stackoverflow.com/q/69471034/ asked by the user 'Another' ( https://stackoverflow.com/u/17037767/ ) and on the answer https://stackoverflow.com/a/69471106/ provided by the user 'Jeff Bowman' ( https://stackoverflow.com/u/1426891/ ) at 'Stack Overflow' website. Thanks to these great users and Stackexchange community for their contributions.

Visit these links for original content and any more details, such as alternate solutions, latest updates/developments on topic, comments, revision history etc. For example, the original title of the Question was: Mock in java exception

Also, Content (except music) licensed under CC BY-SA https://meta.stackexchange.com/help/l...
The original Question post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license, and the original Answer post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license.

If anything seems off to you, please feel free to write me at vlogize [AT] gmail [DOT] com.
---
How to Mock Exceptions in Java for Effective Testing

Testing is an essential part of software development, particularly in Java, where you often encounter various types of exceptions that your code needs to manage. One common scenario is when dealing with custom exceptions, such as a NotFoundException. In this post, we'll break down how to properly mock exceptions in your Java code using Mockito, and ensure that your tests run smoothly without encountering null errors.

The Problem: Mocking a Custom Exception

Let's consider a situation where you have a custom NotFoundException that your code may throw when a resource isn't found. Here's the catch block you're dealing with:

[[See Video to Reveal this Text or Code Snippet]]

You want to mock this exception in your unit tests but encounter a null exception. The code you attempted was as follows:

[[See Video to Reveal this Text or Code Snippet]]

The problem arises because of the line ex.getError().setTitle(NOT_FOUND);, which leads to a null pointer exception since ex.getError() returns null.

The Solution: Properly Mocking the Exception

To successfully mock the NotFoundException, follow these steps:

1. Understand How Matchers Work

The way matchers like any() and eq() work in Mockito is crucial. The anyString() matcher does not return a real String but provides a placeholder in the Mockito calls. Therefore, in your when condition, use any() instead of eq(any()):

[[See Video to Reveal this Text or Code Snippet]]

2. Provide a Valid Error Object

To resolve the null pointer issue, you need to pass a valid Error object into the NotFoundException constructor. This is because the getError() method on the NotFoundException instance is expected to return a non-null Error object that is later used to set the title of the error. Modify your test code like this:

[[See Video to Reveal this Text or Code Snippet]]

3. Mock the Error Object If Necessary

If creating an Error object is complicated or resource-intensive, you can mock it instead:

[[See Video to Reveal this Text or Code Snippet]]

Then, use this mockError in your NotFoundException:

[[See Video to Reveal this Text or Code Snippet]]

Conclusion

Mocking exceptions in Java using Mockito can sometimes be tricky, especially with custom exceptions like NotFoundException. By following the appropriate steps and ensuring that you provide a valid Error object, you can effectively avoid null pointer exceptions and make your tests robust and reliable.

Embrace mocking and make your testing process smoother, ensuring that your code handles exceptions gracefully.