webdriver-manager | A binary manager for E2E | Functional Testing library

I was following the tutorial from here and it still says ModuleNotFoundError: No module named 'webdriver_manager', even after installing webdrivermanager in multiple ways, already recommended in other posts on stackoverflow. I tried pip install webdriver-manager, pip install webdriver_manager and pip install webdrivermanager, yet nothing seems to work.

Edit: It seems to work on my Laptop, so I think It could be a wrong install of the libary... any suggestions on what I should do?

I'm moving my test project from Selenium 3 to Selenium 4 and I'm getting warnings about "executable_path" deprecation. I couldn't find the proper way to use webdriver_manager for Firefox with Selenium 4 so I'm still using the "executable_path". They also haven't updated their doc here: https://pypi.org/project/webdriver-manager/

I am working on a nodejs project that has some End to End tests. The test are running fine on my local and it failing from my gitlab pipeline because of webdriver was not recognized.

I tried installing webdriver in couple of different ways like Protractor but not fixed my issues. Any help would be appriciated.

Here is my gitlab-ci.yml file

stages:

• build
• test

before_script:

• npm install # install npm packages
• npm install protractor -g

build:

stage: build

script:

I am trying to click the first YouTube channel on the top of the result page. My code is as follows.

I'm new to the protractor. I created a project with angular and its works fine without docker. However, when I build the image it's successfully created. Unfortunately unable to run that one.

Folder : protractor Contents below

Recently I spent quite a time to start e2e test to my project and incorporate it into build pipeline. A setup requires at least 2 nodes (mongodb + .Net5 backend with Angular client) so it is been decided to run all of this in docker. I've added additional docker-compose-test.yml where I'll start temporary nodes to run server integration tests (that needs mongo) and then client tests including e2e (that needs completely working setup). So after days of tuning all of this I ended up with a protractor.conf.js that have a chromeDriver hardcoded for docker:

I have created a docker-compose.yml file to run some protractor tests that are stored in a public repo. There are several containers created in the yml file:

• shared_repo: where tests are cloned.
• selenium-hub: container with a selenium image.
• chrome: container with a selenium/node-chrome-debug.
• protractor: container with a node:12.14 image

Docker-compose file is:

I am running a process with Selenium and handling as many errors as I can and creating custom exceptions for few, but I have an issue if unexpected error does occur within process Selenium will keep running and take up resources/ram unless explicitly shut down, is there a better way to handle it than wrapping everything around try except and within except shutting down Selenium? much thanks

I would like to have some kind of "signal" in case error occurs send error to sentry io and free ram space from Selenium

simple example

I am trying to run protractor test on Azure DevOps pipeline and getting the following error. Notice that jar file path is pointing to my local drive even when the tests are being run from Azure DevOps server. Any idea what I need to do?

Same test works when running from local machine but fails on Azure. I have the selenium-server-standalone-3.141.59.jar in my project's node_modules folder. What I don't understand is that why is it looking at my local machine (C:\Automation) when I am running test from Azure.