driver.js | vanilla JavaScript engine to drive the user 's focus | Animation library

The actual problem was that there was a condition part in the protractor configuration file that overwrite my headless option :( so a stupid problem.

Not coming out of it so that it runs the next command to start test.

The net command is the task Run Test Cases, right? If yes, we could click the task and expand the tab Control Options and ensure the field Run this task is set to Even if a previous task has failed, unless the build was canceled.

Then if the task Webdriver Start fails, the pipeline will continue to run the next task Run Test Cases.

Update1

Not coming out of it so that it runs the next command to start test.

The initial problem has been solved.

Since you have not started or webdriver not get started correctly, we could see the error issue: ECONNREFUSED connect ECONNREFUSED 127.0.0.1:4444. If the previous task successfully runs Webdriver, we will not see the error message.

We need ensure the Webdriver start and then run the Protractor test.

According the doc: Microsoft Windows Server 2019 Datacenter and Ubuntu 20.04.2 LTS. We find there is only ChromeDriver 88.0.4324.96 on our hosted agent.

So we have two suggestions:

1. We noticed that the test is working well on your local machine, so we can try to install a self-agent in your local machine and use the new agent to try again.

2. We can add a bash task and use the below the script to install latest version of the ChromeDriver first.

   npm install chromedriver --chromedriver_cdnurl=https://chromedriver.storage.googleapis.com/89.0.4389.23/chromedriver_win32.zip

you can turn off ssl validation as

Within Locator Strategies . is interpreted differently, maorly to denote classnames. Hence the error.

You can change the Class By from:

Solved in webdriver-manager@12.1.8

Make sure to install it globally and locally

Your CSP has errors:

• a double default-src directives, the second one will be ignored.
• in the part 'unsafe-inline'; https://*.googleapis/*/ https://*.fontawesome.com/*/ the directive name is missed, therefore browser counts a https://*.googleapis/*/ and https://*.fontawesome.com/*/ host-sources as directive's names'. The ; is a separator for directives, therefore after 'unsafe-inline'; a directive name should follow.
• https://*.googleapis/*/ and https://*.fontawesome.com/*/ have invalid syntax because * is not allowed in the path-part or to cover top level domain zone, pls see how to correctly specify host-source.

I an not sure about gap: and content: scheme-sources, they not used in ordinary CSP, but they may be applicable in CSP for browser extensions.

I encounter the same error this morning and found that the fix was to run:
webdriver-manager update
npm install --force protractor
There was a fix to this issue in the latest webddriver-manager update. You'll need to force a dependency update on protractor for it to use the latest webdriver-manager

Finally, I fixed the issue by editing node_modules/webdriver-manager/built/lib/files/file_manager.js

Update file_manager.js #line-no-166 fileUrl.url = fileUrl.url.replace(/_m1/, '');

Github issue: https://github.com/angular/webdriver-manager/issues/476