Skip to content

Conversation

@HeikoKlare
Copy link
Contributor

Hamcrest is available by default when using JUnit 4. With JUnit 5, Hamcrest has to be required as an additional dependency. At the same time, we already have a dependency to the more up-to-date AssertJ library. For that reason, this change adapts the last remaining Hamcrest usage in resource tests, a matcher for marker severities, with an equivalent assertion based on AssertJ.

Hamcrest is available by default when using JUnit 4. With JUnit 5,
Hamcrest has to be required as an additional dependency. At the same
time, we already have a dependency to the more up-to-date AssertJ
library. For that reason, this change adapts the last remaining Hamcrest
usage in resource tests, a matcher for marker severities, with an
equivalent assertion based on AssertJ.
@github-actions
Copy link
Contributor

github-actions bot commented Jan 3, 2026

Test Results

 1 953 files  ±0   1 953 suites  ±0   1h 22m 51s ⏱️ - 10m 49s
 4 743 tests ±0   4 719 ✅ ±0   24 💤 ±0  0 ❌ ±0 
14 229 runs  ±0  14 047 ✅ ±0  182 💤 ±0  0 ❌ ±0 

Results for commit 3b6049f. ± Comparison against base commit 04f2b2d.

@HeikoKlare HeikoKlare merged commit 80a8ab8 into eclipse-platform:master Jan 3, 2026
18 checks passed
@HeikoKlare HeikoKlare deleted the junit5-resourcetests-hamcrest branch January 3, 2026 12:09
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.

1 participant