Analyzed
7 months
ago.
based on code collected
almost 2 years
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...
- ...
- ...
- ...
-
...
took an estimated 12 years of effort (COCOMO model)
starting with its first commit in November, 2007
ending with its most recent commit over 2 years ago
Quick Reference
git://github.com/mockito/mockito...
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.
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
Did You Know...
-
...
nearly 1 in 3 companies have no process for identifying, tracking, or remediating known open source vulnerabilities
-
...
anyone with an Open Hub account can update a project's tags
-
...
65% of companies leverage OSS to speed application development in 2016
-
...
by exploring contributors within projects, you can view details on every commit they have made to that project
30 Day SummarySep 5 2018 — Oct 5 2018
|
12 Month SummaryOct 5 2017 — Oct 5 2018
|
