I'd like to list what classes are touched during the execution of each unit test. I want to discover which tests have an overly large scope and should use a smaller unit instead. Measuring the code coverage via IntelliJ or JaCoCo doesn't help me as I cannot drill down to a single test. Has anyone managed to do something similar? I found a

We can see that the method testCalculateBalance of BalanceCalculatorTest covers BalanceCalculator, PriorServiceBalanceProvider and TimeAccount, but we don't see TimeAccountProvider, because it is mocked in the test. I'll paste the code snippets, so you get the full picture. Bottom line is, it works, but it is not very user friendly.

public class BalanceCalculatorTest {

@Test
public void testCalculateBalance() {
    TimeAccountProvider timeAccountProvider = Mockito.mock(TimeAccountProvider.class);
    Mockito.doReturn(Collections.singleton(new TimeAccount())).when(timeAccountProvider).getTimeAccounts();
    BalanceCalculator balanceCalculator = new BalanceCalculator(timeAccountProvider);
    Assert.assertEquals(balanceCalculator.calculateBalance(), 2);
}

}

public class BalanceCalculator {

private final TimeAccountProvider timeAccountProvider;

public BalanceCalculator(TimeAccountProvider timeAccountProvider) {
    this.timeAccountProvider = timeAccountProvider;
}

public int calculateBalance() {
    Set<TimeAccount> timeAccounts = timeAccountProvider.getTimeAccounts();
    int sum = 0;
    for (TimeAccount timeAccount : timeAccounts) {
        Set<TimeAccountDetail> bookings = timeAccount.getTimeAccountDetails();
        sum  = bookings.stream()
                .mapToInt(TimeAccountDetail::getAmount)
                .sum();
    }
    sum  = new PriorServiceBalanceProvider().getPriorBalance();
    return sum;
}

}