Support JUnit 5

[echebbi]

Closes #73.

Rely on the pitest-junit5-plugin Maven plugin to discover JUnit 5 tests. Its JARs are wrapped as an Eclipse bundle and dynamically added to Pitest's classpath when JUnit 5 is detected in project's classpath.

Sadly, some exceptions are shown in the console when running JUnit 5 tests but I didn't manage to solve them; actually I suspect that they depend on the version of JUnit 5 installed in Eclipse IDE.

Excerpt of an output produced by Pitest

 java.lang.NoClassDefFoundError: org/junit/platform/engine/support/filter/ExclusionReasonConsumingFilter
   at org.junit.vintage.engine.discovery.VintageDiscoverer.createTestClassPredicate(VintageDiscoverer.java:83)
   at org.junit.vintage.engine.discovery.VintageDiscoverer.collectTestClasses(VintageDiscoverer.java:61)
   at org.junit.vintage.engistderr  : ne.discovery.VintageDiscoverer.discover(VintageDiscoverer.java:51)
   at org.junit.vintage.engine.VintageTestEngine.discover(VintageTestEngine.java:65)
   at org.junit.platform.launcher.core.DefaultLauncher.discoverEngineRoot(DefaultLauncher.java:130)
   at ostderr  : rg.junit.platform.launcher.core.DefaultLauncher.discoverRoot(DefaultLauncher.java:117)
   at org.junit.platform.launcher.core.DefaultLauncher.execute(DefaultLauncher.java:90)
   at org.pitest.junit5.JUnit5TestUnitFinder.findTestUnits(JUnit5TestUnitFinder.javstderr  : a:79)
   at org.pitest.testapi.execute.FindTestUnits.findTestUnits(FindTestUnits.java:57)
   at org.pitest.testapi.execute.FindTestUnits.getTestUnits(FindTestUnits.java:40)
   at org.pitest.testapi.execute.FindTestUnits.findTestUnitsForAllSuppliedClasses(Findstderr  : TestUnits.java:29)
   at org.pitest.mutationtest.execute.MutationTestMinion.findTestsForTestClasses(MutationTestMinion.java:154)
   at org.pitest.mutationtest.execute.MutationTestMinion.run(MutationTestMinion.java:94)
   at org.pitest.mutationtest.execute.Mutstderr  : ationTestMinion.main(MutationTestMinion.java:137)
Caused by: java.lang.ClassNotFoundException: org.junit.platform.engine.support.filter.ExclusionReasonConsumingFilter
   at java.net.URLClassLoader.findClass(URLClassLoader.java:382)
   at java.lang.ClassLoadstderr  : er.loadClass(ClassLoader.java:424)
   at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:349)
   at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
   ... 14 more

[codecov]

Codecov Report

Merging #113 into master will decrease coverage by 0.47%.
The diff coverage is 77.77%.

@@             Coverage Diff              @@
##             master     #113      +/-   ##
============================================
- Coverage     84.86%   84.39%   -0.48%     
+ Complexity      298      296       -2     
============================================
  Files            45       45              
  Lines          1242     1243       +1     
  Branches         88       89       +1     
============================================
- Hits           1054     1049       -5     
- Misses          127      132       +5     
- Partials         61       62       +1

Impacted Files	Coverage Δ	Complexity Δ
...ner/src/org/pitest/pitclipse/runner/PitRunner.java	51.28% <ø> (+1.28%)	6 <0> (ø)	⬇️
...org/pitest/pitclipse/runner/io/SocketProvider.java	73.17% <ø> (-1.25%)	10 <0> (ø)
...c/org/pitest/pitclipse/runner/PitCliArguments.java	94.38% <0%> (-2.17%)	25 <0> (ø)
...er/src/org/pitest/pitclipse/runner/PitOptions.java	90.24% <100%> (-3.78%)	17 <1> (ø)
...er/src/org/pitest/pitclipse/runner/PitRequest.java	94.11% <0%> (-5.89%)	5% <0%> (-1%)
...er/src/org/pitest/pitclipse/runner/PitResults.java	83.87% <0%> (-3.23%)	5% <0%> (-1%)

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 46ca555...1df64f7. Read the comment docs.

[echebbi]

Actually, Pitclipse cannot run JUnit 5 tests when it is installed from an update site:

org.pitest.util.PitError: Could not load requested test plugin junit5

Hopefully it will just be a matter of adding the META-INF/services/org.pitest.testapi.TestPluginFactory file to org.pitest.pitest-junit5-plugin.

[echebbi]

Actually I just missed the Eclipse-BundleShape: dir line in pitest-junit5-plugin's MANIFEST.MF file.

Moreover I observed that no exception was shown in the console when testing JUnit 5 on Eclipse Oxygen which confirms my preceding hypothesis.

[sonarcloud]

SonarCloud Quality Gate failed.

0 Bugs
0 Vulnerabilities (and 0 Security Hotspots to review)
1 Code Smell

0.0% Coverage
0.0% Duplication