chore(e2e): fix wdio config for Chrome #2251
Merged
+34
−65
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
smalluban
force-pushed
the
fix-wdio
branch
15 times, most recently
from
981be67 to
5d3a5f2
Compare
chrmod
approved these changes
Feb 17, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The recent update of Chrome introduced a problem with the
browser.switchWindow()API, which closes the whole browser and makes tests fail immediately after.I tried many different approaches (from temporarily fixed Chrome version - v131 and older passes tests) to try to avoid the bug/feature of Chrome, but without success. However, the root problem is that the onboarding page automatically opens after an extension is installed. If we disable the automatic opening of that page, we can fix the issue using the latest Chrome.
I have used the
--debugmode of the extension build to add conditions in the background to prevent onboarding from opening automatically. It is pointless to create a separate flag for it.The good side-effect of using debug mode is sending telemetry signals to dev env, so for example
engagedsignals are not saved on prod (which can be many during a day, as every run of tests sends this signal).