Going back to the latest stable VS Code version to perform e2e tests #1623
Conversation
pastuxso
force-pushed
the
revert-1622-cris/tests-vscode-1.92.2
branch
from
250b2b6
to
17bedf2
Compare
|
pastuxso
changed the title
pastuxso
force-pushed
the
revert-1622-cris/tests-vscode-1.92.2
branch
from
e5bf028
to
8afc2b4
Compare
This reverts commit d2d4ce9.
This reverts commit 17bedf2.
Bumps the e2e-tests group with 1 update in the / directory: [chromedriver](https://github.com/giggio/node-chromedriver). Updates `chromedriver` from 128.0.3 to 129.0.0 - [Commits](giggio/node-chromedriver@128.0.3...129.0.0) --- updated-dependencies: - dependency-name: chromedriver dependency-type: direct:development update-type: version-update:semver-major dependency-group: e2e-tests ... Signed-off-by: dependabot[bot] <[email protected]>
pastuxso
force-pushed
the
revert-1622-cris/tests-vscode-1.92.2
branch
from
d1d5a5b
to
2c2d324
Compare
|
🤔, we want to make changes to the lifecycle ID stuff soon. So I'd say let's continue to run tests against the old version of vscode and consider disabling the relevant tests in favor of running against |
|
@sourishkrout Let's keep it open, I'll do a follow-up next week. For now, main is running using the v1.92.2, so no changes are necessary. I'll convert it to draft again. |
|
@pastuxso @sourishkrout , regarding this issue "It seems that the command > Developer: Reload Window is generating a disconnection between the test runner and the chromedriver. ", do you know if this will be fixed anytime soon? |
Hi @diyer! No, we don't. For now, We are using the 1.92.2. |
It seems that the command
> Developer: Reload Windowis generating a disconnection between the test runner and the chromedriver. This step is required to test Lifecycle Identity e2e Tests using different combinations of settings.This PR refactors the Lifecycle ID e2e tests to avoid the usage of Window Reloading and enabled the latest version again.
Reverts #1622
Related: webdriverio-community/wdio-vscode-service#136