issues/163: Some tests in nested classes are not exercised when changing related production code not exercised by the tests' top-level class

[pjmartos]

Skippy appears to not be taking into account that test classes may contain nested classes (e.g. JUnit 5 test classes annotated with @Nested) that in turn may contain test methods of their own (it is not mandatory, but it is usually the case).

Worts case scenario, if the top-level class itself doesn't exercise a production class that has changed, none of the tests would be executed, even if some of the nested classes of that test class do. The net result is that the change in the production class would be undetected.