[🐛 Bug]: Test not starting on v8

See original GitHub issue

Have you read the Contributing Guidelines on issues?

I have read the Contributing Guidelines on issues.

WebdriverIO Version

Node.js Version

16.13.2

Mode

Standalone Mode

Which capabilities are you using?

No response

What happened?

Trying to migrate from v7 to v8. The tests start and get stuck without any error.

My dependencies

"@wdio/allure-reporter": "^8.0.0",
"@wdio/appium-service": "^8.0.0",
"@wdio/cli": "^8.0.0",
"@wdio/local-runner": "^8.0.0",
"@wdio/mocha-framework": "^8.0.0",
"@wdio/selenium-standalone-service": "^8.0.0",
"@wdio/spec-reporter": "^8.0.0",

What is your expected behavior?

Test should run just as they did with v7

How to reproduce the bug.

Setup a fresh webriver.io project with v8 and run the test scripts

Relevant log output

`2022-12-02T10:07:44.576Z DEBUG @wdio/utils:initialiseServices: initialise service "chromedriver" as NPM package
2022-12-02T10:07:44.579Z INFO @wdio/cli:launcher: Run onPrepare hook
Initializing Chrome Service With Port - 5010
2022-12-02T10:07:44.605Z INFO chromedriver: Initiate Chromedriver Launcher (v8.0.0)
2022-12-02T10:07:44.608Z INFO chromedriver: Start Chromedriver (/Users/reshail/lean-test-framework/node_modules/chromedriver/lib/chromedriver/chromedriver) with args --port=5010 --url-base=/
2022-12-02T10:07:44.629Z INFO chromedriver: Starting ChromeDriver 107.0.5304.62 (1eec40d3a5764881c92085aaee66d25075c159aa-refs/branch-heads/5304@{#942}) on port 5010
2022-12-02T10:07:44.630Z INFO chromedriver: Only local connections are allowed.
2022-12-02T10:07:44.631Z INFO chromedriver: Please see https://chromedriver.chromium.org/security-considerations for suggestions on keeping ChromeDriver safe.
2022-12-02T10:07:44.631Z INFO chromedriver: ChromeDriver was started successfully.
2022-12-02T10:07:44.724Z DEBUG @wdio/cli:utils: Finished to run "onPrepare" hook in 144ms
2022-12-02T10:07:44.727Z INFO @wdio/cli:launcher: Run onWorkerStart hook
2022-12-02T10:07:44.727Z DEBUG @wdio/cli:utils: Finished to run "onWorkerStart" hook in 0ms
2022-12-02T10:07:44.728Z INFO @wdio/local-runner: Start worker 0-0 with arg: run,config/wdio.conf.js`

When I force quit it

Ended WebDriver sessions gracefully after a SIGINT signal was received!
2022-12-02T10:12:15.904Z INFO @wdio/local-runner: Shutting down spawned worker
[0-0] 2022-12-02T10:12:15.904Z INFO @wdio/local-runner: Received SIGINT, giving process 5000ms to shutdown gracefully
[0-0] 2022-12-02T10:12:15.907Z INFO @wdio/local-runner: Run worker command: endSession
[0-0] 2022-12-02T10:12:15.908Z ERROR @wdio/local-runner: Failed launching test session: TypeError: Cannot read properties of undefined (reading 'sessionId')
[0-0]     at Runner.endSession (file:///Users/reshail/lean-test-framework/node_modules/@wdio/runner/build/index.js:364:50)
[0-0]     at process.<anonymous> (file:///Users/reshail/lean-test-framework/node_modules/@wdio/local-runner/build/run.js:18:22)
[0-0]     at process.emit (node:events:402:35)
[0-0]     at process.emit (node:domain:475:12)
[0-0]     at emit (node:internal/child_process:917:12)
[0-0]     at processTicksAndRejections (node:internal/process/task_queues:84:21)
2022-12-02T10:12:15.926Z DEBUG @wdio/local-runner: Runner 0-0 finished with exit code 1

Code of Conduct

I agree to follow this project’s Code of Conduct

Is there an existing issue for this?

I have searched the existing issues

Issue Analytics

State:
Created 10 months ago
Comments:19 (12 by maintainers)

Top GitHub Comments

1reaction

Diazolecommented, Dec 8, 2022

@sankalpguptasymphony I fixed it in 8.0.8 - https://github.com/webdriverio/webdriverio/pull/9339

1reaction

Diazolecommented, Dec 6, 2022

I am also receiving Error - SeleniumStandalone.start is not a function on v8.

2022-12-06T11:22:07.159Z DEBUG @wdio/utils:initialiseServices: initialise service "selenium-standalone" as NPM package
2022-12-06T11:22:07.253Z DEBUG @wdio/utils:initialiseServices: initialise service "selenium-standalone" as NPM package
2022-12-06T11:22:07.253Z INFO @wdio/cli:launcher: Run onPrepare hook
2022-12-06T11:22:07.766Z ERROR @wdio/cli:utils: A service failed in the 'onPrepare' hook
TypeError: SeleniumStandalone.start is not a function
    at SeleniumStandaloneLauncher.onPrepare (file:///.../@wdio/selenium-standalone-service/build/launcher.js:92:42)
    at async file:///.../@wdio/cli/build/utils.js:42:17
    at async Promise.all (index 0)
    at async Launcher.run (file:///.../@wdio/cli/build/launcher.js:82:13)

npm init wdio@latest . produces the same error.

Top Results From Across the Web

[ 🐛 Bug]: Getting Started does not work on Windows 10 #9289

I expected the setup to run without error and an example test to run. How to reproduce the bug. To reproduce the bug...

V8, run-tests.py fails - Stack Overflow

there are 2 bugs in the date-format/format-test.js: 1. in javascript, month starts from 0, 2. UTC time should be used to create the...

Version 8.x - Katalon Docs

[Bug] The web service keyword getElementText was not working properly. [Bug] [Mobile] When configuring test suites inside a test suite collection to run ......

Release Notes | Firebase - Google

arm in the Firebase console. To learn more, see Start testing with Android Virtual Devices. August 10, 2022. SDK Releases.

Apache Tomcat 8 (8.5.84) - Changelog

Fix a bug in MethodExpression handling that triggered an error when ... modified some TLS configurations when running on a Java 8 JDK....