From 49e6311fcf774f6931ffbb627702e4fb99ef3604 Mon Sep 17 00:00:00 2001 From: Marc Philipp Date: Sat, 23 Mar 2019 14:36:34 +0100 Subject: [PATCH] Report initialization failures per test method Prior to this commit, `DefaultInternalRunner` threw an exception when `MockitoAnnotations.initMocks()` failed from the overridden `withBefores` method. Instead, it now returns a `Statement` that is responsible for initializing. Potential exceptions are then handled by JUnit, regardless whether version 4.12 or 4.13-beta-2 is used. Instead of reporting a class-level error, JUnit will now report a failure for each test method in such test classes. Related issue: junit-team/junit4#1599 --- .../runners/DefaultInternalRunner.java | 31 ++++++++----------- .../runners/DefaultInternalRunnerTest.java | 6 ++-- 2 files changed, 16 insertions(+), 21 deletions(-) diff --git a/src/main/java/org/mockito/internal/runners/DefaultInternalRunner.java b/src/main/java/org/mockito/internal/runners/DefaultInternalRunner.java index 2f26ff1359..93aa32d46e 100644 --- a/src/main/java/org/mockito/internal/runners/DefaultInternalRunner.java +++ b/src/main/java/org/mockito/internal/runners/DefaultInternalRunner.java @@ -30,34 +30,29 @@ public DefaultInternalRunner(Class testClass, final Supplier