@@ -69,7 +69,7 @@
Loading
69 69
 * </code></pre>
70 70
 *
71 71
 * If you would like to take advantage of Mockito JUnit runner features
72 -
 * but you cannot use the runner because, for example, you use TestNG, there is a solution!
72 +
 * but you cannot use the runner there is a solution!
73 73
 * {@link MockitoSession} API is intended to offer cleaner tests and improved debuggability
74 74
 * to users that cannot use Mockito's built-in JUnit support (runner or the rule).
75 75
 */

@@ -1371,9 +1371,11 @@
Loading
1371 1371
 *
1372 1372
 * To quickly find out how "stricter" Mockito can make you more productive and get your tests cleaner, see:
1373 1373
 * <ul>
1374 -
 *     <li>Strict stubbing with JUnit Rules - {@link MockitoRule#strictness(Strictness)} with {@link Strictness#STRICT_STUBS}</li>
1375 -
 *     <li>Strict stubbing with JUnit Runner - {@link MockitoJUnitRunner.StrictStubs}</li>
1376 -
 *     <li>Strict stubbing if you cannot use runner/rule (like TestNG) - {@link MockitoSession}</li>
1374 +
 *     <li>Strict stubbing with JUnit4 Rules - {@link MockitoRule#strictness(Strictness)} with {@link Strictness#STRICT_STUBS}</li>
1375 +
 *     <li>Strict stubbing with JUnit4 Runner - {@link MockitoJUnitRunner.Strict}</li>
1376 +
 *     <li>Strict stubbing with JUnit5 Extension - <code>org.mockito.junit.jupiter.MockitoExtension</code></li>
1377 +
 *     <li>Strict stubbing with TestNG Listener <a href="https://github.com/mockito/mockito-testng">MockitoTestNGListener</a></li>
1378 +
 *     <li>Strict stubbing if you cannot use runner/rule - {@link MockitoSession}</li>
1377 1379
 *     <li>Unnecessary stubbing detection with {@link MockitoJUnitRunner}</li>
1378 1380
 *     <li>Stubbing argument mismatch warnings, documented in {@link MockitoHint}</li>
1379 1381
 * </ul>
Files Complexity Coverage
src/main/java/org/mockito 85.67% 84.85%
subprojects 79.06% 85.34%
Project Totals (325 files) 85.58% 84.86%
Sunburst
The inner-most circle is the entire project, moving away from the center are folders then, finally, a single file. The size and color of each slice is representing the number of statements and the coverage, respectively.
Icicle
The top section represents the entire project. Proceeding with folders and finally individual files. The size and color of each slice is representing the number of statements and the coverage, respectively.
Grid
Each block represents a single file in the project. The size and color of each block is represented by the number of statements and the coverage, respectively.
Loading