Share Proxy

To run GUI autotests in GitLab CI\CD using Docker, Selenium, and PyTest, you can follow these steps:

1. Create a .gitlab-ci.yml file in the root directory of your project. This file will define the pipeline and the jobs for your CI\CD process.

2. Configure the pipeline to use the appropriate image for your tests. In this case, you can use a Python image with the required dependencies installed.

3. Define the before_script section to set up the environment for the tests, including installing the necessary packages and downloading the required drivers for Selenium.

4. Define the test job to run the PyTest tests using the Selenium WebDriver.

Here's an example of a .gitlab-ci.yml file:

stages:
  - test

variables:
  SELENIUM_CHROME_DRIVER: '102.0.5005.62'
  SELENIUM_FIREFOX_DRIVER: '0.26.0'

image: python:3.8

cache:
  paths:
    - .venv
    - requirements.txt

before_script:
  - apt-get update -qq
  - apt-get install -y --no-install-recommends \
      build-essential \
      wget \
      xvfb \
      xvfb-run
  - pip install --upgrade pip
  - pip install --quiet --upgrade pytest
  - pip install --quiet selenium
  - pip install --quiet webdriver-manager
  - wget https://github.com/SeleniumHQ/selenium/releases/download/v${SELENIUM_CHROME_DRIVER}/chromedriver_linux64.zip
  - unzip chromedriver_linux64.zip chromedriver
  - wget https://github.com/SeleniumHQ/selenium/releases/download/v${SELENIUM_FIREFOX_DRIVER}/geckodriver-v${SELENIUM_FIREFOX_DRIVER}
  - mv geckodriver-v${SELENIUM_FIREFOX_DRIVER} geckodriver

test:
  stage: test
  script:
    - pytest tests/
  tags:
    - selenium
  artifacts:
    reports:
      - html
  only:
    - master
    - merge_requests

This .gitlab-ci.yml file defines a single stage called test that runs the PyTest tests in the tests/ directory. The before_script section installs the necessary dependencies, downloads the Selenium WebDriver for Chrome and Firefox, and sets up the environment for running the tests.

The tags: - selenium line ensures that the job runs on a runner with the selenium tag, which should have the appropriate Selenium WebDriver installed. The artifacts: reports: - html line enables the generation of HTML reports for the test results.

The only: - master - merge_requests line specifies that the tests should be run on every commit to the master branch and on every merge request.

Once you've set up the .gitlab-ci.yml file, commit and push it to your repository. Then, create a new merge request or push to the master branch to trigger the CI\CD pipeline and run the GUI autotests using Docker, Selenium, and PyTest.

Selenium is a popular tool for automating web browser interactions, but it does not have built-in support for interacting with browser push notifications. Push notifications are a feature of the browser itself, and Selenium operates at a lower level, interacting with the Document Object Model (DOM) and simulating user actions.

However, you can use Selenium in combination with JavaScript to interact with push notifications. Here's a step-by-step guide on how to do this:

Here's an example Python script using Selenium and the Chrome WebDriver that demonstrates these steps:

from selenium import webdriver
from selenium.webdriver.common.by import By
from selenium.webdriver.support.ui import WebDriverWait
from selenium.webdriver.support import expected_conditions as EC

# Set up the Chrome WebDriver
driver = webdriver.Chrome()

# Navigate to the website that triggers the push notification
driver.get("https://example.com")

# Wait for the push notification to appear
wait = WebDriverWait(driver, 10)
push_notification = wait.until(EC.presence_of_element_located((By.CSS_SELECTOR, "div.push-notification")))

# Execute JavaScript to click the push notification
driver.execute_script("arguments[0].click();", push_notification)

# Perform any additional actions after clicking the push notification
# ...

# Close the browser
driver.quit()

Please replace the "div.push-notification" CSS selector with the appropriate selector for the push notification element on the website you are working with. Also, make sure to adjust the wait time (10 seconds in this example) as needed for the push notification to appear.

Keep in mind that this approach relies on executing JavaScript code, which can be more brittle than using Selenium's native methods. It's essential to handle exceptions and edge cases, such as the push notification not appearing within the expected time frame.

You can check the validity of proxies by using special software and a proxy checker. These tools not only check if the proxy is working, but also inform you about possible blocking by various platforms and social networks. Online services (checkers) also provide information related to ping, speed, proxy anonymity level, and geo. The combination of all these data allows for the most objective assessment of a proxy server's performance.

Open the Chrome preferences screen, and then, expanding the advanced settings menu, click on the "Advanced" section. Open the "System" item, then on the tab that opens, click on "Open proxy settings for computer". The proxy settings interface will appear in front of you. This will be either the "System Settings" application or the "Browser Properties" application, depending on your operating system.

Simply, in the connection properties of your PC or mobile device, you need to enter the data of the proxy server through which you will be connecting. In Windows, for example, this is done through "Settings", then "Network and Internet", and in the next window you should open the tab "Proxy server".