Analyzed
about 2 months
ago.
based on code collected
about 2 months
ago.
Project Summary
Java mocking is dominated by expect-run-verify libraries like EasyMock or jMock. Mockito offers simpler and more intuitive approach: you ask questions about interactions after execution. Using mockito, you can verify what you want. Using expect-run-verify libraries you are often forced to look after irrelevant interactions.
Badges
In a Nutshell, Mockito...
- ...
- ...
-
...
has a well established, mature codebase
maintained by a large development team
with decreasing Y-O-Y commits -
...
took an estimated 12 years of effort (COCOMO model)
starting with its first commit in November, 2007
ending with its most recent commit 11 months ago
Quick Reference
git://github.com/mockito/mockito...
MIT License
Permitted
Commercial Use
Modify
Distribute
Private Use
Sub-License
Forbidden
Hold Liable
Required
Include Copyright
Include License
These details are provided for information only. No information here is legal advice and should not be used as such.
This Project has No vulnerabilities Reported Against it
Did You Know...
-
...
Black Duck offers a free trial so you can discover if there are open source vulnerabilities in your code
-
...
search using multiple tags to find exactly what you need
-
...
65% of companies leverage OSS to speed application development in 2016
-
...
anyone with an Open Hub account can update a project's tags
30 Day SummarySep 5 2018 — Oct 5 2018
|
12 Month SummaryOct 5 2017 — Oct 5 2018
|
