testeiya 0.2.1 → 0.3.10

package/skills/testeiya/testomatio-docs/docs/integrations/continuous-integration/circle.md

@@ -1,115 +0,0 @@
----
-title: Circle CI
-description: Integrate CircleCI with Testomat.io to automate test execution and reporting. This guide explains configuring the config.yml workflow, setting parameters, and passing environment variables for streamlined CI integration. It covers running tests via the Testomat.io interface and accessing test reports post-execution.
-type: article
-url: https://docs.testomat.io/integrations/continuous-integration/circle
-head:    
-  - tag: meta
-    attrs:
-      name: keywords
-      content: Circle CI, Testomat.io, CI connection, CI Integration, CircleCI workflow, Personal API Token, Continuous Integration, Test Automation, Test Management, input variables, configuration, Circle CI Trigger URL
----
-
-To connect Circle CI to Testomat.io, lets start with configuring your Circle CI:
-
-1. Create an access token on Circle CI by following [the instuctions by link](https://circleci.com/docs/managing-api-tokens/#creating-a-personal-api-token).
-
-![Testomat.io - CircleCI](./images/CircleCI_1.png)
-
-2. Create a workflow in `config.yml` file in `.circle` folder in the root folder in your repository.
-
-3. This workflow will be used solely by Testomat.io so it should start only on `workflow_dispatch` event. The event should be defined with the following input parameters:
-
-```
-parameters:
-  testomatio:
-    type: string
-    default: ""
-
-  run:
-    type: string
-    default: ""
-
-  testomatio_url:
-    type: string
-    default: ""
-
-  grep:
-    type: string
-    default: ""
-
-```
-
-4. The **Job** should include a step where the test runner is executed with `--grep` option and `TESTOMATIO` environment variables passed in. 
-For instance:
-
- ```
-      - run:
-          name: Run tests
-          command: npx codeceptjs run --grep "<< pipeline.parameters.grep >>"
-          environment:
-            TESTOMATIO: << pipeline.parameters.testomatio >>
-            TESTOMATIO_RUN: << pipeline.parameters.run >>
-            TESTOMATIO_URL: << pipeline.parameters.testomatio_url >>
-```
-
-:::note
-
-If you use on-premise Testomat.io setup you will also need to add `testomatio_url` parameter.
-
-:::
-
-After Circle CI is set up, its time to open your project in Testomat.io and configure the connection between these two systems.
-
-1. Go to **'Settings'**.
-2. Select **'Continuous Integration'**.
-3. Click **'Connect to CI'**.
-
-![Testomatio - CI](./images/CI_4.png)
-
-4. Select **'Circle CI'** and enter following details on the **'Connection'** tab:
-
-- `Circle CI Trigger Url` - (see how it works [here](https://circleci.com/docs/2.0/api-developers-guide/#getting-started-with-the-api)).
-- `Circle Token` - Auth token from Circle CI, created in Circle CI during Step 1.
-
-![Testomatio - CircleCI](./images/CircleCI_2.png)
-
-5. Switch to **'Input Variables'** tab and select checkboxes:
-
-- Send Run ID as `run` input (required for scheduled jobs).
-- Send Testomat.io API key as `testomatio` input.
-- Send Testomat.io Server URL as `testomatio_url` input (if you use on-premise setup).
-
-:::note
-
-You can set and pass more input variables if you set them in [Environment Configuration](./index.md#environment-configuration). For example: test environment, browser, branch, etc.
-
-:::
-
-6. Click on **'Save'** button to save the connection.
-
-![Testomatio - CircleCI](./images/CircleCI_3.png)
-
-7a. When the connection is saved, open **'Runs'** page and select `Run Automated Tests in CI` option in extra menu.
-
-![Testomatio - CI Run](./images/CI_Run_1.png)
-
-8a. Select **'Circle CI'** profile in a list, select a target ref or any other variables, if any were configured. Optionally, select a **Test Plan** or create a new one.
-
-9a. Click on **'Launch'** button and wait for the results.
-
-![Testomatio - CircleCI](./images/CircleCI_4.png)
-
-OR
-
-7b. On **'Tests'** page select any automated suite or test case -> click **'Extra menu'** button -> select **'Run Tests'** option -> open **'Run in CI'** tab.
-
-8b. Select **'Circle CI'** profile in a list, as well, select a target ref or any other variables, if any were configured.
-
-9b. Click on **'Launch'** button and wait for the results.
-
-![Testomatio - CircleCI](./images/CircleCI_4b.gif)
-
-This will start a new job in Circle CI, please check that the job was successfully triggered and completed. After the job has finished, a run report will be available on Runs page of Testomat.io.
-
-![Testomatio - CircleCI](./images/CircleCI_5.png)

package/skills/testeiya/testomatio-docs/docs/integrations/continuous-integration/github.md

@@ -1,120 +0,0 @@
----
-title: GitHub Actions
-description: This guide explains how to integrate GitHub Actions with Testomat.io for continuous integration. It includes creating workflows, setting up environment variables, using Testomat.io-specific input parameters, and triggering automated tests. The integration allows detailed test reporting and efficient CI workflows.
-type: article
-url: https://docs.testomat.io/integrations/continuous-integration/github
-head:  
-  - tag: meta
-    attrs:
-      name: keywords
-      content: GitHub, Testomat.io, CI connection, CI Integration, GitHub Actions, Personal Access Token, Continuous Integration, Test Automation, Test Management, input parameters, environment variables, API token, Workflow, test reporting
----
-
-To set up connection between GitHub and Testomat.io, first, you need to configure your GitHub account:
-
-1. Create a Personal Access Token on GitHub with access to workflow scope (follow the instructions by link - [Create PAT](https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/managing-your-personal-access-tokens#creating-a-personal-access-token-classic)).
-
-![Testomatio - GitHub](./images/Github_1.png)
-
-2. Create a Workflow in a GitHub Repository: Go to **'Actions'** tab in Repository -> Select Workflow template -> Click **'Configure'** button. Then you will get a workflow template. 
-**A workflow filename will be used by Testomat.io to call a specific workflow.**
-
-![Testomatio - GitHub](./images/Github_2.png)
-
-![Testomatio - GitHub](./images/Github_3.png)
-
-3. This workflow will be used solely by Testomat.io, so it should start only on `workflow_dispatch` event. The event should be defined with the following input parameters:
-
-```yaml
-name: Testomatio Tests
-
-on:
-  workflow_dispatch:
-    inputs:
-      grep:
-        description: 'tests to grep '
-        required: false
-        default: ''
-      run:
-        required: false
-      testomatio:
-        required: false
-```
-
-4. The **Job** should include a step where the test runner is executed with `--grep` option and `TESTOMATIO` environment variables passed in. For instance:
-
-```yaml
-    - run: npx codeceptjs run --grep "${{ github.event.inputs.grep }}"
-      env:
-        TESTOMATIO: "${{ github.event.inputs.testomatio }}"
-        TESTOMATIO_RUN: "${{ github.event.inputs.run }}"
-```
-
-After configuring your GitHub account, integrate GitHub Actions CI with your Testomat.io project:
-
-1. Go to **'Settings'**.
-2. Select **'Continuous Integration'**.
-3. Click **'Connect to CI'**.
-
-![Testomatio - CI](./images/CI_4.png)
-
-4. Select **'GitHub'** and enter following details on the **'Connection'** tab:
-
-- `GitHub Username`.
-- `API token` - PAT created, in GitHub during Step 1.
-- `Organization/Repository (or User/Repository)`.
-- `Workflow` - name of a workflow in GitHub Actions, in our case `testomatio.yml`.
-
-![Testomatio - GitHub](./images/Github_4.png)
-
-5. Open **'Configuration'** tab and check the default `ref` value. `ref` specifies the target branch or tag for test execution. By default, it is set to `master`, but you can adjust this if your main branch uses a different name, such as `main`.
-
-![Testomatio - GitHub](./images/Github_5.png)
-
-6. Go to **'Input Variables'** tab and enable `run` and `testomatio` inputs, to pass them from Testomat.io.
-
-:::note
-
-You can set and pass more input variables if you set them in [Environment Configuration](./index.md#environment-configuration). Like in our case, test environments were set.
-
-:::
-
-:::note
-
-The `ref` parameter specifies which branch to run the workflow on. The provided workflow must be registered in the repository's GitHub Actions and must exist in the branch referenced by ref. A GitHub Action is considered registered if it exists in the project's default branch or has been triggered at least once.
-
-:::
-
-7. Click on **'Save'** button to save the connection.
-
-![Testomatio - GitHub](./images/Github_6.png)
-
-8a. When the connection is saved, open **'Runs'** page and select `Run Automated Tests in CI` option in extra menu.
-
-:::note
-
-When using the "Test connection" button, workflow lookup is performed against the repository's default branch. The ref parameter from the config is ignored. This is a GitHub Actions API limitation.
-
-:::
-
-![Testomatio - CI Run](./images/CI_Run_2.png)
-
-9a. Select **'GitHub'** profile in a list, select a target ref and any other variables, if any were configured. Optionally, select a **Test Plan** or create a new one.
-
-10a. Click on **'Launch'** button and wait for the results.
-
-![Testomatio - GitHub](./images/Github_7.png)
-
-OR
-
-8b. On **'Tests'** page select any automated suite or test case -> click **'Extra menu'** button -> select **'Run Tests'** option -> open **'Run in CI'** tab.
-
-9b. Select **'GitHub'** profile in a list, as well, select a target ref and any other variables, if any were configured.
-
-10b. Click on **'Launch'** button and wait for the results.
-
-![Testomatio - GitHub](./images/Github_7b.gif)
-
-This will start a new job in GitHub Actions, please check that the job was successfully triggered and completed. After the job has finished, a run report will be available on Runs page of Testomat.io.
-
-![Testomatio - GitHub](./images/Github_8.png)

package/skills/testeiya/testomatio-docs/docs/integrations/continuous-integration/gitlab.md

@@ -1,88 +0,0 @@
----
-title: GitLab CI
-description: Learn how to integrate GitLab CI with Testomat.io to automate test execution and reporting. The guide covers configuring .gitlab-ci.yml, passing environment variables, and triggering pipelines for seamless CI/CD integration. It also explains setting input variables and running tests directly from the Testomat.io interface.
-type: article
-url: https://docs.testomat.io/integrations/continuous-integration/gitlab
-head:  
-  - tag: meta
-    attrs:
-      name: keywords
-      content: GitLab, Testomat.io, CI connection, CI Integration, GitLab CI, Pipeline Trigger, Continuous Integration, Test Automation, Test Management, environment variables, GitLab Host, GitLab CI Trigger URL, Workflow, API
----
-
-To set up connection between GitLab and Testomat.io, first, you need to configure your GitLab account:
-
-1. Add new **Pipeline Trigger** in your GitLab Project - [read more](https://docs.gitlab.com/ee/ci/triggers/#trigger-a-pipeline).
-
-![Testomatio - GitLab](./images/GitLab_1.png)
-
-2. Go to **'Code' -> 'Repository'** and create **.gitlab-ci.yml** file or add the job to existing one. E.g. check by [link](https://gitlab.com/TetianaKhomenko/prod-setup/-/blob/main/.gitlab-ci.yml).
-
-![Testomatio - GitLab](./images/GitLab_2.png)
-
-It should contain next commands:
-```
-    - export TESTOMATIO="${testomatio}"
-    - export TESTOMATIO_URL="${testomatio_url}"
-    - export TESTOMATIO_RUN="${run}"
-```
-3. The **Job** should include a step where the test runner is executed with `--grep` option and `TESTOMATIO` environment variables passed in. For instance:
-
-```
-    - npx codeceptjs run-workers 2 --grep "${grep}"
-```
-When GitLab is set up, go to your Project in Testomat.io and configure GitLab CI connection:
-
-1. Go to **'Settings'**.
-2. Select **'Continuous Integration'**.
-3. Click **'Connect to CI'**.
-
-![Testomatio - CI](./images/CI_4.png)
-
-4. Select **'GitLab'** and enter following details on the **'Connection'** tab:
-
-- `Gitlab Host`.
-- `GitLab CI Trigger Url` - trigger pipeline URL, created in GitLab during Step 1.
-- `Trigger Token` - Active pipeline trigger token, created in GitLab during Step 1.
-
-![Testomatio - GitLab](./images/GitLab_3.png)
-
-5. Open **'Configuration'** tab and check the default `ref` value. `ref` specifies the target branch or tag for test execution. By default, it is set to `master`, but you can adjust this if your main branch uses a different name, such as `main`.
-
-![Testomatio - GitLab](./images/GitLab_4.png)
-
-6. Go to **'Input Variables'** tab and enable `run`, `testomatio token` and `TESTOMATIO_URL` variables to pass them from Testomat.io.
-
-:::note
-
-You can set and pass more input variables if you set them in [Environment Configuration](./index.md#environment-configuration). For example: test environment, browser, branch, etc.
-:::
-
-7. Click on **'Save'** button to save the connection.
-
-![Testomatio - GitLab](./images/GitLab_5.png)
-
-8a. When the connection is saved, open **'Runs'** page and select `Run Automated Tests in CI` option in extra menu.
-
-![Testomatio - CI Run](./images/CI_Run_3.png)
-
-9a. Select **'GitLab'** profile in a list, select a target ref and any other variables, if any were configured. Optionally, select a **Test Plan** or create a new one.
-
-10a. Click on **'Launch'** button and wait for the results.
-
-![Testomatio - GitLab](./images/GitLab_6.png)
-
-OR
-
-8b. On **'Tests'** page select any automated suite or test case -> click **'Extra menu'** button -> select **'Run Tests'** option -> open **'Run in CI'** tab.
-
-9b. Select **'GitLab'** profile in a list, as well, select a target ref and any other variables, if any were configured.
-
-10b. Click on **'Launch'** button and wait for the results.
-
-![Testomatio - GitLab](./images/GitLab_6b.gif)
-
-
-This will start a new pipeline in GitLab CI. Please check that the job was successfully triggered and completed. After the job has finished, a run report will be available on Runs page of Testomat.io.
-
-![Testomatio - GitLab](./images/GitLab_7.png)

package/skills/testeiya/testomatio-docs/docs/integrations/continuous-integration/index.mdx

@@ -1,151 +0,0 @@
----
-title: Continuous Integration
-description: Explore how to integrate continuous testing into your CI/CD pipeline using Testomat.io. This guide explains the setup process for Continuous Integration (CI), allowing users to connect their test management tool with popular CI tools like Jenkins, GitLab, and more. Learn how to automate test runs, manage reports, and streamline your testing workflows within a CI environment for effective test tracking and execution.
-type: article
-url: https://docs.testomat.io/integrations/continuous-integration
-head:
-  - tag: meta
-    attrs:
-      name: keywords
-      content: Testomat.io, Continuous Integration, CI connection, CI Integration, CI/CD, test automation, test management, Jenkins, Atlassian Bamboo, BitBucket Pipelines, TeamCity, GitHub Actions, GitLab CI, Circle CI, Azure Pipelines, automated testing, CI tools, CI job, testing workflow, test reports, input variables, environment configuration, custom variables
----
-
-import DirectoryLinks from '/src/components/DirectoryLinks.astro';
-
-<DirectoryLinks directory="integrations/continuous-integration" />
-
-Testomat.io allows executing tests on CI from its interface.
-A single test, suite, test plan, or all tests can be executed automatically on CI.
-
-**Currently following CI systems supported:**
-
-* [Atlassian Bamboo](https://docs.testomat.io/integrations/continuous-integration/bamboo)
-* [BitBucket Pipelines](https://docs.testomat.io/integrations/continuous-integration/bitbucket)
-* [Teamcity](https://docs.testomat.io/integrations/continuous-integration/teamcity)
-* [GitHub Actions](https://docs.testomat.io/integrations/continuous-integration/github)
-* [GitLab CI](https://docs.testomat.io/integrations/continuous-integration/gitlab)
-* [Jenkins](https://docs.testomat.io/integrations/continuous-integration/jenkins)
-* [Circle CI](https://docs.testomat.io/integrations/continuous-integration/circle)
-* [Azure Pipelines](https://docs.testomat.io/integrations/continuous-integration/azure)
-
-Testomat.io uses REST API to trigger jobs on external CI systems. IDs of tests or suites can be passed to the job so only a specific test or suite will be executed. The test runner greps all tests by their IDs and executes a subset of tests. Then a report is sent back to Testomat.io via reporter.
-
-![Testomatio - CI](./images/CI_1.png)
-
-**Connecting CI server to Testomat.io consist of the following steps:**
-
-1. Create Testomat.io Project.
-2. Import automated tests into that project from a repository.
-3. [Assign IDs](#assigning-ids) for imported tests source code.
-4. Create a new job in CI according to instructions on this page.
-5. Connect CI server to Testomat.io.
-6. Run your tests or suites to get reports!
-
-## Configuring CI
-
-CI configuration has 3 steps:
-
-1. Establishing a connection with CI.
-2. Setting up required input variables.
-3. Setting up custom configuration variables.
-
-Follow the guide for a corresponding CI to set it up.
-
-:::note
-
-Please ensure that Testomat.io IP addresses are allowed to access your CI environment: 142.132.185.19, 5.75.250.20
-
-![Testomatio - Configuration](./images/CI_IP_address.png)
-
-:::
-
-### Input Variables
-
-While connection settings can be different across CI settings, the list of input variables is the same.
-
-Here is how `run` input variable can be accessed on different CIs:
-
-- Atlassian Bamboo: `${bamboo.run}`
-- GitHub Actions: `${github.event.inputs.run}`
-
-It may as well pass other input variables which can be used on CI to improve reporting.
-
-**Here is the list of preconfigured input variables:**
-
-1. `grep` - Testomat.io sends `grep` variable to CI to identify which tests should be executed. `grep` variable is required and selected by default in Testomat.io.
-
-2. `run` - passes Run ID to CI. If this option is toggled on, when a run is created in Testomat.io, it is instantly added to the list of runs marked as 'Scheduled'. On CI `run` variable must be passed as `TESTOMATIO_RUN` environment variable to a reporter. This allows mapping a scheduled run to the run which is currently processed. **If `TESTOMATIO_RUN` is not set, a duplicate run will be created**.
-
-3. `testomatio` - passes project access key to CI. This input variable must be passed as `TESTOMATIO` environment variable to match the Testomat.io project. Toggle on this option if you prefer not to hardcode Testomat.io Project ID in CI configuration but to obtain this value on launch. This may be useful if you have a different Testomat.io project configured on CI run.
-
-4. `testomatio_url` - when working on a self-hosted Testomat.io instance, this variable can be used to pass Testomat.io endpoint to CI system. Pass `testomatio_url` environment variable to `TESTOMATIO_URL`.
-
-![Testomatio - Input Variables](./images/CI_2.png)
-
-### Environment Configuration
-
-Sometimes extra configuration is required for CI job. For instance, extra configuration variables can be used to specify:
-
-- browser.
-- target branch.
-- staging/production environments.
-- suites.
-
-Testomat.io allows to predefine configuration variables and adjust them for each run. Config variables can be set in **'Configuration'** tab on CI connection settings.
-
-![Testomatio - Configuration](./images/CI_3.png)
-
-Config variables should be put per line with the default value passed in with `=`. The format is similar to `.env` file format:
-
-```
-browsers=chrome,firefox,safari
-branch=main
-user=admin@admin.com
-password=123456
-suites=[3f4290f0,b89df296,78b10b62]
-```
-
-`ref=master` config variable is set up by default for some CI services in Testomat.io but it can be changed at any time.
-
-:::note
-
-To set a variable without a default value just pass it as on a line without `=`
-
-:::
-
-Those variables will be available for a reconfiguration on each CI Run executed from Testomat.io.
-If a variable value contains comma `,` like in example above: `chrome,firefox,safari`, these values will be displayed with the select box. Otherwise, a simple input will be shown.
-
-![Testomatio - CI Profile](./images/CI_profile.png)
-
-These variables will be passed to CI in the same manner as `grep` parameter. So, CI job should be prepared to handle these config variables. For instance, if GitHub Actions are used, values are passed as `inputs` and can be used like this:
-
-```yaml
-    - run: npx codeceptjs run --grep "${{ github.event.inputs.grep }}" --profile "${{ github.event.inputs.branch }}"
-      env:
-        TESTOMATIO: "${{ github.event.inputs.testomatio }}" # passed from Testomatio by default
-        BROWSER: "${{ github.event.inputs.browser }}"
-        TEST_USER: "${{ github.event.inputs.user }}"
-        TEST_PASSWORD: "${{ github.event.inputs.password }}"
-```
-
-### Assigning IDs
-
-To execute a specific test or a suite a test runner should have a way to find a test by its unique name. For this reason, Testomat.io IDs can be used. If tests in the source code will have Testomat.io IDs it will be very simple to filter tests. We provide a semi-automatic way to assign Testomat.io IDs to tests in source code.
-
-For JavaScript frameworks use the same `check-tests` command you used for importing tests with `--update-ids`. The tests must be already imported in Testomat.io:
-
-```
-TESTOMATIO={apiKey} npx check-tests <framework> <pattern> --update-ids
-```
-
-For Cucumber tests use `check-cucumber` command with the similar `--update-ids` command. The command should be the same as for importing plus `--update-ids` option:
-
-```
-TESTOMATIO={apiKey} npx check-cucumber <pattern> --update-ids
-```
-
-This command will update your source code. Please check the changes before committing it.
-If the Testomat.io IDs were placed correctly you can commit your changes to repository.
-
-From now on, Testomat.io can use Test IDs to run exact tests and suites on Continuous Integration servers.

package/skills/testeiya/testomatio-docs/docs/integrations/continuous-integration/jenkins.md

@@ -1,121 +0,0 @@
----
-title: Jenkins
-description: Learn how to integrate Jenkins with Testomat.io for continuous integration. This guide covers creating Jenkins jobs, configuring parameters, triggering builds remotely, and connecting Jenkins with Testomat.io using API tokens. It also includes steps for passing environment variables for test execution and enabling on-premise setups.
-type: article
-url: https://docs.testomat.io/integrations/continuous-integration/jenkins
-head:
-  - tag: meta
-    attrs:
-      name: keywords
-      content: Jenkins, Testomat.io, CI connection, CI Integration, Jenkins API Token, Freestyle project, build triggers, remote build, environment variables, CodeceptJS, Jenkins Hostname, input variables, environment configuration, automated tests, test plan
----
-
-To connect Jenkins to Testomat.io you will need a user and an API Token created on Jenkins.
-API token can be added on **'Configure'** page of the current user:
-
-![Testomatio - Jenkins](./images/Jenkins.png)
-
-Then, follow the instructions added below:
-
-1. Create a new Jenkins job. Select **'Freestyle project'**.
-
-![Testomatio - Jenkins](./images/Jenkins_1.png)
-
-:::note
-
-It is recommended to avoid spaces in Job Name to prevent issues with connecting to this job via URL.
-
-:::
-
-2. Make this build parametrized
-
-![Testomatio - Jenkins](./images/Jenkins_2.png)
-
-3. Add the following parameters as a string with empty default values:
-
-- `run`
-- `testomatio`
-- `grep`
-
-:::note
-
-If you use on-premise Testomat.io setup you will also need to add `testomatio_url` parameter.
-
-:::
-
-4. Go to **'Build Triggers'** and select **'Trigger build remotely'**.
-
-![Testomatio - Jenkins](./images/Jenkins_3.png)
-
-5. Proceed with configuring the Job and set all required parameters like SCM and build steps.
-
-![Testomatio - Jenkins](./images/Jenkins_4.png)
-
-Within a step pass in configured parameters as environment variables into the test runner. Let's take CodeceptJS command as an example:
-
-```
-TESTOMATIO_RUN=${run} TESTOMATIO=${testomatio} npx codeceptjs run --grep "${grep}"
-```
-
-:::note
-
-Prepend `TESTOMATIO_URL=${testomatio_url}` if you use on-premise version
-
-:::
-
-![Testomatio - Jenkins](./images/Jenkins_5.png)
-
-6. Save the build.
-
-After Jenkins is set up, go to Testomat.io and create a new **CI connection** inside your project: 
-
-1. Go to **'Settings'**.
-2. Select **'Continuous Integration'**.
-3. Click **'Connect to CI'**.
-
-![Testomatio - CI](./images/CI_4.png)
-
-4. Select **'Jenkins'** and fill in all required fields:
-
-- `Jenkins Hostname` - URL of Jenkins host.
-- `Username` - a user on Jenkins which will trigger builds.
-- `API Token` - a token we created previously in the user's settings.
-- `Job Name` - the name of a job we just created.
-
-![Testomatio - Jenkins](./images/Jenkins_7.png)
-
-5. Switch to **'Input variables'** tab and enable variables that were configured for parametrized builds.
-
-:::note
-
-Don't forget to select `testomatio_url` if you use on-premise version.
-
-:::
-
-You can pass more input variables if you set them in [Environment Configuration](./index.md#environment-configuration). For example: test environment, browser, branch, etc.
-
-6. Click **'Save'** button and check the connection.
-
-![Testomatio - Jenkins](./images/Jenkins_8.png)
-
-Now you can run a test or a group of tests via Jenkins CI. 
-
-7a. Open **'Runs'** page then select `Run Automated Tests in CI` option in extra menu.
-
-![Testomatio - CI Run](./images/CI_Run_1.png)
-
-8a. Select **'Jenkins'** profile in a list. Optionally, select a **Test Plan** or create a new one.
-
-![Testomatio - Jenkins](./images/Jenkins_9.png)
-
-OR
-
-7b. On **'Tests'** page select any automated suite or test case -> click **'Extra menu'** button -> select **'Run Tests'** option -> open **'Run in CI'** tab.
-
-8b. Select **'Jenkins'** profile in a list.
-
-![Testomatio - Jenkins](./images/Jenkins_9a.gif)
-
-9. Launch a Run and wait for the results.
-
-![Testomatio - Jenkins](./images/Jenkins_10.png)