Support @Suite from JUnit5 about eclipse.jdt.ui

[noopur2507]

This issue seems to be fixed

Thanks for the confirmation.

[ktatavarthi]

@jjohnstn is this issue a continuation of

• Bug 576995 - [junit 5] Add @suite support from JUnit 5.8.1

Please add your comments here.

[jjohnstn]

Will do.

[jjohnstn]

Looking into this, it seems there is some requirement for the suite name to start with the prefix "Test". If I rename the file to be TestCssCoreTestSuite, it works. I need to look at where the filtering is taking place and why it isn't looking at the annotation.

[jjohnstn]

I have just installed the new EPP for Eclipse Committers 2022-06 and now it works fine in a child Eclipse without a need for a rename.

I have the following additional change to MANIFEST.MF

• org.junit.platform.suite.api;bundle-version="1.1.0"

• org.junit.platform.suite.api;bundle-version="1.1.0",
• org.junit.platform.suite.engine;bundle-version="1.8.1",
• org.junit.jupiter.engine;bundle-version="5.8.1"

There is cached information in the TestKindRegistry which would explain why a rename fixed the problem for me and it works today after restarting. Could you add the changes above and restart with -clean and see if it works for you?

[vogella]

Thanks @jjohnstn for looking into this. I'm still not able to run the test suite. I pushed the example to eclipse-platform/eclipse.platform.ui#158 to make it easier to check what is wrong. My version range for the MANIFEST.MF is different, I picked whatever the Eclipse SDK provides as version.

 org.junit.jupiter.api;bundle-version="5.8.1",
 org.junit.platform.suite.api;bundle-version="1.8.1",
 org.junit.platform.suite.engine;bundle-version="1.8.1",
 org.junit.jupiter.engine;bundle-version="5.8.1"

[fedejeanne]

This issue seems to be fixed