Skip to content
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

Simple side test is failing when --auto-open-devtools-for-tabs option is enabled in chrome #1868

Open
NikhilHedau opened this issue Oct 9, 2024 · 0 comments

Comments

@NikhilHedau
Copy link

🐛 Bug Report

I have a side file which is using facebook webpage url. The side test is failing with the below error when --auto-open-devtools-for-tabs is passed , the page loads but the open command is giving an error. If the above option is not passed, test is passing.

This behaviour has been observed in both selenium side runner v3 and v4.

PFB error

`info: Running test facebook-automation
debug: Playing state changed prep for test facebook-automation
debug: Playing state changed playing for test facebook-automation
debug: executing open|/
debug: errored open|/
debug: Playing state changed errored for test facebook-automation
info: Finished test facebook-automation Failure
debug: Last command: {"command":"open","comment":"","id":"6d3bab2f-e92a-4db0-90d5-815faf8531f6","target":"/","targetFallback":[],"value":""}
FAIL ../../../.npm-global/lib/node_modules/selenium-side-runner/dist/main.test.js (60.28 s)
Running project facebook-automation
Running suite Default Suite
✕ Running test facebook-automation (60003 ms)

● Running project facebook-automation › Running suite Default Suite › Running test facebook-automation

ECONNREFUSED connect ECONNREFUSED 127.0.0.1:59998

  at ClientRequest.<anonymous> (node_modules/selenium-webdriver/http/index.js:293:15)

● Running project facebook-automation › Running suite Default Suite › Running test facebook-automation

thrown: "Exceeded timeout of 60000 ms for a test.
Add a timeout value to this test to increase the timeout, if this is a long-running test. See https://jestjs.io/docs/api#testname-fn-timeout."

  at node_modules/jest-each/build/bind.js:47:15
      at Array.forEach (<anonymous>)
  at src/main.test.ts:174:11
      at Array.forEach (<anonymous>)
  at src/main.test.ts:161:22
      at Array.forEach (<anonymous>)
  at Object.<anonymous> (src/main.test.ts:134:18)

Test Suites: 1 failed, 1 total
Tests: 1 failed, 1 total
Snapshots: 0 total
Time: 60.307 s, estimated 61 s
Ran all test suites within paths "/user/.npm-global/lib/node_modules/selenium-side-runner/dist/main.test.js".
`

To Reproduce

selenium-side-runner facebook-automation-v4.side -c "goog:chromeOptions.args=[--auto-open-devtools-for-tabs] browserName=chrome" --debug

Expected behavior

Test should pass

Project file reproducing this issue (highly encouraged)

Attached is the side file .
facebook-automation.txt

Environment

OS: macOs Sonoma 14.5
Selenium IDE Version: 3.17.2
Selenium SIDE Runner Version: 4.0.12
Node version: 20.11.1
Browser: Google-chrome
Browser Version: Version 129.0.6668.101 (Official Build) (arm64)
Chromedriver Version: 129.0.6668.89

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

No branches or pull requests

1 participant