code: @CheckReturnValue
      public static <T> T mock(Class<T> classToMock, String name) {
          return mock(classToMock, withSettings()
                  .name(name)
                  .defaultAnswer(RETURNS_DEFAULTS));
      }
docs: Specifies mock name. Naming mocks can be helpful for debugging - the name is used in all verification errors.
  <p>
  Beware that naming mocks is not a solution for complex code which uses too many mocks or collaborators.
  <b>If you have too many mocks then refactor the code</b> so that it's easy to test/debug without necessity of naming mocks.
  <p>
  <b>If you use <code>&#064;Mock</code> annotation then you've got naming mocks for free!</b> <code>&#064;Mock</code> uses field name as mock name. {@link Mock Read more.}
  <p>
  
  See examples in javadoc for {@link Mockito} class
  
  @param classToMock class or interface to mock
  @param name of the mock
  @return mock object