Skip to content

Conversation

@HeikoKlare
Copy link
Contributor

@HeikoKlare HeikoKlare commented Dec 30, 2025

The custom AssertionFailedErrors specified in org.eclipse.core.tests.harness are derived from JUnit 3/4's AssertionFailedError coming from org.junit. In order to fully migrate the test harness to JUnit 5, this change adapts those classes to subclass the AssertionFailedError from org.opentest4j as done by JUnit 5 as well.

Contributes to #903

Requires #2350

@github-actions
Copy link
Contributor

github-actions bot commented Dec 30, 2025

Test Results

 1 953 files  ±0   1 953 suites  ±0   1h 26m 4s ⏱️ +57s
 4 745 tests ±0   4 721 ✅ ±0   24 💤 ±0  0 ❌ ±0 
14 235 runs  ±0  14 053 ✅ ±0  182 💤 ±0  0 ❌ ±0 

Results for commit 68d2734. ± Comparison against base commit e190abb.

♻️ This comment has been updated with latest results.

The custom AssertionFailedErrors specified in
org.eclipse.core.tests.harness are derived from JUnit 3/4's
AssertionFailedError coming from org.junit. In order to fully migrate
the test harness to JUnit 5, this change adapts those classes to
subclass the AssertionFailedError from org.opentest4j as done by JUnit 5
as well.

Contributes to
eclipse-platform#903
@HeikoKlare HeikoKlare force-pushed the assertionfailederror-tests.harness branch from d8ecf0f to 68d2734 Compare December 30, 2025 17:40
@HeikoKlare HeikoKlare merged commit 09f89e4 into eclipse-platform:master Dec 30, 2025
18 checks passed
@HeikoKlare HeikoKlare deleted the assertionfailederror-tests.harness branch December 30, 2025 18:22
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