Skip to content

Conversation

@HeikoKlare
Copy link
Contributor

Several test cases of VirtualTableViewerTest randomly fail. This includes explicit failures of testRenameWithSorter() and testContains() and silent failures of other test cases that simply return successfully even if the test actually failed. The reason is a missing processing of an update of the table data, which is most likely caused by the shell not having focus.

With this change, the test execution ensures that in cases where an update of the table data is expected, the shell is forced active. In addition, early returns producing silent failures are replaced by assertions leading to explicit failures in case the condition is still not met.

In case tests that previously failed silently now start to fail explicitly despite the changes, I propose to disable them completely (which does make a difference to the current state, see #1583).

Contributes to #1583

May fix #1005

@github-actions
Copy link
Contributor

github-actions bot commented Apr 29, 2024

Test Results

   921 files  ±0     921 suites  ±0   46m 4s ⏱️ - 1m 50s
 7 529 tests ±0   7 379 ✅ ±0  150 💤 ±0  0 ❌ ±0 
23 739 runs  ±0  23 224 ✅ ±0  515 💤 ±0  0 ❌ ±0 

Results for commit 33c75f1. ± Comparison against base commit cdfe96a.

♻️ This comment has been updated with latest results.

@HeikoKlare HeikoKlare marked this pull request as draft April 29, 2024 12:53
@HeikoKlare HeikoKlare force-pushed the issue-1583-virtualtableviewertest branch 4 times, most recently from ba1643e to c89a7de Compare April 29, 2024 17:47
@HeikoKlare HeikoKlare marked this pull request as ready for review April 29, 2024 18:43
@HeikoKlare
Copy link
Contributor Author

Failing test is unrelated and already documented: #1737

…ipse-platform#1005

Several test cases of VirtualTableViewerTest randomly fail. This
includes explicit failures of testRenameWithSorter() and testContains()
and silent failures of other test cases that simply return successfully
even if the test actually failed. The reason is a missing processing of
an update of the table data, which is most likely caused by the shell
not having focus.

With this change, the test execution ensures that in cases where an
update of the table data is expected, the shell is forced active and
events are processed until the data is finally set properly. In
addition, early returns producing silent failures are replaced by
assertions leading to explicit failures in case the condition is still
not met.

Contributes to
eclipse-platform#1583
May fix eclipse-platform#1005
@HeikoKlare HeikoKlare force-pushed the issue-1583-virtualtableviewertest branch from c89a7de to 33c75f1 Compare May 1, 2024 18:10
@HeikoKlare HeikoKlare merged commit 4560024 into eclipse-platform:master May 1, 2024
@HeikoKlare HeikoKlare deleted the issue-1583-virtualtableviewertest branch May 1, 2024 19:46
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.

Random failing VirtualTableViewerTest.testRenameWithSorter and VirtualTableViewerTest.testContains

1 participant