-
Notifications
You must be signed in to change notification settings - Fork 135
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Parameterize browser tests to execute them for Edge browser #671 #672
base: master
Are you sure you want to change the base?
Conversation
Test Results 485 files - 1 485 suites - 1 9m 46s ⏱️ + 2m 39s For more details on these failures, see this check. Results for commit b26001f. ± Comparison against base commit c305b75. This pull request removes 230 and adds 390 tests. Note that renamed tests count towards both.
This pull request removes 5 skipped tests and adds 9 skipped tests. Note that renamed tests count towards both.
♻️ This comment has been updated with latest results. |
abe200b
to
f4ac8dc
Compare
…latform#671 Browser tests were only executed for the default configuration of a system's browser using the SWT.NONE flag. Other configurations, such as using the Edge browser in Windows, were not tested. This change parameterizes the browser tests to also execute them for the Edge browser on Windows. It also deactivates those tests for the Edge browser for which the implementation does (currently) not work. This allows to detect regressions when performing future changes to the Edge browser. Fixes eclipse-platform#672
31c2a39
to
549a829
Compare
if (isEdge) { | ||
// wait for and process pending events to properly cleanup Edge browser resources | ||
do { | ||
processUiEvents(); | ||
try { | ||
Thread.sleep(100); | ||
} catch (InterruptedException e) { | ||
} | ||
} while (Display.getCurrent().readAndDispatch()); | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is necessary because otherwise some OS events that are somehow produced by one test occur and are processed by the next test and may interfere with the Edge browser instantation. I have invested quite some time to identify where the events come from and how to properly handle them, but I did not find a proper way to do so. If someone is able to identify the reasons for the events and how to properly process them, I would be glad to have a better solution than this,
@HeikoKlare can this be merged? |
|
I converted this back to draft due to the recent test failure and I will have another look at it. |
9dd213d
to
b002ced
Compare
4d2a5a1
to
fde88d9
Compare
…latform#671 Browser tests were only executed for the default configuration of a system's browser using the SWT.NONE flag. Other configurations, such as using the Edge browser in Windows, were not tested. This change parameterizes the browser tests to also execute them for the Edge browser on Windows. It also deactivates those tests for the Edge browser for which the implementation does (currently) not work. This allows to detect regressions when performing future changes to the Edge browser. Fixes eclipse-platform#671
ffb43cd
to
b26001f
Compare
b26001f
to
d6640f0
Compare
Browser tests were only executed for the default configuration of a system's browser using the
SWT.NONE
flag. Other configurations, such as using the Edge browser in Windows, were not tested.This change parameterizes the browser tests to also execute them for the Edge browser on Windows. It also deactivates those tests for the Edge browser for which the implementation does (currently) not work. This allows to detect regressions when performing future changes to the Edge browser.
Fixes #671