docker-selenium VS Selenium WebDriver

Edit: I got some parts of it running. This video is very helpful. I gave up on the official docker repository for change detection io and switched to the LSIO version. I had to first install and run the docker Selenium container (available here). I installed the standalone version of Chrome from that page. Now I added one line to the docker-compose.yml in the environment section (as mentioned in the video. I did not add BASE_URL) and that was "WEBDRIVER_URL=http://192.168.1.15:4444" (this has to be an actual IP address, can't use "localhost" or anything else. I redeployed the container and the webdriver worked.

Selenium with Docker Selenium Grid https://github.com/SeleniumHQ/docker-selenium. Isolated and scalable.

Next is the image that we are using to run the docker command. Here we are using the Selenium Firefox standalone image with tag 4.0.0-rc-1-prerelease-20210618. More information about the latest versions available can be found from the official Selenium Github repository and the Docker hub public registry.

If you run your own, you need to account for your computer's processing power. That is the bottleneck. Check out this repo for more info. https://github.com/SeleniumHQ/docker-selenium

Same. I had sucess with https://github.com/SeleniumHQ/docker-selenium

If you look on selenium's dockerhub, there are many images to chose from which are much newer. As far as I'm concerned, that image is abandoned and I would definitely not use it. Not saying it is the reason for whatever happened to you, but kind of shocking that change detection is recommending it.

Playwright has a limitation that restricts running tests in Selenium Grid to only the version prior to 4.5.2-20221021 (at the time of this writing - February/2023).

I literally clicked on your link, followed the instructions and found this.

Selenium is an extensively used open-source automation framework for web applications. It allows for cross-browser testing by automating browser actions, making it a staple tool for end-to-end testing in diverse web development environments.

While similar to Puppeteer, Cypress, and Selenium, there are some differences. Let’s find out what they are.

browser.get('http://selenium.dev/')

Cypress is a next-generation front-end Automation testing tool built for modern web applications. It is a JavaScript-based end-to-end testing framework and is known for faster test execution as compared with other testing tools (like Selenium or Protractor).

Removing ExpectedConditions from documentation makes sense since it was removed from the codebase around 2019 already.

https://github.com/SeleniumHQ/selenium --> trunk

You won't be able to test the javascript function itself from within python, but you can exercise the front-end code using something like cypress (https://cypress.io) or the older but still respectable selenium (https://selenium.dev).

once you solve this you may run into: https://github.com/SeleniumHQ/selenium/issues/11750, so add that workaround.

Other libraries with similar functionality are Selenium, which is very popular outside the JavaScript world, and Playwright, a younger step-brother of Puppeteer.

🔗 https://selenium.dev