testeiya 0.2.1 → 0.3.9

package/skills/testeiya/testomatio-docs/docs/getting-started/index.md

@@ -1,290 +0,0 @@
----
-title: Start With Testomat.io
-description: This guide helps users start from scratch with Testomat.io by creating projects, writing test cases, running manual and automated tests, and analyzing results with detailed reporting and analytics. It also includes importing automated tests and tracking automation coverage for optimization.
-type: article
-url: https://docs.testomat.io/getting-started/start-from-scratch/
-head:
-  - tag: meta
-    attrs:
-      name: keywords
-      content: Testomat.io, getting started, manual tests, automated tests, test reporting, project creation, test analytics, automation coverage, test cases, test management system
----
-
-<!--
-> If you don't have any manual or automated tests yet - follow this guide. Otherwise, pick the section of the guide relevant to your project. You might want to start from [this section](https://docs.testomat.io/getting-started/import-tests-from-source-code/) if you consider **importing tests from source code** into Testomat.io. For those interested in importing tests from the **Cucumber** framework, go straight to [this section](https://docs.testomat.io/getting-started/import-tests-from-cucumber/#why-do-i-need-to-import-my-tests)!
--->
-
-Welcome!
-
-This step-by-step guide helps you to create your project, add tests, execute them, and review results with analytics.
-
-By the end of this guide, you will have:
-
-- a project
-- suites/folders with suites
-- tests
-- runs
-- a report
-- visual analytics with all data
-
-![Testomat.io - GETTING STARTED general diagram](./images/testing-workflow.png)
-
-## Create Project
-
-A project is the main entity in Testomat.io that contains all tests, test execution programs, and analytical data on them. Every project can contain any number of suites and folders with any amount of tests, test runs, plans, and reports in them.
-
-:::note
-
-Each project is a separate entity. That means, you can do whatever you want within the Project, but you cannot cross-do staff between Projects.
-
-:::
-
-Register at [app.testomat.io](https://app.testomat.io) and activate your user account. Then create a new project:
-1. Go to your account **Dashboard**.
-2. In the top-right corner, click **Create**.
-3. Enter the project title.
-4. Choose the project type:
-    - BDD Project
-    - Classical Project
-5. Decide whether to use demo data or your own data.
-6. Click **Create**.
-
-![Testomat.io - Create new project](./images/create-project.png)
-
-Use [BDD Project](https://docs.testomat.io/project/tests/bdd-test-case-editor/) if you plan to work with BDD descriptions or the Cucumber framework.
-
-Use [Classical Project](https://docs.testomat.io/project/tests/classical-test-case-editor/) if you want free-form markdown test cases with automation synced to test cases.
-
-You have just created your first project! 
-
-Now you can start creating suites and test cases for your projects.
-
-## Create a Suite
-
-Test suite is a collection of tests grouped together. You can create suites or create a folder with suites. 
-
-![Testomat.io - Create new Suite](./images/project-hierarchy-icons.png)
-
-To create a suite:
-1. Select a project.
-2. Click **New suite**.
-3. Enter your Suite name.
-4. Press `Enter` on your keyboard.
-
-Another way to create suite:
-
-1. Click action menu button (...).
-2. Select **Create more suites** from the menu.
-
-![create more suite button](./images/suite1.png)
-
-3. Enter the title of the new suite or folder.
-4. Click **'+ Suite'** to create a test suite, or optionally
-5. Click **'Folder'** to create a folder for grouping suites.
-
-![create new suite/folder](./images/suite%202.png)
-
-:::note
-
-You can create folders to group your suites. On the project page, click **New folder**, enter its name, and press `Enter` on the keyboard.
-
-You can create any number of folders and suites within a folder.
-
-:::
-
-## Create Manual Test Cases
-
-Read full article: [Test Case Creation and Editing](https://docs.testomat.io/project/tests/test-case-creation-and-editing/).
-
-After you’ve created test suites, you can start adding tests. 
-1. Select a test suite.
-2. Click on Suite, and a Suite panel will open to the right. 
-3. At the bottom of the **Tests** tab, enter the name of the test. 
-4. Click **Create**. 
-5. Click on the test to edit it.
-
-:::note
-
-When tests are newly created, they are marked as **manual** by default, which shows that they are ready for manual checks. 
-
-:::
-
-You can also create a test using the **New test** button at the top of the Suite editor panel.
-
-![Testomat.io - Create test case](./images/manual-tests-create.png)
-
-### Bulk-create Tests
-
-Read full article: [Bulk Edit](https://docs.testomat.io/advanced/bulk-edit-folder/bulk-edit-on-suite-and-test-level/).
-
-To add multiple tests at once by listing their names, rather than adding each one individually:
-1. Open (or create) a suite.
-2. Turn on the **Bulk** toggle.
-3. Type **one test name per line** in the input field.
-4. Click **Create** - every line becomes a separate test, all added together.
-
-![Testomat.io - Create test case](./images/bulk-create-tests.png)
-
-## Run Manual Tests
-
-Read full article: [Running Tests Manually](https://docs.testomat.io/project/runs/running-tests-manually/).
-
-There are two main ways to start a manual run:
-
-From the ‘Tests’ page, quick launch for selected tests or suites, or adding tests to an already ongoing run without leaving the Tests view.
-
-1. On the **Tests** sidebar tab, activate **Multi-select**.
-2. Select tests you need to run.
-3. Click the **Run** button in the actions menu below.
-
-![Testomat.io - Tests manual run](./images/tests-manual-run.png)
-
-From the ‘Runs’ page - the classic way to create and manage full runs with complete configuration options.
-
-1. Go to the **Runs** tab in the sidebar.
-2. Click the **New** button and select **New manual test run**.
-3. Enter the run **Title**.
-4. Then select **All tests**, **Test plan**, **Select tests**, or **Without tests** to run tests.
-5. Click the **Launch** button to execute the tests.
-
-![Testomat.io - Run manual tests](./images/run-manual-tests.png)
-
-:::note
-
-Before tests execution, you can specify the run [environment options](https://docs.testomat.io/getting-started/running-tests-manually/#multi-environment-tests).
-
-You can also toggle the **Run Automated as Manual** switch to select the result of automated tests manually.
-
-:::
-
-When the test execution is launched, testers can:
-- Mark each test as **Passed**, **Failed**, or **Skipped**. 
-- Add messages.
-- Attach evidence (screenshots, logs, etc.)
-- Assign tests to specific team members.
-
-![Testomat.io - Execute tests](./images/launch-manual-run.png)
-
-## Import Automated Tests
-
-Read full article: [Import Automated Tests](https://docs.testomat.io/getting-started/#import-automated-tests), [Import from CSV/XLSX](https://docs.testomat.io/project/import-export/import/import-tests-from-csv-xlsx/), and [Import Tests From TestRail](https://docs.testomat.io/project/import-export/import/import-tests-from-testrail/).
-
-To add automated tests to your project, you must import them from the source code, a CSV file, or an existing TestRail suite. To import automated tests, follow these steps:
-
-1. Open your project.
-2. Navigate to the actions (...).
-3. Click **Import automated tests**.
-
-Alternatively:
-
-1. Go to the Imports menu.
-2. Navigate to the **Import** dropdown menu.
-3. Select an import option:
-
-   | Import option | Description |
-   |---|---|
-   | **Import from Source Code** | Imports tests directly from your local project or repository. |
-   | **Import from CSV** | Imports tests from a CSV file and converts it to one of the available formats. |
-   | **Import from TestRail** | Imports tests from an existing TestRail suite. |
-
-In the **Import** section, pick the framework, programming language and operating system you are using for testing.
-
-![Testomat.io - Copy instructions](./images/copy-import-instructions.png)
-
-:::note
-
-Please check your environment:
-
-- For NodeJS (JavaScript, TypeScript): you need NodeJS 10+ and npm installed to be able to run this command.
-- For PHP: you need PHP > 7.2 and Composer installed.
-
-:::
-
-### Import via Terminal
-
-Testomat.io can store tests from various frameworks. To import automated tests:
-
-1. Open a terminal, navigate to the tests folder in your project. 
-2. Copy and execute the import command in a terminal.
-3. See a report on how many tests were found.
-4. Reopen the project and see that all tests with their folders and files are shown on Testomat.io.
-
-![Testomat.io - Execute command in terminal, automated tests found and sent](./images/import-tests-terminal.png)
-
-If you don't see a similar message, please check the command's API change command parameters so it could find tests. The most common issues with import are different file naming format and/or incorrect directory for import.
-
-:::note
-
-All imported tests are marked as "Automated" by default. Please, check that the link actually points to the corresponding file.
-
-:::
-
-## Run Automated Tests
-
-Read full article: [Running Automated Tests](https://docs.testomat.io/project/runs/running-automated-tests/).
-
-To start Run Automated Tests:
-1. Go to the **Runs** page. 
-2. Navigate to the **New** dropdown menu.
-3. Select **Report automated tests**.
-
-![Testomat.io - Import automated tests](./images/report-automated-tests.png)
-
-5. In the opened window select your framework. 
-6. Testomat.io will generate a terminal command.
-
-![Testomat.io - Choose test automation framework](./images/report-automated-tests-2.png)
-
-7. Start generated commands in your terminal from your project folder.
-
-![Testomat.io - Execute test cases](./images/execute-test-terminal.png)
-
-8. A new Test Run will appear on Runs page.
-
-## Test Run Report
-
-Read full article: [Testomat.io Reporter](https://docs.testomat.io/test-reporting/reporter/).
-
-You can use Testomat.io as a test management system or as a rich reporting tool. Each test has its history and a lifecycle, so each test report will be attached to a corresponding test in a project.
-
-To view your test run reports: 
-
-1. Navigate to the Runs menu. 
-2. Find the information about the completed test run (the duration of the run, the performer, etc.)
-3. Filter by status, find specific tests by tags, or sort by available methods. 
-4. You can see test results in real-time.
-
-![Testomat.io - Simplified test report](./images/run-report-1.png)
-
-To get a detailed report of the test run, click on the **Report** button. Share the report with your stakeholders.
-
-![Testomat.io - Detailed test report](./images/run-report-2.png)
-
-:::note
-
-Artifacts like screenshots, videos, and traces are uploaded to your own cloud storage via S3 protocol. Artifacts can be uploaded privately or publicly and used in reports.
-
-:::
-
-## Analytics
-
-Read full article: [Analytics](https://docs.testomat.io/project/analytics/).
-
-Testomat.io Analytics provides an extensive overview of testing data by tracking both automated and manual tests. You can visualize trends over time with custom charts, identify automation coverage, monitor failure patterns, and analyze metrics like flaky or slowest tests.
-
-![Testomat.io - Analytics](./images/analytics-testomat-io.png)
-
-Additional features include a failure board, label, and tag statistics for better team insights, allowing for optimized testing and proactive bug prevention.
-
-
-
-## Explore more features
-
-Learn more: [AI-Powered Features](https://docs.testomat.io/advanced/ai-powered-features/ai-powered-features/) and [Issues Management Systems](https://docs.testomat.io/integrations/issues-management/).
-
-Once you’re comfortable with the core workflow, you can start using advanced features to help you with your QA process. 
-
-A built-in AI assistant can generate new test cases from existing suites or requirements, suggest missing scenarios, summarize project coverage, and write descriptions for undocumented automated tests.
-
-On the integrations side, Testomat.io works out of the box with popular automation frameworks ([Playwright](https://docs.testomat.io/tutorials/playwright/), [Cypress](https://docs.testomat.io/test-reporting/workflows/#github-actions-and-cypress-trigger--pr), [Cucumber](https://docs.testomat.io/project/import-export/import/import-bdd/#_top), and more), CI/CD tools like [GitHub Actions](https://docs.testomat.io/integrations/continuous-integration/github), [GitLab](https://docs.testomat.io/integrations/continuous-integration/gitlab), and [Jenkins](https://docs.testomat.io/integrations/continuous-integration/jenkins), as well as team tools such as [Slack](https://docs.testomat.io/integrations/report-notifications/slack) and [Confluence](https://docs.testomat.io/integrations/issues-management/confluence). In addition, the [Jira](https://docs.testomat.io/integrations/report-notifications/jira) plugin keeps tests, issues, and results in sync so your whole team can manage testing without leaving the tools they already use.
-

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

@@ -1,96 +0,0 @@
----
-title: Azure Pipelines
-description: Integrate Azure Pipelines with Testomat.io to automate test execution and reporting. This guide explains setting up CI connections, creating input variables, and configuring pipelines to run tests with tools like CodeceptJS, Jest, or Playwright. It also details passing custom variables and specifying branches for targeted testing.
-type: article
-url: https://docs.testomat.io/integrations/continuous-integration/azure
-head:  
-  - tag: meta
-    attrs:
-      name: keywords
-      content: Azure DevOps, Testomat.io, CI connection, CI Integration, Azure Pipeline, Personal Access Token, Continious Integration, Test Automation, Test Management, Microsoft Azure, input variables, configuration, workflows, test reporting
----
-
-To connect Azure DevOps to Testomat.io, first you need to create an Private Access Token (PAT).
-Learn how to create a PAT following the link - [Create PAT](https://learn.microsoft.com/en-us/azure/devops/organizations/accounts/use-personal-access-tokens-to-authenticate?view=azure-devops&tabs=Windows).
-
-And follow the instructions below:
-
-1. Create a **PAT** in your Azure DevOps account with permission to **Read & Execute Build**.
-
-![Testomatio - Azure Pipeline](./images/Azure_D_1.png)
-
-2. Obtain the **ID** of a Pipeline you want to execute. Open a Pipeline and copy its ID from `definitionId` query parameter. On this screenshot the ID is `1`.
-
-![Testomatio - Azure Pipeline](./images/Azure_D_2.png)
-
-3. Create a new **CI connection** inside your project in Testomat.io: go to **'Settings' -> 'Continuous Integration' ->** click **'Connect to CI'** select **'Azure Pipelines'**
-
-![Testomatio - Azure Pipeline](./images/Azure_D_3.png)
-
-4. Enter following details on the **'Connection'** tab:
-
-- `Personal Access Token` - PAT created, in Azure DevOps during Step 1.
-- `Azure DevOps Organization`.
-- `Azure DevOps Project`.
-- `Azure DevOps Pipeline Id` - open a pipeline and copy a number value of `definitionId` param from URL (in our case `definitionId = 1`).
-- `Azure Server URL` - in case you use self-hosted Azure DevOps Server instead of Azure Cloud.
-
-![Testomatio - Azure Pipeline](./images/Azure_D_4.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).
-
-6. Save the conection
-
-![Testomatio - Azure Pipeline](./images/Azure_D_5.png)
-
-7. Testomat.io will need to send Input Variables into a Pipeline. For this, you need to enable them inside a Pipeline using **Azure DevOps UI**. Open a Pipeline and edit it.
-
-![Testomatio - Azure Pipeline](./images/Azure_D_6.png)
-
-8. Click **'Variables'** button
-
-![Testomatio - Azure Pipeline](./images/Azure_D_7.png)
-
-9. Create the following variables:
-
-- `grep`
-- `run`
-- `testomatio`
-- `testomatio_url`
-
-![Testomatio - Azure Pipeline](./images/Azure_D_8.png)
-
-Do not set defaults to this variable and tick **'Let users override this value when running this pipeline'** so Testomat.io could set these variables via API request.
-
-![Testomatio - Azure Pipeline](./images/Azure_D_9.png)
-
-10. Update the Pipeline to use passed variables. Update the script and pass environment variables to a test runner. Each variable can be accessed as `$(variable)`.
-For CodeceptJS this command will look the following way:
-
-```yaml
-- script: |
-    TESTOMATIO=$(testomatio) TESTOMATIO_URL=$(testomatio_url) TESTOMATIO_RUN=$(run) npx codeceptjs run --grep="$(grep)"
-  displayName: 'run tests'
-```
-
-:::note
-
-If you use Jest, Playwright, Cucumber, Cypress, etc. replace  `npx codeceptjs run` with the execution command of your test runner.
-
-:::
-
-You can pass more custom variables into a Pipeline defining them in a Pipeline UI first and listing them in Testomat.io configuration as well. These variables should be set in Azure in the same way as `grep`. See [Environment Configuration](./index.md#environment-configuration) to see how they can be configured in Testomat.io.
-
-To specify a different branch to run tests add `ref` parameter on **'Configuration'** tab specifying target ref.
-
-![Testomatio - Azure Pipeline](./images/Azure_D_10.png)
-
-To specify `develop` branch add this as config parameter:
-
-```
-ref=refs/heads/develop
-```

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

@@ -1,94 +0,0 @@
----
-title: Atlassian Bamboo
-description: This guide explains integrating Atlassian Bamboo with Testomat.io for continuous integration. It includes configuring Bamboo plans, setting environment variables, and running tests with the CodeceptJS framework. Steps to connect Bamboo to Testomat.io via API keys and enable reporting are also provided.
-type: article
-url: https://docs.testomat.io/integrations/continuous-integration/bamboo
-head:    
-  - tag: meta
-    attrs:
-      name: keywords
-      content: Atlassian Bamboo, Testomat.io, CI integration, CI connection, continuous integration, CodeceptJS, test automation, API token, environment variables, test reporting, Bamboo plan setup, configuration, workflows
----
-
-Let's configure Bamboo CI server to work for CodeceptJS framework:
-
-1. Create a plan in Bamboo for Testomat.io to run in Testomat.io.
-
-![Testomatio - Bamboo](./images/Bamboo_1.png)
-
-2. Note the **'Plan key'**. In this case its **'TES'**.
-3. Configure the job to install node dependencies.
-
-![Testomatio - Bamboo](./images/Bamboo_2.png)
-
-4. Add the script to run CodeceptJS tests:
-
-```
-TESTOMATIO_RUN=${bamboo.run} npx codeceptjs run --grep "${bamboo.grep}"
-```
-Following environment variables must be set:
-
-- **Add `TESTOMATIO` environment variable with API key of Testomat.io project.**
-- If you are running a self-hosted Testomat.io instance, add `TESTOMATIO_URL` variable to specify a host to which reports will be sent.
-
-![Testomatio - Bamboo](./images/Bamboo_3.png)
-
-5. Set an input variable. Open Plan configuration:
-
-![Testomatio - Bamboo](./images/Bamboo_4.png)
-
-add `grep` and `run` variables with an empty string as a default value
-
-![Testomatio - Bamboo](./images/Bamboo_5.png)
-
-Now, as Bamboo is configured, you need to configure Bamboo integration at Testomat.io:
-
-1. Go to **'Settings'**.
-2. Select **'Continuous Integration'**.
-3. Click **'Connect to CI'**.
-
-![Testomatio - CI](./images/CI_4.png)
-
-4. Select **'Atlassian Bamboo'** and enter the details of Bamboo server on **'Connection'** tab:
-
-- `Bamboo Hostname` - URL of Bamboo host.
-- `API Token` - to generate API token [check this](https://confluence.atlassian.com/bamboo/personal-access-tokens-976779873.html).
-- `Project Key` - Chars ID, in our example its `EX`.
-- `Plan Key` - Chars ID, in our example its `TES`.
-
-A project and plan keys can be found from URL:
-
-![Testomatio - Bamboo](./images/Bamboo_6.png)
-
-![Testomatio - Bamboo](./images/Bamboo_7.png)
-
-5. Enable `run` option on **'Input Variables'** tab. This allows CI to send a report to a specific Run inside Testomat.io.
-6. Click **'Save'** button and check the connection.
-
-![Testomatio - Bamboo](./images/Bamboo_8.png)
-
-:::note
-
-You can pass more input variables if you set them in [Environment Configuration](./index.md#environment-configuration). For example: test environment, browser, branch, etc.
-
-:::
-
-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 **'Bamboo'** profile in a list. Optionally, select a **Test Plan** or create a new one.
-
-![Testomatio - Bamboo](./images/Bamboo_10.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 **'Bamboo'** profile in a list.
-
-![Testomatio - Bamboo](./images/Bamboo_9a.gif)
-
-9. Launch a Run and wait for the results.
-
-![Testomatio - Bamboo](./images/Bamboo_11.png)

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

@@ -1,106 +0,0 @@
----
-title: BitBucket Pipelines
-description: Integrate Bitbucket Pipelines with Testomat.io to streamline test execution and reporting. This guide explains setting up API tokens, configuring pipeline parameters, and running tests with environment variables like TESTOMATIO. It includes instructions for handling grep options, on-premise setups, and connecting Testomat.io for seamless CI/CD integration.
-type: article
-url: https://docs.testomat.io/integrations/continuous-integration/bitbucket
-head:  
-  - tag: meta
-    attrs:
-      name: keywords
-      content: Bitbucket Pipelines, Testomat.io, CI/CD integration, CI connection, CI Integration, automated testing, test reporting, API tokens, environment variables, test management, on-premise setups
----
-
-To connect BitBucket to Testomat.io you will need a API Token created in your BitBucket account.
-API token can be added on **'Repository settings'** page of the current user - [create an access token for repository](https://support.atlassian.com/bitbucket-cloud/docs/create-a-repository-access-token/).
-
-![Testomat.io - Bitbucket API Token](./images/Bitbucket_1.png)
-
-Then create a new BitBucket project. Click on **'Create'** button at the header menu and select **'Project'** option from the displayed dropdown list.
-
-![Testomat.io - Bitbucket New Project](./images/Bitbucket_2.png)
-
-Make this build parametrized. Go to **'Settings' -> 'Workspace settings' -> 'Workspace variables'**
-
-![Testomat.io - Bitbucket Workspace Variables](./images/Bitbucket_3.png)
-
-Add the following parameters as a string with empty default values:
-
-- ```run```
-- ```testomatio```
-- ```grep```
-
-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}"```
-
-![Testomat.io - Bitbucket Job Step](./images/Bitbucket_4.png)
-
-:::note
-
-If you use on-premise Testomat.io setup you will also need to add `testomatio_url` parameter.
-
-:::
-
-Save the build and switch to Testomat.io. To integrate BitBucket with your Testomat.io project follow the steps described below:
-
-1. Go to **'Settings'**.
-2. Select **'Continuous Integration'**.
-3. Click **'Connect to CI'**.
-
-![Testomatio - CI](./images/CI_4.png)
-
-4. Select **'BitBucket Pipeline'** and enter following details on the **'Connection'** tab:
-
-- `API token` - access token, created in BitBucket during Step 1.
-- `Workspace Name` - Workspace UID.
-- `Repository Slug`- a URL-friendly version of a repository name, automatically generated by BitBucket for use in the URL.
-
-![Testomatio - Bitbucket](./images/Bitbucket_5.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.
-
-:::
-
-:::note
-
-If a pipeline is specified in the configuration, the Bitbucket integration will trigger a custom pipeline instead of the default one.
-
-:::
-
-6. Click on **'Save'** button to save the connection.
-
-![Testomatio - Bitbucket](./images/Bitbucket_6.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 **'BitBucket'** 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 - Bitbucket](./images/Bitbucket_7.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 **'BitBucket'** 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 - Bitbucket](./images/Bitbucket_7b.gif)
-
-This will start a new job in BitBucket, 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 - Bitbucket](./images/Bitbucket_8.png)
-
-