In Selenium Java, we write something like this
FirefoxOptions options = new FirefoxOptions();
FirefoxBinary firefoxBinary = new FirefoxBinary();
options.addPreference("network.proxy.type", ProxyType.AUTODETECT.ordinal());
options.setBinary(firefoxBinary);
Can some one please help me.
Build info: version: '3.141.59', revision: 'e82be7d358', time: '2018-11-14T08:25:53'
System info: host: '----', ip: '-----', os.name: 'Mac OS X', os.arch: 'x86_64', os.version: '10.15.7', java.version: '15.0.1'
Driver info: driver.version: unknown
[17:38:59] E/launcher - WebDriverError: Timed out waiting for driver server to start.
Build info: version: '3.141.59', revision: 'e82be7d358', time: '2018-11-14T08:25:53'
System info: host: '-------', ip: '----', os.name: 'Mac OS X', os.arch: 'x86_64', os.version: '10.15.7', java.version: '15.0.1'
Driver info: driver.version: unknown
hey Everyone, I started seeing webdriver session not started error since this morning. Here is the exact error I get
[21:02:18] I/direct - Using ChromeDriver directly...
21:02:18 [21:02:18] E/runner - Unable to start a WebDriver session.
21:02:18 [21:02:18] E/launcher - Error: Error: spawn Unknown system error -86
21:02:18 at ChildProcess.spawn (internal/child_process.js:373:11)
21:02:18 at Object.spawn (child_process.js:559:9)
21:02:18 at exec (/usr/local/lib/node_modules/protractor/node_modules/selenium-webdriver/io/exec.js:116:27)
21:02:18 at resolveCommandLineFlags.then.args (/usr/local/lib/node_modules/protractor/node_modules/selenium-webdriver/remote/index.js:219:25)
21:02:18 at processTicksAndRejections (internal/process/task_queues.js:86:5)
21:02:18 [21:02:18] E/launcher - Process exited with error code 100I am using directConnect:true config and, chromedriver path I have provided was working till yesterday without any change. What am I missing? I appreciate any help in advance. Thanks
This has been published to npm as version 12.1.8. After updating to version 12.1.8, you will need to run webdriver-manager clean before running webdriver-manager update.
See https://stackoverflow.com/questions/65609111/getting-driver-info-driver-version-unknown-while-running-scripts-using-protr/65638301#65638301 and angular/webdriver-manager#478
6 replies
hey everyone, my protractor tests were working fine on version 7 and wedriver-version 12.1.8 so far but after today I suddenly started seeing this error. The individual jasmine specs seems to pass but I did not get this error until today.
(node:75637) UnhandledPromiseRejectionWarning: Error: Error while waiting for Protractor to sync with the page: "both angularJS testability and angular testability are undefined. This could be either because this is a non-angular page or because your test involves client-side navigation, which can interfere with Protractor's bootstrapping. See http://git.io/v4gXM for details"
at runWaitForAngularScript.then (/Users/sukthankar/Documents/manager_web_test_automation/node_modules/protractor/built/browser.js:463:23)
at process._tickCallback (internal/process/next_tick.js:68:7)
(node:75637) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with.catch(). (rejection id: 1)
(node:75637) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
(node:75637) UnhandledPromiseRejectionWarning: Error: Error while waiting for Protractor to sync with the page: "both angularJS testability and angular testability are undefined. This could be either because this is a non-angular page or because your test involves client-side navigation, which can interfere with Protractor's bootstrapping. See http://git.io/v4gXM for details"
at runWaitForAngularScript.then (/Users/sukthankar/Documents/manager_web_test_automation/node_modules/protractor/built/browser.js:463:23)
at process._tickCallback (internal/process/next_tick.js:68:7)
(node:75637) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with.catch(). (rejection id: 2)also seeing json formatting error on my tsconfig.json under node_modules/protractor. wondering if that is related. I am using waitForAngular(false) before my tests run since we have outstanding http requests that keep polling as a part of our app. If there any workaround for the above error, please let me know. Thanks.
Probably will have more info some time Q2-ish?
Hi Craig. Will this include a roadmap to support for Selenium 4?
In my organization we are at a point where we have to decide whether we give up on Protractor and migrate to other tools (like MS Playwright). We see the risk that modern browsers will not support JsonWire anymore but only W3C WebDriver protocol, forcing us to use Selenium 4 based tooling.
1 reply
Hello. I hope you're all well. Please may somebody assist.
I have been using the browser.actions().mouseMove(el, {x: 0, y: 150}) to attempt to scroll within a div on a page, but the offset isn't working...
I have a fixed footer, hence the reason I need a vertical offset, however it just ignores the y offset completely. There is more than enough feed below the element to scroll.
Oddly a negative value does work.
I have also attempted to use browser.wait(ec.visibilityOf(ef), 10000).then(() => //logic), however the promise resolves without the element being visible within the viewport... so I'm guessing that this is evaluating the theoretical visibility according to the painted presence of the element, and doesn't account for the viewport.
Why is scrolling such a problem? This seems like it should be a common issue, but I'm not finding much info surrounding scrolling in Protractor's actions wrapper API implementation.
Is it just me? You can be honest. Haha.
Do you maybe know if w3c mode is implicitly enabled in these later versions?
chromeOptions: { w3c: false } worked fine. With the 3.141.59-20210311 images it no longer works. I had to switch to 'goog:chromeOptions': { w3c: false } before I could get it to work again.
protractor-cucumber-framework on any of your projects, then please upgrade it to version 8.0.0. This latest version has replaced the old integration and reporting engine with Serenity/JS while retaining backwards compatibility. You'll also get support for Cucumber.js v 7 (and all the previous ones), as well as support for both the native Cucumber.js reporters and Serenity/JS reporters. Thoughts and feedback welcome! I typically hang out on the Serenity/JS channel - https://gitter.im/serenity-js/Lobby
25 replies