-
Currently trying to find out if this is a bug in Tycho 2.6+ or not. Test bundle with mixed JUnit4/5 tests inside. Resolution was to use org.junit.Assume.assumeTrue(), thus making the test not pure JUnit5 anymore. Difference between Tycho 2.5 and 2.6 is that in 2.6 it uses the new JUnit57vintage provider. If I use the JUnit5 Assumption in a pure JUnit5 test bundle, the JUnit5 assumption works as expected again, and it uses the JUnit57 provider but not the JUnit57vintage provider. Did I miss something that is necessary since Tycho 2.6 or is this a bug? Thanks. |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 1 reply
-
After a little more investigation I'm fairly confident this is a bug in Tycho 2.6+. I'm going to convert this to an issue. |
Beta Was this translation helpful? Give feedback.
-
For future reference: The ticket: #630 |
Beta Was this translation helpful? Give feedback.
After a little more investigation I'm fairly confident this is a bug in Tycho 2.6+. I'm going to convert this to an issue.