Skip to content

feat: use junit5 platform in our tests#1187

Merged
markdomeng merged 1 commit into
dsldevkit:masterfrom
markdomeng:junit5vintage2
Oct 17, 2025
Merged

feat: use junit5 platform in our tests#1187
markdomeng merged 1 commit into
dsldevkit:masterfrom
markdomeng:junit5vintage2

Conversation

@markdomeng
Copy link
Copy Markdown
Collaborator

use junit-vintage-engine to support junit4 tests

Comment thread ddk-target/ddk.target
@@ -52,6 +52,8 @@
<unit id="org.mockito" version="2.23.0.v20200310-1642"/>
<unit id="org.hamcrest" version="2.2.0.v20210711-0821"/>
<unit id="org.junit" version="4.13.2.v20211018-1956"/>
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

should we not remove now the old junit unit?

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we cant, it is still required to run the vintage engine

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we can remove it as we gradually convert our tests to native junit5

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I have been looking at it and I understand it now. Can we still change a bit the target file to pull a newer junit 5? You can use

  <location includeAllPlatforms="false" includeConfigurePhase="false" includeMode="planner" includeSource="true" type="InstallableUnit">
    <repository location="https://download.eclipse.org/tools/orbit/simrel/maven-osgi/2025-09"/>
    <unit id="junit-jupiter-api" version="5.13.4"/>
    <unit id="junit-vintage-engine" version="5.13.4"/>
  </location>

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

done

Copy link
Copy Markdown
Member

@rubenporras rubenporras left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

should we not remove now the old junit unit?

use junit-vintage-engine to support junit4 tests
@markdomeng markdomeng merged commit dca2fae into dsldevkit:master Oct 17, 2025
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants