testeiya 0.2.1 → 0.3.9

package/skills/testeiya/testomatio-docs/docs/integrations/issues-management/shortcut.md

@@ -1,67 +0,0 @@
----
-title: Shortcut Configuration
-description: Learn how to integrate Shortcut with Testomat.io for effective issue tracking. This guide details how to retrieve your API Access Token and Workflow Name and provides step-by-step instructions to configure the Shortcut integration within Testomat.io seamlessly.
-type: article
-url: https://docs.testomat.io/integrations/issues-management/shortcut
-head:
-  - tag: meta
-    attrs:
-      name: og:image
-      content: https://docs.testomat.io/_astro/New_UTbONHqM_2024-10-31.DUKqHBp2_YEDnG.webp
-      
-  - tag: meta
-    attrs:
-      name: keywords
-      content: Shortcut integration, Testomat.io, issue management, API Access Token, Workflow Name, project management, test management tools, software testing, agile development
----
-
-If you already have a workspace configured in **Shortcut**, you're ready to integrate it with Testomat.io. To get started, you’ll need your **Workflow Name**, and **API Access Token**. We’ll walk you through each step to locate this information and connect it with Testomat.io.
-
-![Testomat.io - Shortcut workspace](./images/New_OsYXONII_2024-11-21.png)
-
-To create the **API Access Token**, follow these steps:
-
-1. Click on **Settings** button
-2. Go to **API Tokens**
-3. Enter **Token Name**
-4. Click on **Generate Token** button
-
-![Testomat.io - Shortcut Create Token](./images/New_ipmViSuc_2024-11-21.png)
-
-5. Copy your API Token
-
-![Testomat.io - Shortcut API Access Token](./images/New_xCU4yAtk_2024-11-21.png)
-
-Keep your **API Access Token** secure, as you’ll need it for the integration with Testomat.io.
-
-To locate the **Workflow Name**, follow these steps:
-
-1. Click on **Settings** button
-2. Go to **Workflows**
-5. Copy your Workflow Name
-
-![Testomat.io - Shortcut Workflow Name](./images/New_L83JSNf7_2024-11-21.png)
-
-After collecting all necessary data, we can move on to Testomat.io. 
-
-1. Select Shortcut from the list of available Issue Management Systems.
-
-![Testomat.io - Connect to Shortcut](./images/New_FMxDuVut_2024-11-21.png)
-
-2. Enter a **Profile Name**
-3. Paste Shortcut **API Access Token**
-4. Paste Shortcut **Workflow Name**
-5. Click on **Save** button
-
-![Testomat.io - Shortcut Configuration](./images/New_g9KgOr4g_2024-11-21.png)
-
-If everything was done correctly, you will receive a confirmation message indicating that the Shortcut profile was successfully created.
-
-![Testomat.io - Shortcut Profile](./images/New_58FqfBg9_2024-11-21.png)
-
-## Frequently Asked Questions (FAQ)
-
-**Q: Although linking an already existing Shortcut ticket does not work as I expected. When using **“Link to Issue”** and entering the Shortcut URL, it does not automatically create an external link on Shortcut.**
-
-A: This behavior is expected. When you use the **“Link to Issue”** feature in Testomat.io to attach an existing Shortcut ticket, it will not automatically create a backlink (external link) inside Shortcut. This limitation is caused by Shortcut’s API, which currently does not allow third-party tools to generate external links on already existing tickets.
-

package/skills/testeiya/testomatio-docs/docs/integrations/issues-management/youtrack.md

@@ -1,94 +0,0 @@
----
-title: YouTrack Configuration
-description: Learn how to integrate YouTrack with Testomat.io for streamlined issue management. This guide explains how to retrieve your YouTrack Workspace Name, Personal Access Token, and Project ID, and then configure the integration within Testomat.io.
-type: article
-url: https://docs.testomat.io/integrations/issues-management/youtrack
-head:
-  - tag: meta
-    attrs:
-      name: og:image
-      content: https://docs.testomat.io/_astro/New_UTbONHqM_2024-10-31.DUKqHBp2_YEDnG.webp
-
-  - tag: meta
-    attrs:
-      name: keywords
-      content: YouTrack integration, Testomat.io, issue tracking, personal access token, workspace configuration, project management, test management tools, software testing, bug tracking
----
-
-If you already have a workspace and project in YouTrack, you’re ready to integrate it with Testomat.io. To do so, you’ll need three items:
-
-- Workspace Name
-- Personal Access Token
-- Project ID
-
-This guide walks you through where to find each.
-
-![Testomat.io - YouTrack Project](./images/New_US8feteR_2024-10-31.png)
-
-## How to Find a Workspace Name
-
-You can find your **Workspace Name** in the browser **URL** when you're logged into YouTrack. For example: `[my-workspace].youtrack.cloud`
-
-![Testomat.io - YouTrack Workspace Name](./images/New_kltLXnVA_2024-10-31.png)
-
-## How to Create a Personal Access Token
-
-To create the **Personal Access Token**, follow these steps:
-
-1. Click on the profile avatar
-2. Go to **Profile**
-3. Then go to **Account Security**
-4. Click on **New token...** button
-
-![Testomat.io - YouTrack Create Token](./images/New_pCUPQyzz_2024-10-31.png)
-
-5. Enter a **Token** name
-6. Select services (**YouTrack, YouTrack Administration**)
-7. Click on **Create** button
-
-![Testomat.io - YouTrack Personal Access Token](./images/New_WzTEWxkc_2024-10-31.png)
-
-Once the token has been created, copy it. Keep your Personal Access Token secure, as you’ll need it for the integration with Testomat.io.
-
-## How to Get a Project ID
-
-Finally, to get the **Project ID**, follow these steps:
-
-1. Open YouTrack [API Documentation](https://www.postman.com/youtrack-dev/youtrack/documentation/sd7pq8x/youtrack-rest-api)-> Administration -> Projects -> Read a List of Projects
-2. Get a request:
-
-```
-https://<your-workspace>.youtrack.cloud/api/admin/projects?fields=id,key,name
-
-```
-
-3. Paste your Personal Access Token
-4. Click **Send** button and get your Project ID in the response body (e.g. `"id": "0-1"`)
-
-![Get Project ID](./images/att1_youtrack.png)
-
-:::note
-
-The ID in the browser URL isn't the same as the project ID in the database.
-
-:::
-
-After collecting all necessary data, we can move on to Testomat.io.
-
-## How to Connect YouTrack in Testomat.io
-
-1. Select YouTrack from the list of available Issue Management Systems.
-
-![Testomat.io - Connect to YouTrack](./images/New_F8MYluVy_2024-10-31.png)
-
-2. Enter a **Profile Name**
-3. Paste YouTrack **Workspace Name**
-4. Paste YouTrack **Personal Access Token**
-5. Paste YouTrack **Project ID**
-6. Click on **Save** button
-
-![Testomat.io - YouTrack Configuration](./images/New_UTbONHqM_2024-10-31.png)
-
-If everything was done correctly, you will receive a confirmation message indicating that the YouTrack profile was successfully created.
-
-![Testomat.io - YouTrack Profile](./images/New_K1fdAe5k_2024-10-31.png)

package/skills/testeiya/testomatio-docs/docs/integrations/report-notifications/azure-devops.md

@@ -1,53 +0,0 @@
----
-title: Azure DevOps Notifications
-description: Configure Azure DevOps notifications in Testomat.io to automate issue creation for failed test runs. This guide explains linking Azure DevOps projects, and setting notification rules to streamline workflows and save time by automating detailed test result reporting.
-type: article
-url: https://docs.testomat.io/integrations/report-notifications/azure-devops
-head:   
-  - tag: meta
-    attrs:
-      name: keywords
-      content: Azure DevOps, Testomat.io, issue tracking, Notification rules,  Report Notifications, Azure DevOps integration, publish report, detailed test run results, test management, test automation, software testing, basic rules, advanced rules engine
----
-
-Testomat.io allows to create issue for failed test runs automatically in Azure DevOps. This option can be enabled in **Settings**.
-
-Before you set up Notification rules for Azure DevOps, you need to connect your Azure DevOps project with Testomat.io. Please follow the instuction in dedicated section - [Azure DevOps Configuration.](https://docs.testomat.io/integrations/issues-management/azure/)
-
-After the Azure DevOps is connected with Testomat.io, go to the **Settings (1) -> Report Notifications(2)** and click on **Add Notification Rule (3)**.
-
-![Testomat.io - Notification](./images/Notification.png)
-
-To enable Notification for Azure DevOps follow next steps:
-
-1. Add a title for Notification Rule.
-2. Choose **Azure DevOps** from the dropdown list.
-
-![Testomat.io - Notification Azure DevOps](./images/Azure_DevOps_1.png)
-
-3. Select **Azure DevOps integration** from dropdown list.
-4. Select **'Publish a report and use public link in report notification'** option, if you need it.
-5. Configure rules to define on which conditions this notification should be sent in **BASIC RULES** section 
-
-OR 
-
-use **ADVANCED RULES ENGINE** to enter your rule expression.
-
-6. Click on **Save** button.
-
-| **Basic Rules**             | **Advanced Rules Engine**             |
-| --------------------------- | ------------------------------------- |
-| ![Testomat.io - Basic rule](./images/Azure_DevOps_2.png) | ![Testomat.io - Advanced Rules Engine](./images/Azure_DevOps_3.png) |
-
-Testomat.io will now automatically create an issue with detailed Test Run results in your Azure DevOps project for any failed Test Runs. This eliminates the need to manually input data for each Test Run, saving you time and ensuring that all contributors are notified in a convenient way.
-
-![Testomat.io - Notification Azure DevOps](./images/Azure_DevOps_4.png)
-
-
-:::note
-
-When **'Publish a report and use public link in report notification'** option is enabled, the public report will be generated and everyone who has this link will be able to see it.
-
-![Testomat.io - Notification](./images/Public_Report.png)
-
-:::

package/skills/testeiya/testomatio-docs/docs/integrations/report-notifications/email.md

@@ -1,71 +0,0 @@
----
-title: Email Notifications
-description: Learn how to configure email notifications in Testomat.io to receive updates on test run results. This guide covers setting notification rules, customizing fields, and managing multiple email recipients effectively.
-type: article
-url: https://docs.testomat.io/integrations/report-notifications/email
-head:   
-  - tag: meta
-    attrs:
-      name: keywords
-      content: Testomat.io, Email notifications, Report Notifications, Add Notification Rule, Run context, RunGroup context, basic rules, advanced rules engine, Run Report, multiple notifications, test management, test automation, software testing
----
-
-Testomat.io allows sending Notifications for finished runs via Email.
-Let's see how it works!
-
-First, you need to set up Email notifications in the Settings tab:
-
-1. Go to **Settings**.
-2. Select **Report Notifications** option.
-3. Click on **Add Notification Rule**.
-
-![Testomat.io - Notification](./images/Notification.png)
-
-At this point your next steps are:
-
-4. Add a title for Notification Rule.
-5. Choose **Email** from the dropdown list.
-
-![Testomat.io - Notification Email](./images/Email_2.png)
-
-6. Enter one or multiple email addresses (separated by coma) to receive notifications.
-7. Select **'Publish a report and use public link in report notification'** option, if you need it.
-8. Select **Notification rule context**: Run or RunGroup.
-9. Add notification rules in **BASIC RULES** section
-
-OR
-
-use **ADVANCED RULES ENGINE** to enter your rule expression.
-
-10. Click on **Save** button.
-
-| **Basic Rules**             | **Advanced Rules Engine**             |
-| --------------------------- | ------------------------------------- |
-| ![Testomat.io - Basic rule](./images/Email_3.png) | ![Testomat.io - Advanced Rules Engine](./images/Email_4.png) |
-
-Now you have Email Notification enabled for the project. 
-
-![Testomat.io - Notification Email](./images/Email_5.png)
-
-**How does it work?**
-Each time Testomat.io creates Run Report, which corresponds to your Email Notification Rule, it will be sent to email.
-
-![Testomat.io - Notification Email](./images/Email_6.png)
-
-:::note
-
-You can set up multiple Email Notifications for different Rules.
-
-![Testomat.io - Notification Email](./images/Email_7.png)
-
-:::
-
-:::note
-
-When **'Publish a report and use public link in report notification'** option is enabled, the public report will be generated and everyone who has this link will be able to see it.
-
-![Testomat.io - Notification](./images/Public_Report.png)
-
-:::
-
-

package/skills/testeiya/testomatio-docs/docs/integrations/report-notifications/jira.md

@@ -1,52 +0,0 @@
----
-title: Jira Notifications
-description: Configure Jira notifications in Testomat.io to automate issue creation for failed test runs. This guide explains linking Jira projects, selecting issue types, and setting notification rules to streamline workflows and save time by automating detailed test result reporting.
-type: article
-url: https://docs.testomat.io/integrations/report-notifications/jira
-head:   
-  - tag: meta
-    attrs:
-      name: keywords
-      content: Testomat.io, Jira, automatic issue creation, failed test runs, Notification rules, Report Notifications, Add Notification Rule, Jira project, publish report, public link, basic rules, advanced rules engine, detailed test run results, test management, test automation, software testing
----
-
-Testomat.io allows to create Jira issue for failed test runs automatically. This option can be enabled in **Settings**.
-To do this, you need to connect Jira project with Testomat.io. Please see dedicated documentation - [Connecting to JIRA project.](https://docs.testomat.io/integration/jira/#connecting-to-jira-project)
-
-After the Jira is connected with Testomat.io, go to the **Settings (1) -> Report Notifications(2)** and click on **Add Notification Rule (3)**.
-
-![Testomat.io - Notification](./images/Notification.png)
-
-To create a new Notification Rule for Jira follow next steps:
-
-1. Add a title for Notification Rule.
-2. Choose **Jira** from the dropdown list.
-
-![Testomat.io - Notification Jira](./images/Jira_1.png)
-
-3. Select your dedicated Jira project from **Jira Project** dropdown list.
-4. Select needed issue type from **Issue Type** dropdown list.
-5. Select **'Publish a report and use public link in report notification'** option, if you need it.
-6. Configure rules to define on which conditions this notification should be sent in **BASIC RULES** section
-
-OR
-
-use **ADVANCED RULES ENGINE** to enter your rule expression.
-
-7. Click on **Save** button.
-
-| **Basic Rules**             | **Advanced Rules Engine**             |
-| --------------------------- | ------------------------------------- |
-| ![Testomat.io - Basic rule](./images/Jira_2.png) | ![Testomat.io - Advanced Rules Engine](./images/Jira_3.png) |
-
-Now Testomat.io will create an issue with detailed information on Test Run results within your Jira project for failed Test Runs. So you don't need to put all the data on each Test Run manually. This helps to save time and notify all contributors in a convenient way.
-
-![Testomat.io - Notification Jira](./images/Jira_4.png)
-
-:::note
-
-When **'Publish a report and use public link in report notification'** option is enabled, the public report will be generated and everyone who has this link will be able to see it.
-
-![Testomat.io - Notification](./images/Public_Report.png)
-
-:::

package/skills/testeiya/testomatio-docs/docs/integrations/report-notifications/ms-teams.md

@@ -1,60 +0,0 @@
----
-title: Microsoft Teams Notifications
-description: Configure Microsoft Teams notifications in Testomat.io to receive test updates. This guide provides detailed steps for setting up incoming webhooks in Teams, generating a Webhook URL, and linking it with Testomat.io for seamless test result notifications.
-type: article
-url: https://docs.testomat.io/integrations/report-notifications/ms-teams
-head:
-  - tag: meta
-    attrs:
-      name: keywords
-      content: Microsoft Teams integration, Testomat.io, failed test runs, Notification rules, Report Notifications, Add Notification Rule, publish report, public link, basic rules, advanced rules engine, detailed test run results, test management, test automation, software testing
----
-
-To send noitifcations in MS Teams, first you need to set up **Incoming Webhooks** for your channel.
-
-Steps to configure:
-
-1. Navigate to **Apps** panel.
-2. Search for **Incoming Webhook** and add it ([read more here](https://learn.microsoft.com/en-us/microsoftteams/platform/webhooks-and-connectors/how-to/add-incoming-webhook?tabs=newteams%2Cdotnet)).
-
-![Testomat.io - Notification Teams](./images/Teams_1.png)
-
-3. Configure it and copy Webhook URL.
-
-![Testomat.io - Notification Teams](./images/Teams_2.png)
-
-After Teams is Set up, open your Project in Testomat.io and go to the **Settings (1) -> Report Notifications(2)** and click on **Add Notification Rule (3)**.
-
-![Testomat.io - Notification](./images/Notification.png)
-
-Create a new Notification Rule for Teams in Testomat.io following next steps:
-
-1. Add a title for Notification Rule.
-2. Choose **Microsoft Teams** from the dropdown list.
-
-![Testomat.io - Notification Teams](./images/Teams_3.png)
-
-3. Paste Teams Webhook URL.
-4. Select **'Publish a report and use public link in report notification'** option, if you need it.
-5. Configure rules to define on which conditions this notification should be sent in **BASIC RULES** section
-
-OR
-
-using **ADVANCED RULES ENGINE** to enter your rule expression.
-
-6. Click on **Save** button.
-
-| **Basic Rules**             | **Advanced Rules Engine**             |
-| --------------------------- | ------------------------------------- |
-| ![Testomat.io - Basic rule](./images/Teams_4.png) | ![Testomat.io - Advanced Rules Engine](./images/Teams_5.png) |
-
-**How does it work?**
-Each time Testomat.io creates Run Report, which corresponds to your Teams Notification Rule, it will be sent to selected Teams channel.
-
-:::note
-
-When **'Publish a report and use public link in report notification'** option is enabled, the public report will be generated and everyone who has this link will be able to see it.
-
-![Testomat.io - Notification](./images/Public_Report.png)
-
-:::

package/skills/testeiya/testomatio-docs/docs/integrations/report-notifications/rules.md

@@ -1,267 +0,0 @@
----
-title: Notification Rules
-description: Learn how to configure and manage notifications in Testomat.io for various channels, including Email, Slack, MS Teams, and Jira. This guide covers setting up notification rules, both basic and advanced, and demonstrates how to send alerts based on specific test run conditions. Streamline communication with automatic notifications for failed tests, test completion, and other custom triggers.
-type: article
-url: https://docs.testomat.io/integrations/report-notifications/rules
-head:
-  - tag: meta
-    attrs:
-      name: og:image
-      content: https://docs.testomat.io/_astro/Basic_Rules.BGM4UhZJ_Z1Yiri8.webp
-
-  - tag: meta
-    attrs:
-      name: keywords
-      content: Testomat.io, notifications, Email alerts, Email notifications, Slack notifications, MS Teams, Jira integration, Jira Notification, Azure DevOps, Telegram notification, Notification rules, test runs, automated alerts, CI notifications, QA tools, notification channels, Report Notification, Basic rules, Advanced rules engine, Run Group Notifications, test management, test automation, software testing
----
-
-**Notification** is one of the attractive Agile testing tool features. Test management web application Testomat.io provides for collaborative purposes notification QA team, development team and business. So, keeping the teams engaged with project updates and getting fast feedback from business owners is simpler than ever! In addition, you as the test manager or team owner through **Team Management Dashboard** will have end-to-end visibility on your collaboration process.
-
-**Available to notify by:**
-
-- **Email** notifications.
-- **Slack** notification.
-- **Microsoft Teams** notification.
-- **Jira** notification.
-- **Azure DevOps** notification.
-- **Telegram** notification.
-
-Testomat.io allows sending notifications for finished runs:
-
-- Send brief reports to stakeholders.
-- Notify team members of failed or passed tests.
-- Notify test results after test executions.
-- Configure on which condition notification should be sent.
-
-Testomat.io has powerful rule engine which can be used to define on which conditions a notification should be sent. You can have multiple notification types with different notification channels in use for a single project.
-
-![Testomat.io - Notification](./images/Rules.png)
-
-## How to Setup Notification
-
-Sending configuration thanks to seamless integration is really simple. Enable notification you can on **Settings Dashboard** -> **Report Notification**. You are free to select an environment and configure condition notification should be sent. Simply fill the fields using **Basic rules**. Then modify your notification scheme to notify a group of people of your choice. Also, notification settings might be configured through the **Advanced rules engine** with using variables.
-
-You can read more about how to setup your notification in the sections below.
-
-## Basic Rules
-
-There is a basic and advanced rules engine.
-
-Inside Basic rules you can define simple conditions on which notifications should be sent:
-
-1. Runs with title.
-2. Runs of RunGroup with title.
-3. Run Type.
-4. Run Status.
-
-![Testomat.io - Basic Rules](./images/Basic_Rules.png)
-
-For instance, here is the rule for all manual runs with **"Release"** word in title to be reported:
-
-![Testomat.io - Basic Rules](./images/Basic_Rules_1.png)
-
-## Quick Toggle for Report Notifications
-You can enable or disable report notifications directly from the notification profile using a quick toggle. Switch notifications on or off without changing the full configuration. This is useful when notifications need to be temporarily paused during debugging or active development.
-
-## Advanced Rules
-
-The advanced rules engine allows writing conditions in a special expression language similar to Ruby or JavaScript.
-
-This is the same rule we defined previously in Basic mode written in the format of Advanced mode. A notification will be sent for all manual runs that contain the word "Release":
-
-```
-manual and contains(run, "Release")
-```
-
-A complete list of allowed variables:
-
-- `automated` - boolean. True if a run is automated
-- `manual` - boolean. True if a run is manual
-- `has_failed` - boolean. True if a run has failed
-- `has_passed` - boolean. True if a run has passed
-- `was_terminated` - boolean. True if a run was terminated
-- `run` - string. Title of a run
-- `rungroup` - title. Title of rungroup a run belongs to
-- `status` - string. Status of run, 'passed' or 'failed' as a string.
-- `started_at` - datetime. Time when the run was started.
-- `finished_at` - datetime. Time when the run was finished
-- `passed_tests` - collection. A list of all passed tests in a run.
-- `failed_tests` - collection. A list of all failed tests in a run.
-- `skipped_tests` - collection. A list of all skipped tests in a run.
-- `env` - collection. A list of environments.
-
-An expression should return a boolean value. To deal with types other than boolean functions and methods can be used:
-
-**String**
-
-String values can be checked with equal `==` or not equal `!=` operators. Also there is `contains` function which checks inclusion of a string in another string:
-
-```
-contains(run, "New")
-```
-
-**Collection**
-
-Collections contain an array of objects.
-
-Use `.size` to check for the size of items in the collection. For instance, this rule is activated when a number of failed tests is more than 10.
-
-```
-failed_tests.size > 10
-```
-
-Collection of tests can be filtered. Tests in the collection have following properties:
-
-- `test['title']` - title of a test
-- `test['suite']` - title of a suite of a test
-- `test['id']` - id of a test
-- `test['suite_id']` - id of a suite
-- `test['status']` - status of a test in collection
-
-For instance, this is how to check if a collection of failed tests contains at least one test with `@important` tag in its name:
-
-```
-failed_tests.filter(test, contains(test["title"], "@important")).size > 0
-```
-
-**DateTime**
-
-`started_at` and `finished_at` variables are of datetime type. They have properties from [Date](https://ruby-doc.org/stdlib-2.6.1/libdoc/date/rdoc/Date.html) and [DateTime](https://ruby-doc.org/stdlib-2.6.1/libdoc/date/rdoc/DateTime.html) classes of Ruby that can be used in expressions. Most used ones are:
-
-- `hour`
-- `minute`
-- `day`
-- `wday`
-- `month`
-- `year`
-- [etc](https://ruby-doc.org/stdlib-2.6.1/libdoc/date/rdoc/Date.html)
-
-For instance, this is how notification can be enabled for reports finished in non-business time:
-
-```
-(finished_at.hour > 18 or finished_at.hour < 9)
-```
-
-## Examples
-
-**Notify when tests are failing on CI:**
-
-To match tests executed on CI specify a Run title with "[CI]" prefix to identify that these tests were executed on CI:
-
-```
-TESTOMATIO_TITLE="[CI] Automated Tests"
-```
-
-Then write a notification rule that will check only for failing runs with "[CI]" in their title:
-
-```
-contains(run, "[CI]") and has_failed
-```
-
-**Notify when automated tests are terminated:**
-
-```
-automated and was_terminated
-```
-
-### Examples for Runs Notifications
-
-**Notify when a Run has failed between 10 PM and 9 AM:**
-
-```
-has_failed and (finished_at.hour > 22 or finished_at.hour < 9)
-```
-
-**Notify when an automated Run has failed on alpha environment:**
-
-```
-automated and has_failed and contains (env, "alpha”)
-```
-
-**Notify when a Run that contains at least one test with the word "autocomplete" in the title has passed:**
-
-```
-has_passed and passed_tests.filter(test, contains(test["title"], "autocomplete")).size > 0
-```
-
-For example:
-
-![Testomat.io - Run Rules](./images/Run_rule.png)
-
-And Run that matches this Notification rule:
-
-![Testomat.io - Run Rules](./images/Run_rule_1.png)
-
-## Run Group Notifications
-
-:::note
-
-Please note that Run Group Notifications are available for **Email notification** type only.
-
-:::
-
-To configure Notification Rule for Run Group you need:
-
-1. Select rungroup for Notification rule context
-2. Add your Rule Expression, for example, you can use `rungroup_finished` variable if you want to get notification when all Run report inside the group are finished.
-
-![Alt text](./images/Rungroup.png)
-
-### Rules for Run Group Notifications
-
-The rules engine allows writing conditions in a special expression language similar to Ruby or JavaScript.
-
-A list of allowed variables:
-
-- `title` - string. Title of a rungroup
-- `rungroup_finished` - boolean. True if all runs completed => True if rungroup contains only finished runs.
-- `runs` - collection. A list of all runs inside a rungroup
-- `finished_runs` - collection. A list of finished (passed or failed) runs inside a rungroup
-- `ongoing_runs` - collection. A list of pending runs (scheduled, in progress) runs inside a rungroup
-- `failed_runs` - collection. A list of failed runs inside a rungroup
-
-### Examples for Run Groups Notifications
-
-**Notify when all runs within one Run Group (Run Group include more than 1 run) are finished:**
-
-```
-(runs.size > 1) and rungroup_finished
-```
-
-**Notify when there is at least one run in the `finished_runs` collection whose `finished_at` timestamp is older than 100 seconds ago:**
-
-```
-finished_runs.filter(run, run['finished_at'] < 100.seconds_ago).size > 0
-```
-
-**Notify when there are no currently ongoing runs in the run Group (means all runs are finished):**
-
-```
-ongoing_runs.filter(run, run['created_at'] <= 0.seconds_ago).size == 0
-```
-
-**Notify when next rules are met:**
-
-- the title of the Run Group contains the substring 'str-' and
-- all runs within this Run Group are finished and
-- at least one of the runs within this Run Group has a title that contains the exact string 'islast: true'
-
-```
-contains(title, "str-") and rungroup_finished and (runs.select(run, contains(run["title"], "islast: true")).size > 0)
-```
-
-For example:
-
-![Testomat.io - RunGroup Rules](./images/RunGroup_rule.png)
-
-And Run Group that matches this Notification rule:
-
-![Testomat.io - RunGroup Rules](./images/RunGroup_rule_1.png)
-
-:::note
-
-Testomat.io allows you to check which of your Runs or Run Groups match the created notification rule:
-
-![Testomat.io - Rule Check](./images/Rule_check.gif)
-
-:::