Tasty mocking framework for unit tests in Java
Current version is 2
Still on Mockito 1.x? See what’s new in Mockito 2!
Project status updates
After releasing Mockito 2 (see what’s new) the team will continue to improve version 2.x for a short time, then focus on Mockito 3. Please provide your feedback and suggestions for the scope of Mockito 3.x using the above two channels and GitHub issue tracker. Mockito 3.x will target Java 8.
Fancy getting world-wide visibility and building up an eternal fame of an OSS contributor?
- Help the project site look decent and match the quality of the library!
- Contribute a pull request! It is automatically released via state-of-art continuous delivery automation.
- Use latest version! Hack and experiment. Speak up at the mailing list. Report issues and new features.
Why drink it?
Mockito is a mocking framework that tastes really good. It lets you write beautiful tests with a clean & simple API. Mockito doesn’t give you hangover because the tests are very readable and they produce clean verification errors. Read more about features & motivations.
Massive StackOverflow community voted Mockito the best mocking framework for java. Even though StackOverflow shuns questions that likely raise emotional debates the fact is Mockito has the most votes. You can add your vote, too!
Top 10 Java library across all libraries, not only the testing tools. In late 2013 there was an analysis made of 30.000 GitHub projects. Although Mockito reached number 9 in the main report, mockito-core and mockito-all are the same tool and therefore the factual position of Mockito is number 4, surpassing famous tools like Guava or Spring. Treat this study as an indicator of a big impact that Mockito makes every day on unit tests written in Java.
“We decided during the main conference that we should use JUnit 4 and Mockito because we think they are the future of TDD and mocking in Java”
Given the current popularity of Mockito, Dan was spot on with his prediction.
Use your own judgement in choosing a testing framework. The Mockito team always respects your choice. Keep writing great tests every day!
How do I drink it?
Legacy builds with manual dependency management can use 1.* “mockito-all” distribution. It can be downloaded from Mockito’s Bintray repository or Bintray’s jcenter. “mockito-all” distribution has been discontinued in Mockito 2.*.
now you can verify interactions
and stub method calls
Main reference documentation features:
@Mock: create mock
@Spy: partial mocking, real methods are invoked but still can be verified and stubbed
@InjectMocks: automatically inject mocks/spies fields annotated with
verify(): to check methods were called with given arguments
- Try Behavior-Driven development syntax with BDDMockito
- Use Mockito on Android, thanks to the team working on dexmaker
- Do not mock types you don’t own
- Don’t mock value objects
- Don’t mock everything
- Show love with your tests!
Mockito is served to you by Szczepan Faber and friends. First engineers who were using Mockito in production were developers of the Guardian project in London in early 2008. Szczepan was lucky to be a part of the ThoughtWorks team assigned to the challenging and exciting Guardian project. Here is how he explained why we needed another mocking framework?
Hats down before EasyMock folks for their ideas on beautiful and refactoring-friendly mocking API. First hacks on Mockito were done on top of the EasyMock code.
Currently Mockito is maintained by Szczepan Faber, Brice Dutheil, Rafael Winterhalter, Tim van der Lippe, Marcin Grzejszczak, Marcin Zajączkowski and a small army of contributors. Friends who contributed to Mockito (apologize if I missed somebody): Pascal Schumacher, Christian Schwartz, Igor Czechowski, Patric Fornasier, Jim Barritt, Felix Leipold, Liz Keogh, Dan North, Bartosz Bańkowski, David Wallace.
- Thanks to Éric Lefevre-Ardant for his long running and continuous support on the mailing-list
- Thanks to Erik Ramfelt, and Steve Christou for the Jenkins server that was used originally for CI.
- Thanks to Erik Brakkee who originally helped with maven central syncing.
- Thanks to Igor Czechowski for dealing with maven central and for the name “Mockito”!
- Thanks to Karol Poźniak for the original colorful logo, Darek Chrzan for the second one, and Évy Dutheil for the third :)
Training by core engineers
Mockito core engineers, experts in the field of software quality can help you with:
- getting your team up to speed with test automation with mock objects
- enabling and sustaining test driven development in its best form: BDD
- achieving maintainable, high quality tests that unlock continuous delivery
- securing production code quality and minimizing defects through rigorous test automation
Get in touch at email@example.com