eclipse-windowbuilder / eclipse-windowbuilder/windowbuilder

test_abstractPart_resizeActive fails with 2026-12

Closed
#1,614 3 comments 0 reactions 0 assignees View on GitHub
Dominant language
Java
Stars
97
Forks
34
Avg merge
21h 38m
Merged PRs (30d)
29

Description

Likely something was changed in the Platform with https://github.com/eclipse-simrel/simrel.build/commit/38ed8d6f352bdaa81d8e8fb65dcbb00654f5e130, causing the page layout to now have a different size.

```
org.opentest4j.AssertionFailedError: expected: but was:
at org.junit.jupiter.api.AssertionFailureBuilder.build(AssertionFailureBuilder.java:151)
at org.junit.jupiter.api.AssertionFailureBuilder.buildAndThrow(AssertionFailureBuilder.java:132)
at org.junit.jupiter.api.AssertEquals.failNotEqual(AssertEquals.java:197)
at org.junit.jupiter.api.AssertEquals.assertEquals(AssertEquals.java:182)
at org.junit.jupiter.api.AssertEquals.assertEquals(AssertEquals.java:177)
at org.junit.jupiter.api.Assertions.assertEquals(Assertions.java:1145)
at org.eclipse.wb.tests.designer.core.AbstractJavaTest.assertEditor(AbstractJavaTest.java:273)
at org.eclipse.wb.tests.designer.rcp.RcpModelTest.assertEditor(RcpModelTest.java:126)
at org.eclipse.wb.tests.designer.rcp.model.rcp.PageLayoutTest.test_abstractPart_resizeActive(PageLayoutTest.java:1206)
at java.base/java.lang.reflect.Method.invoke(Method.java:565)
at org.eclipse.wb.tests.designer.core.model.parser.AbstractJavaInfoTest$JavaInfoExtension.interceptTestMethod(AbstractJavaInfoTest.java:88)
at java.base/java.util.ArrayList.forEach(ArrayList.java:1604)
at java.base/java.util.ArrayList.forEach(ArrayList.java:1604)
```

The `CTabFolder` created in this test used to have a width of 585, which is now 592 and thus causing the ratios to be off. Not sure if this is caused by an SWT or an UI change.

Contributor guide

Open the contributing guide

Research direction

Start with PageLayoutTest.test_abstractPart_resizeActive at PageLayoutTest.java:1206 and inspect the failing assertEditor call and its generated CTabFolder dimensions. Compare the expected 0.47 ratio with the observed 0.46 result, then run this test to verify behavior across the affected platform or UI configuration. Done means the test reflects the intended layout behavior and passes reliably.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
desktop, testing
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
68/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.