What Are The Limitations Of Mockito?

1.	What Are The Limitations Of Mockito?
Answer» Mockito 2.x specific limitations Requires JAVA 6+ Cannot mock static methods Cannot mock constructors Cannot mock equals(), hashCode(). Firstly, you should not mock those methods. Secondly, Mockito defines and depends upon a specific implementation of these methods. Redefining them MIGHT break Mockito. Mocking is only possible on VMs that are supported by Objenesis. Don't worry, most VMs should work just fine. Spying on real methods where real implementation REFERENCES outer CLASS via OuterClass.this is impossible. Don't worry, this is extremely rare case. Mockito 1.x Specific limitations Needs Java 5+ Cannot mock FINAL classes Cannot mock final methods - their real behavior is executed without any exception. Mockito cannot warn you about mocking final methods so be vigilant. Cannot mock static methods Cannot mock constructors Cannot mock equals(), hashCode(). Firstly, you should not mock those methods. Secondly, Mockito defines and depends upon a specific implementation of these methods. Redefining them might break Mockito. Mocking is only possible on VMs that are supported by Objenesis (Note Objenesis is in version 2.1). Don't worry, most VMs should work just fine. Spying on real methods where real implementation references outer Class via OuterClass.this is impossible. Don't worry, this is extremely rare case. Mockito 2.x specific limitations Mockito 1.x Specific limitations

Answer»

Mockito 2.x specific limitations

Requires JAVA 6+
Cannot mock static methods
Cannot mock constructors
Cannot mock equals(), hashCode(). Firstly, you should not mock those methods. Secondly, Mockito defines and depends upon a specific implementation of these methods. Redefining them MIGHT break Mockito.
Mocking is only possible on VMs that are supported by Objenesis. Don't worry, most VMs should work just fine.
Spying on real methods where real implementation REFERENCES outer CLASS via OuterClass.this is impossible. Don't worry, this is extremely rare case.

Mockito 1.x Specific limitations

Needs Java 5+
Cannot mock FINAL classes
Cannot mock final methods - their real behavior is executed without any exception. Mockito cannot warn you about mocking final methods so be vigilant.
Cannot mock static methods
Cannot mock constructors
Cannot mock equals(), hashCode(). Firstly, you should not mock those methods. Secondly, Mockito defines and depends upon a specific implementation of these methods. Redefining them might break Mockito.
Mocking is only possible on VMs that are supported by Objenesis (Note Objenesis is in version 2.1). Don't worry, most VMs should work just fine.
Spying on real methods where real implementation references outer Class via OuterClass.this is impossible. Don't worry, this is extremely rare case.

Discussion