Refactoring the tests that use too many mocks

In this recipe, we will take a look at a test that uses too many Mockito mocks. In this way, the test code becomes unreadable and unmaintainable. Since your test code is your living documentation, you should always remember to put a lot of effort into refactoring it until you can read it like a book.

Getting ready

For this recipe, we will again generate a new identity for a given person. Each person has an address, and that address has a street number. Since we are performing unit testing, we will check in isolation whether NewIdentityCreator properly executes its logic. It is responsible for creating a new name, new street number, and new siblings for the current person, as shown in the following code:

class NewIdentityCreator {

  public String createNewName(Person person) {
        return person.getName() + "_new";
    }

  public int createNewStreetNumber(Person person) {
        return person.getAddress().getStreetNumber() + 5;
    }

    public...