BrowserMob Proxy

The first thing to do is to go into the "Settings" of the messenger. In the "Data and Memory" section, at the very bottom, are the "Proxy Settings". Activate "Use proxy" and select the protocol SOCKS5, then in the line "Server" write the address and in the line "Port" - the port of the proxy. Since SOCKS5 often uses a system of authentication, you'll need to enter your username and password in the appropriate lines. Sign the result by clicking the checkbox at the top right corner of the screen. When you have connected the proxy to Telegram, don't forget to click "Share" and select the desired contacts.

There are several ways to bypass Telegram blocking, the most popular of which involves installing a proxy. There are bots in the messenger that allow you to get such a working tool, such as @socks_bot, for free. By running the bot and selecting a location to connect, you can get an IP address, port, username and password. To activate the proxy, go through "Settings" to "Data and Drive" and then to "Proxy Settings." After enabling "Use proxy settings", enter the corresponding data in the specified fields.

Most users use A-Parser for this purpose. It is one of the best applications for checking web applications. There is a corresponding tab, "Proxy server", in the standard menu of A-Parser. It is where you can specify the settings for the connection. And in the "Tools" section you can use parameters for parsing.

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.

The proxy domain most often refers to the IP address where the server is located. It can only "learn" the IP address of the user when processing the traffic. But in most cases it does not store such information later for security reasons.