Convert tests to JUnit5

[jonahgraham]

The state of CDT tests is a mishmash of JUnit3/4/5 paradigms. Now JUnit6 has just been released and I think we should avoid also having JUnit6 intermixed.

This is an umbrella bug that all the associated work can be connected to, but there is no specific release to complete this. This is a good first issue because updating tests is a good way to become familiar with the CDT code base.

[Attyuttam]

Hi, if this issue is still open, I would like to pick it up

[jonahgraham]

Wonderful @Attyuttam - there is lots to do. I have pushed all my draft work to #1390

I have had to lower the priority of that work. I had thought the JUnit5 conversion was necessary to resolve some other issues with testing (namely #1375) - but once I realized the issue was elsewhere I didn't see this to conclusion.

Please feel free to pick up my work, or start converting other (non org.eclipse.cdt.core) tests.

[jonahgraham]

PS In case you haven't seen it yet, https://github.com/eclipse-cdt/cdt/blob/main/TESTING.md#converting-tests-to-junit5 has some previous guidelines I wrote on doing the converting. Please feel free to provide PRs to TESTING.md as you learn new stuff that is worth sharing.

[Attyuttam]

Hey @jonahgraham , thanks for replying. I went through your PR as well the TESTING.md file.
It seems that you are upgrading all tests in Junit3/4 to Junit5 and that includes changes like files extending from BaseTestCase should now be extending from BaseTestCase5 etc.

Will it be fine if I create a branch from your branch and add my changes on top ?

I am extremely new to this, so please pardon me if I am asking the wrong questions.

[jonahgraham]

Your understanding is correct. Please don't add to my branch, there is too much in it to review in one go.

Instead create new smaller PRs, for example pull out one commit from my branch, make sure it does the expected thing, and make a pr out of it.

Alternatively, convert some tests in other bundles.