-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support JUnit 5 #113
Support JUnit 5 #113
Conversation
Codecov Report
@@ 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
Continue to review full report at Codecov.
|
Actually, Pitclipse cannot run JUnit 5 tests when it is installed from an update site:
Hopefully it will just be a matter of adding the |
aa10844
to
cb25e89
Compare
Actually I just missed the Moreover I observed that no exception was shown in the console when testing JUnit 5 on Eclipse Oxygen which confirms my preceding hypothesis. |
Because: - older versions of Eclipse IDE do not support JUnit 5, making hard to test whether Pitclipse supports JUnit 5 test Breaking change: - drop support for Eclipse Mars, Eclipse Neon
Details: - wrap the pitest-junit5-plugin Maven plugin as an Eclipse bundle - this plugin allows Pitest to detect JUnit 5 tests; it is dynamically added to Pitest's classpath when JUnit 5 is detected in project's classpath
Because: - they are shown in the console during PIT execution but provide no value
Because: - I just faced issues while changing project's version due to Maven using the tycho-versions-plugin 1.3.0
cb25e89
to
1df64f7
Compare
SonarCloud Quality Gate failed. 0 Bugs |
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