Gin Trusted Proxies

Find a working proxy and start installing it in the messenger. Telegram has bots that allow you to get several proxies for free, including @socks5_bot. When you launch it, once the location is selected, you'll get an IP address, port, username and password. Go through "Settings" to "Data and Disk" and then to "Proxy Settings" and enter the required data in the highlighted fields: server, port, username and password.

Such proxy redirects requests from clients to different servers (globally or within a single local network). It can be used for load balancing in different Internet services, for testing web applications, for secured access to local network servers (all "non-client" traffic is ignored).

To simulate a click during scraping, you can use a headless browser automation library like Puppeteer for Node.js. Puppeteer provides a high-level API to control headless browsers, allowing you to automate tasks such as clicking on elements, filling out forms, and navigating through pages.

Here's a basic example of how you can use Puppeteer to simulate a click:

1. Install Puppeteer:

   • Install Puppeteer using npm:

npm install puppeteer

Write the Scraping Script:

• Create a Node.js script (e.g., scrape_with_click.js) with the following code:

const puppeteer = require('puppeteer');

async function scrapeWithClick() {
    const browser = await puppeteer.launch();
    const page = await browser.newPage();

    try {
        // Navigate to the target URL
        await page.goto('https://example.com');

        // Wait for a specific selector to appear (replace with the selector of the element you want to click)
        const elementSelector = 'button#exampleButton';
        await page.waitForSelector(elementSelector);

        // Simulate a click on the specified element
        await page.click(elementSelector);

        // Wait for the page to settle (replace with additional logic if needed)
        await page.waitForTimeout(2000);

        // Extract and print information after the click
        const extractedInfo = await page.evaluate(() => {
            // Replace this with your logic to extract information from the clicked page
            return document.title;
        });

        console.log('Extracted information after click:', extractedInfo);
    } catch (error) {
        console.error('Error during scraping:', error);
    } finally {
        // Close the browser
        await browser.close();
    }
}

// Run the scraping script
scrapeWithClick();

• • Replace 'https://example.com' with the URL you want to scrape.

  • Replace 'button#exampleButton' with the selector of the element you want to click.

• Run the Script:

  • Run the script using Node.js:

node scrape_with_click.js

This script uses Puppeteer to launch a headless browser, navigate to a specified URL, wait for a specific element to appear, simulate a click on that element, and then perform additional actions or extractions as needed.

Make sure to handle errors and adjust the script based on the structure of the website you are scraping.

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.

Proxy "tunneling" should be understood as the isolation of traffic from the user. It allows you to form a fully protected channel for data exchange, which will be isolated from all other traffic.