Skip to content

Migrate JUnit 4 tests to JUnit 5 in org.eclipse.jface.tests#3412

Merged
akurtakov merged 2 commits into
eclipse-platform:masterfrom
vogella:simple-jface-tests-junit5
Oct 19, 2025
Merged

Migrate JUnit 4 tests to JUnit 5 in org.eclipse.jface.tests#3412
akurtakov merged 2 commits into
eclipse-platform:masterfrom
vogella:simple-jface-tests-junit5

Conversation

@vogella
Copy link
Copy Markdown
Contributor

@vogella vogella commented Oct 17, 2025

No description provided.

@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented Oct 17, 2025

Test Results

 3 018 files  ±0   3 018 suites  ±0   2h 23m 54s ⏱️ - 11m 8s
 8 226 tests ±0   7 977 ✅ ±0  249 💤 ±0  0 ❌ ±0 
23 598 runs  ±0  22 804 ✅ ±0  794 💤 ±0  0 ❌ ±0 

Results for commit a2b56b5. ± Comparison against base commit 8ff6a17.

♻️ This comment has been updated with latest results.

This commit fixes compilation and test failures introduced during the
JUnit 4 to JUnit 5 migration in org.eclipse.jface.tests.

Changes:
- Added missing import for org.junit.jupiter.api.function package in
  MANIFEST.MF to resolve NoClassDefFoundError for Executable class
  used by assertThrows() in LabelProviderTest
- Fixed assertEquals parameter order in Bug205700TreeViewerTest to match
  JUnit 5 signature: assertEquals(expected, actual, message)
- Fixed assertEquals parameter order in WizardProgressMonitorTest to match
  JUnit 5 signature: assertEquals(expected, actual, message)

The JUnit 5 assertEquals method has a different parameter order than
JUnit 4. In JUnit 4 it was assertEquals(message, expected, actual) but
in JUnit 5 it is assertEquals(expected, actual, message).

All 1298 tests now pass successfully (0 failures, 0 errors, 3 skipped).

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
@vogella
Copy link
Copy Markdown
Contributor Author

vogella commented Oct 18, 2025

LGTM

@akurtakov akurtakov merged commit 554e227 into eclipse-platform:master Oct 19, 2025
18 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.

2 participants