The Chrome (version 58) webdriverio is currently inactive, while Firefox is up and running

Question

The Chrome (version 58) webdriverio is currently inactive, while Firefox is up and running

Previously, I successfully ran automation tests on Firefox and Chrome locally. However, there seems to be an issue that has arisen when trying to run them on Chrome recently.

My system configurations:

Operating System: Windows 10 (64-bit)
Chrome Version: 58
Node.js Version: 6.10.3

The specific error I'm encountering in the console while attempting to execute Chrome is:

ERROR: An unknown server-side error occurred while processing the command. (UnknownError:13) Chrome

.

Additionally, in the selenium-server console, I noticed this message:

os.name: 'Windows 10', os.arch: 'amd64', os.version: '10.0', java.version: '1.8.0_121' Driver info: driver.version: unknown

Furthermore, the following details were logged:

Executing: [new session: Capabilities [{rotatable=true, seleniumProtocol=WebDriver, locationContextEnabled=true, loggingPrefs=org.openqa.selenium.logging.LoggingPreferences@8ac8f23, browserName=chrome, javascriptEnabled=true, chromeOptions={args=[--start-maximized, --start-fullscreen]}, handlesAlerts=true, maxInstances=1, requestOrigins={name**=webdriverio, version=4.6.2**, url=}}]]) INFO - Creating a new session for Capabilities [{rotatable=true, seleniumProtocol=WebDriver, locationContextEnabled=true, loggingPrefs=org.openqa.selenium.logging.LoggingPreferences@, browserName=chrome, javascriptEnabled=true, chromeOptions={args=[--start-maximized, --start-fullscreen]}, handlesAlerts=true, maxInstances=1, requestOrigins={name=webdriverio, version=4.6.2, url=}}] ERROR - org.apache.commons.exec.ExecuteException: Process exited with an error: -1073741819 (Exit value: -1073741819) WARN - Exception thrown

The testing framework being used is WebdriverIO, and the test scripts are authored in JavaScript.

Contents of package.json:

dependencies": {
    "chai": "3.5.0",
    "chai-as-promised": "6.0.0",
    ... (remaining content omitted for brevity)

After deleting the node_modules directory and reinstalling via npm locally, the problem persisted.

Interestingly, switching from Chrome to Firefox in the wdio.config.js file allows Firefox to run without issues. A colleague using the same Chrome version faced no such problems.

The console displays webdriverio, version=4.6.2, which differs from the version specified in package.json. Should I opt for an alternative version or pursue another course of action?

Appreciate any insights or advice.

UPDATE: wdio config file

pastebin com/Jd9WrH7B

javascript selenium google-chrome webdriver-io wdio-v4

Answer 1

Answer №1

Below are your options:

1.) If you prefer to continue executing your test cases using npm run <testName> with the latest version ("webdriverio": "4.8.0"), you can follow these steps:

a. Update your global WebdriverIO instance by running:

npm install -g webdriverio@latest

, or

npm install -g <a href="/cdn-cgi/l/email-protection" class="__cf_email__" data-cfemail="ed9a888f899f849b889f8482add9c3d5c3dd">[email protected]</a>

(this will upgrade your global WebdriverIO version to 4.8.0);

b. Alternatively, run your test case with your current WebdriverIO version using:

./node_modules/.bin/wdio <wdioConfigFile>

(in this case wdio.config.js). This command should be executed from your project root folder;

c. Attempt to force updates on your dependencies by running npm update in your project's root directory; (this is more of a Last Resort!).

Note: These methods will only work if you have selenium-standalone configured as a service in your wdio.config.js file (

services: ['selenium-standalone']

).

2.) If problems persist, comment out the selenium-standalone service line from your wdio.config.js file and initiate your own chromedriver selenium-standalone instance:

In your preferred command line interface (e.g., cmd), enter:

java -Dwebdriver.chrome.driver=C:\selenium\chromedriver.exe -jar selenium-server-standalone-3.0.1.jar -port 4444

.

Note: Ensure that you have the most recent chromedriver.exe binary in the same directory where you're starting the server, along with the selenium-standalone .jar file. I usually keep them in C:\selenium\.

Let me know if any of these solutions prove helpful! As mentioned earlier, the error could stem from various reasons, but we're making progress by ruling out possibilities.

Answer 2

Below are your options:

1.) If you prefer to continue executing your test cases using npm run <testName> with the latest version ("webdriverio": "4.8.0"), you can follow these steps:

a. Update your global WebdriverIO instance by running:

npm install -g webdriverio@latest

, or

npm install -g <a href="/cdn-cgi/l/email-protection" class="__cf_email__" data-cfemail="ed9a888f899f849b889f8482add9c3d5c3dd">[email protected]</a>

(this will upgrade your global WebdriverIO version to 4.8.0);

b. Alternatively, run your test case with your current WebdriverIO version using:

./node_modules/.bin/wdio <wdioConfigFile>

(in this case wdio.config.js). This command should be executed from your project root folder;

c. Attempt to force updates on your dependencies by running npm update in your project's root directory; (this is more of a Last Resort!).

Note: These methods will only work if you have selenium-standalone configured as a service in your wdio.config.js file (

services: ['selenium-standalone']

).

2.) If problems persist, comment out the selenium-standalone service line from your wdio.config.js file and initiate your own chromedriver selenium-standalone instance:

In your preferred command line interface (e.g., cmd), enter:

java -Dwebdriver.chrome.driver=C:\selenium\chromedriver.exe -jar selenium-server-standalone-3.0.1.jar -port 4444

.

Note: Ensure that you have the most recent chromedriver.exe binary in the same directory where you're starting the server, along with the selenium-standalone .jar file. I usually keep them in C:\selenium\.

Let me know if any of these solutions prove helpful! As mentioned earlier, the error could stem from various reasons, but we're making progress by ruling out possibilities.

The Chrome (version 58) webdriverio is currently inactive, while Firefox is up and running

Answer №1

Similar questions

Using jQuery to Capture Datepicker Input and Assigning to PHP Variable

Tips for retrieving data from a concealed input within a div that is being looped through in Angular.js

How can I efficiently retrieve the "value" of a cookie and store it in a .txt file using Python?

Filtering a string that contains commas using another string that also contains commas

Generate a fresh array from the existing array and extract various properties to form a child object or sub-array

Building a versatile and interactive table using AngularJS with data sourced from a

Discover the Power of Node.js with the @aws-sdk/client-s3 Package, Leveraging AWS CLI Credentials Stored in

What is the most effective approach to seamlessly conceal and reveal a button with the assistance

The Typescript compiler is unable to locate the module './lib'

Encountering a hydration issue with an SVG element embedded within a Link component in Next

verified firebase/firestore requests

What is the best way to transfer data from one function to another file in React without directly calling the component or using props?

next-pwa seems to be malfunctioning without any discernible errors in the production environment

Customizing the DatePicker with a unique button in material-ui

Is there a way to automatically select all checkboxes when I select contacts in my case using Ionic 2?

The request for data:image/png;base64,{{image}} could not be processed due to an invalid URL

Create a simple carousel using only vanilla JavaScript, without relying on any external plugins

Is it possible to extract tooltip text from a website using Python and Selenium, specifically when the text is generated by JavaScript?

When deployed, Angular 14 and Bootsrap 5 are functioning properly on a local environment but encountering issues on an online

unable to access the object3D within the current scene