Mockito

I Use This!

Inactive

Analyzed 1 day ago. based on code collected 1 day 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.

In a Nutshell, Mockito...

...
has had 10,644 commits made by 271 contributors
representing 117,480 lines of code
...
is mostly written in Java
with an average number of source code comments
...
has a well established, mature codebase
maintained by nobody
with stable Y-O-Y commits
...
took an estimated 30 years of effort (COCOMO model)
starting with its first commit in November, 2007
ending with its most recent commit almost 3 years ago

Quick Reference

Project Links:

Homepage
Community
Documentation
Download
Issue Trackers
Mailing Lists

(2 Locations)

Licenses

MIT License

Permitted

Commercial Use

Modify

Distribute

Sub-License

Private Use

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.

All Licenses

Project Security

Vulnerabilities per Version ( last 10 releases )

There are no reported vulnerabilities

Project Vulnerability Report

Security Confidence Index

Poor security track-record

Favorable security track-record

Vulnerability Exposure Index

Many reported vulnerabilities

Few reported vulnerabilities

About Project Vulnerability Report

Did You Know...

...
in 2016, 47% of companies did not have formal process in place to track OS code
...
compare projects before you chose one to use
...
nearly 1 in 3 companies have no process for identifying, tracking, or remediating known open source vulnerabilities
...
you can subscribe to e-mail newsletters to receive update from the Open Hub blog