issue hcoles#537 fix failing unit tests

michielgkalkman · Jun 1, 2020 · 7f70532 · 7f70532
1 parent 692a430
commit 7f70532
Showing 1 changed file with 5 additions and 7 deletions.
diff --git a/pitest/src/test/java/org/pitest/junit/JUnitCustomRunnerTestUnitFinderTest.java b/pitest/src/test/java/org/pitest/junit/JUnitCustomRunnerTestUnitFinderTest.java
@@ -123,13 +123,11 @@ public CustomSuiteRunner(final Class<?> klass, final RunnerBuilder rb)
    *
    * This appears to be happening in org.apache.maven.plugins:maven-pmd-plugin:3.13.0.
    *
-   * This needs to be addressed in two ways:
-   * 1) if the Suite has no SuiteClasses, isTest() is
-   * true. Pitest must not fail if the the name in the
-   * Description throws a ClassNotFoundException
-   * 2) if the Suite has SuiteClasses, isTest() is false,
-   * Pitest must then use the child descriptions of the Suite
-   * to continue testing with.
+   * This needs to be addressed as follows:
+   * if a ClassNotFoundException is thrown
+   * when creating a TestUnit because of non-class name,
+   * find its direct children to create test units
+   * from.
    */
   public static class CustomDescriptionSuiteRunner extends Suite {