testeiya 0.2.1 → 0.3.9

package/skills/testeiya/testomatio-docs/docs/project/runs/archive-runs-and-groups.md

@@ -1,176 +0,0 @@
----
-title: Archive Runs & RunGroups
-description: Testomat.io's archiving feature helps users maintain a clean and organized Runs Dashboard by moving irrelevant test runs and groups to dedicated archive sections. This guide details how to archive single or multiple runs/groups, access archived data with filtering capabilities, manage data retention periods, and unarchive items to restore them to the main view, ensuring historical data preservation and efficient focus.
-type: article
-url: https://docs.testomat.io/project/runs/archive-runs-and-groups
-head:
-  - tag: meta
-    attrs:
-      name: keywords
-      content: managing test runs, rungroups, test management, Testomat.io, multi-selection, archiving, test reporting, filtering, archive runs, archive rungroups, rungroup structure, run report, unarchive runs, unarchive rungroups, data organization.
----
-
-## How to Archive Runs & RunGroups
-
-Archive provides you with the ability to declutter the main Runs Dashboard, ensuring only relevant and active test runs take center stage while preserving historical data.
-
-You can archive Runs or Groups at any time.
-
-**Archive a Single Run or RunGroup:**
-
-1. Сlick the **'Extra menu'** button for Run/Group you want to archive.
-2. Click the **'Archive'** button.
-
-![Testomat.io - Archive runs](./images/Archive_Run_2.png)
-
-3. Click the **'Confirm'** button to archive the run.
-
-![Testomat.io - Confirm runs](./images/Archive_Run_3.png)
-
-OR
-
-Use **'Multi-select'** to archive several Runs simultaneously (this option is for Runs only, not RunGroups).
-
-**Archive Multiple Runs simultaneously:**
-
-1. Click the **'Multi-select'** icon to enable multi-selection.
-2. Select runs you want to archive.
-3. Click the **'Archive'** button.
-
-![Testomat.io - Archive runs](./images/Archive_Run_4.png)
-
-4. Click the **'Confirm'** button to archive the runs.
-
-![Testomat.io - Confirm runs](./images/Archive_Run_5.png)
-
-Archived Runs or Groups are removed from the main Runs board and got the **archived** badge.
-
-![Testomat.io - Archived badge](./images/Archive_Run_6.png)
-
-:::note
-
-When a Run or RunGroup containing unfinished (Pending) tests is archived, the run status changes to **Terminated**. All **Pending** tests become **Skipped**, while tests in other statuses remain **unchanged**.
-
-![Pending status](./images/att5_3703.png)
-
-:::
-
-**To access archived Runs/RunGroups:**
-
-- Click on **'Runs/Groups Archive'** section at the bottom of the page.
-
-![Testomat.io - Run overview](./images/Archive_Run_1.png)
-
-OR
-
-- Click the **'Extra menu'** button at the top right corner and select the specific archive section that you need.
-
-![Testomat.io - Run overview](./images/Archive_Run_1a.png)
-
-Manually archive runs that are no longer in focus, to maintain a clean and organized main board tailored to your ongoing testing priorities.
-
-## Runs Archive
-
-Archived runs find a new home in the dedicated **'Runs Archive'** section. This segregated space ensures that your archived data is easily accessible without cluttering the main board. The Runs Archive comes equipped with filtering capabilities.
-To view all filtering options, click on **'Filter'** icon.
-
-![Testomat.io - Runs Archive](./images/Archive_Run_8.png)
-
-:::note
-
-By default, Testomat.io automatically purges all runs (archived and non-archived) older than 90 days on a daily basis. But you have the flexibility to adjust this retention period based on your project requirements. This will allow you to keep the perfect balance between data cleanliness and historical record preservation.
-
-:::
-
-You can change the default purge period in two ways:
-
-1. On **'Runs Archive'** page click the **'Extra menu'** button.
-2. Clickthe **Purge Old Runs** button.
-
-![Testomat.io - Runs Archive](./images/Archive_Run_9.png)
-
-3. Specify the period after which runs will automatically purge daily.
-4. Click the **'Save'** button.
-
-![Testomat.io - Runs Archive](./images/Archive_Run_10.png)
-
-Alternatively, specify the term on **'Project Settings'** page.
-
-![Testomat.io - Runs Archive](./images/Archive_Run_11.png)
-
-Additionally, all archived runs can be displayed as a group, which can be organized by enabling the **'Rungroup Structure'** toggle.
-
-![Testomat.io - Rungroup Structure button](./images/Archive_Run_12.png)
-
-Testomat.io also allows you to view the Run Report of an archived test run by simply clicking on it.
-
-![Testomat.io - Run Report](./images/Archive_Run_13.png)
-
-## Groups Archive
-
-Archived RunGroups are located in a separate section called **'Groups Archive'**. You can search, filter, and sort archived RunGroups to quickly find what you need.
-
-**Search** — use the search field in the toolbar to find archived RunGroups by name. Results update instantly as you type, showing the number of groups found. Click **x** to clear the search.
-
-![Search](./images/att1_3703.png)
-
-**Filter** — click the **'Filter'** icon to filter archived RunGroups by:
-
-- **Group type** — Build, Release, or Sprint
-- **Finish Range** — a specific date range when the group was finished
-
-![Filters](./images/att2_3703.png)
-
-**Sort** — click the **'Sorting'** button in the top-right corner to sort groups by:
-
-- **ASC by Name** — alphabetically A→Z
-- **DESC by Name** — alphabetically Z→A
-- **ASC by Date** — oldest finished first
-- **DESC by Date** — newest finished first
-
-![Sorting](./images/att3_3703.png)
-
-By clicking on an archived RunGroup, you can see the RunGroup Report.
-
-![RunGroup Archive Report](./images/att4_3703.png)
-
-## How to Unarchive Runs & RunGroups
-
-- Archived runs and groups can be unarchived. This allows you to display them on the main panel.
-- Restoring a RunGroup also restores all its archived runs.
-
-**Unarchive Runs:**
-
-1. Сlick the **'Extra menu'** button for the run.
-2. Select the **'Unarchive'** option from the dropdown menu.
-
-![Testomat.io - Unarchive Runs Archive](./images/Archive_Run_17.png)
-
-3. Click **'Confirm'** button.
-
-![Testomat.io - Unarchive Runs Archive](./images/Archive_Run_18.png)
-
-OR
-
-Use **'Multi-select'** to unarchive a few Runs simultaneously.
-
-1. Click the **'Multi-select'** icon to enable multi-selection.
-2. Select the runs you want to unarchive.
-3. Click the **'Unarchive'** button.
-
-![Testomat.io - Archive runs](./images/Archive_Run_21.png)
-
-4. Click the **'Confirm'** button to unarchive the runs.
-
-![Testomat.io - Confirm runs](./images/Archive_Run_22.png)
-
-**Unarchive RunGroups:**
-
-1. Сlick the **'Extra menu'** button for the RunGroup.
-2. Select the **'Unarchive'** option from the dropdown menu.
-
-![Testomat.io - Unarchive Groups Archive](./images/Archive_Run_19.png)
-
-3. Click the **'Confirm'** button.
-
-![Testomat.io - Unarchive Groups Archive](./images/Archive_Run_20.png)

package/skills/testeiya/testomatio-docs/docs/project/runs/custom-statuses.md

@@ -1,195 +0,0 @@
----
-title: Custom Statuses
-description: Learn how to use custom test result statuses in Testomat.io. This guide explains how to configure additional result messages, apply them during manual test runs, and use them for advanced analytics and reporting.
-type: article
-url: https://docs.testomat.io/project/runs/custom-statuses
-head:
-  - tag: meta
-    attrs:
-      name: keywords
-      content: custom test statuses, manual test management, QA test result customization, software testing workflow, test result labeling, advanced test filtering, test case tracking, QA reporting tools, testing analytics, filter test runs, query language for testing, RQL TQL filters, custom test outcomes, passed failed skipped test status, categorize test results, improve test visibility, test execution tracking, test result analysis, quality assurance tools, test automation support, testing dashboard customization, test case result statuses, manual QA process optimization
----
-
-## Custom Statuses
-
-Custom Statuses let QA teams extend the context of test results by going beyond the standard test results — PASSED, FAILED, and SKIPPED. They are especially useful in manual testing to capture workflow-specific outcomes that default results alone cannot express.
-
-Each custom status is linked to one of the default test results and can:
-
-- Clarify the reason behind a passed, failed, or skipped result
-- Indicate follow-up actions or required next steps
-- Enhance filtering and analysis using a query language
-
-### How to Configure Custom Statuses
-
-When you create a new project, the system provides a set of default custom statuses to help you get started right away. However, you can fully customize these statuses to better fit your team’s workflow and testing needs. Let's see how it works.
-
-1. Open **Settings** in the sidebar
-2. Click on the **Custom Statuses** tab
-
-![Custom Statuses](./images/att_1.png)
-
-You can now add or edit existing statuses by clicking on the relevant field where you want to make changes.
-
-3. Write a report message per line, for example, **'Needs review'**
-4. Click the **'Update'** button to save the changes
-
-![Update button](./images/att_2.png)
-
-The same actions can be applied to each field, such as **'Custom statuses when test is failed'** or **'Custom statuses when test is skipped'**.
-
-### How to Apply Custom Statuses During Test Execution
-
-Custom statuses appear as an additional optional field below the standard test results: PASSED, FAILED, and SKIPPED. When you select one of these standard results during a manual test run, the custom statuses configured specifically for that result become available.
-
-For example, if your test result is **'PASSED'**, you can optionally select a custom status configured for **'PASSED'**, such as **'Needs review'** or another one.
-
-![Apply Custom Statuses During Test Execution](./images/gif_1.gif)
-
-:::note
-
-Custom statuses do not replace the standard test results; they provide an additional layer of detail. They are only available after selecting a standard result. If no standard result is chosen, the custom status field remains hidden.
-
-:::
-
-For detailed steps on setting test results during manual runs, see:
-[How to Set Test Case Results in Manual Run](https://docs.testomat.io/project/runs/running-tests-manually/#how-to-set-test-case-results-in-manual-run).
-
-### How to Filter Test Results by Custom Statuses
-
-Find what matters quickly by filtering your test results based on custom statuses — either within a single run or across multiple runs using Query Language.
-
-- **Quick Filter**: Use the Custom Statuses dropdown in the Run sidebar or Run Report to view results within a single test run
-
-![Quick filter](./images/gif_2.gif)
-
-- **Advanced Filter (Query Language)**: Use query language to search across runs or tests and combine filters for deeper analysis
-
-**Filtering in Runs Query Editor**
-
-1. Go to the **Runs** tab in the sidebar
-2. Click on Query Language Editor at the top of the page
-   (Or simply start typing in the search field)
-
-![Query Language Editor](./images/att_3.png)
-
-3. In the Runs Query Editor, enter your query,
-
-- Filter by a single custom status:
-
-```ini
-has_custom_status == 'Known issue'
-```
-
-- Filter by multiple statuses:
-
-```ini
-has_custom_status in ['Expected behavior','Minor issue','Management decision']
-```
-
-4. Click the **Apply** button
-
-![Apply_button](./images/att_4.png)
-
-After applying the query, you will see a filtered list of test runs that match your criteria. This helps you quickly understand how much of your testing scope falls under a particular custom status.
-
-![query result](./images/att_5.png)
-
-**Filtering in Tests Query Editor**
-
-In contrast, the Tests Query Editor uses the field **custom_status** to filter individual tests by their custom status.
-
-1. Go to the **Tests** tab in the sidebar
-2. Click on Query Language Editor at the top of the page
-   (Or simply start typing in the search field)
-
-![Tests Query Language Editor](./images/att_8.png)
-
-3. In the Tests Query Editor, enter your query,
-
-- Filter by a single custom status:
-
-```ini
-custom_status in ['Expected behavior','Minor issue','Management decision']
-```
-
-- Filter by multiple statuses:
-
-```ini
-custom_status in ['Expected behavior','Minor issue','Management decision']
-```
-
-4. Click the **Apply** button
-
-![Apply](./images/att_9.png)
-
-After applying the query, you will see a filtered list of tests that match your criteria. This helps you quickly identify tests categorized under a particular custom status.
-
-![Result](./images/att_10.png)
-
-See the Query Language documentation for a full list of available variables to use in run and test queries — including custom statuses:
-
-- [Run Query Language (RQL) documentation for run queries](https://docs.testomat.io/advanced/tql/#runs-variables)
-- [Test Query Language (TQL) documentation for test queries](https://docs.testomat.io/advanced/tql/#tests-variables)
-
-### How to Use Custom Statuses in Analytics
-
-You can use Сustom Statuses in Analytics to gain better visibility into your testing outcomes — both at the run level and the test level.
-
-**Custom Charts** help you:
-
-- Track the status and progress of tests over time
-- Identify recurring issues or bottlenecks
-- Make informed decisions based on detailed test outcome trends
-
-**Example queries for test runs (RQL)**:
-
-```ini
-
-has_custom_status in ['Blocked', 'Obsolete', 'Missing implementation', 'Unexecuted', 'Not ready', 'No time']
-has_custom_status in ['Expected error', 'Known issue', 'Dependent defect']
-has_custom_status in ['Expected behavior', 'Minor issue', 'Management decision']
-
-```
-
-![Custom Statuses_Analytics](./images/att_6.png)
-
-**Example queries for individual tests (TQL)**:
-
-```ini
-
-custom_status in ['Blocked', 'Obsolete', 'Missing implementation', 'Unexecuted', 'Not ready', 'No time']
-custom_status in ['Expected error', 'Known issue', 'Dependent defect']
-custom_status in ['Expected behavior', 'Minor issue', 'Management decision']
-
-```
-
-![Test_Custom Statuses_Analytics](./images/att_11.png)
-
-Additionally, use the Timeline view in the sidebar to visualize how custom statuses evolve over time across runs and tests.
-
-![Timeline view](./images/att_7.png)
-
-For detailed instructions on creating and customizing charts, see:
-[How to Use Custom Charts with Test Runs](https://docs.testomat.io/project/analytics/#how-to-use-custom-charts-with-test-runs).
-
-:::note
-
-Keep queries up to date. If your team updates or renames custom statuses, update your queries accordingly, including those used in analytics dashboards. Otherwise, the filters may not return the expected results or and relevant data may be missed.
-
-:::
-
-**Use Cases:**
-
-- Add a custom status to clarify the reason behind a test result (e.g. further investigation needed, blocked by dependencies, waiting for implementation)
-- Highlight tests that require specific follow-up actions, such as re-execution, review, or coordination with other teams
-- Categorize skipped or failed tests to reflect different workflow conditions or business decisions
-- Use meaningful labels to improve visibility and collaboration during triage or reporting
-
-**Tips:**
-
-- Keep custom statuses short and action-oriented
-- Use consistent naming conventions for easier filtering
-- Regularly review and remove unused statuses to avoid clutter
-- Maintain consistent names across projects to improve team collaboration
-- Avoid long descriptive phrases; use concise labels like Blocked, Needs Review, etc.

package/skills/testeiya/testomatio-docs/docs/project/runs/environments.md

@@ -1,203 +0,0 @@
----
-title: Environments
-description: Learn how to configure, manage, and view test results across multiple environments in Testomat.io. This guide covers environment setup in project settings, test execution in different environments (including cross-browser and cross-platform), viewing environment-specific results, CI/CD integration, and troubleshooting common issues.
-type: article
-url: https://docs.testomat.io/project/runs/environments
-head:
-  - tag: meta
-    attrs:
-      name: keywords
-      content: environments, test environments, configure environments, multi-environment testing, CI/CD testing, test reporting, environment setup, Testomat.io, QA environments, cross-browser testing, cross-platform testing, project settings
----
-
-Multi-Environment Feature allows you to execute the same set of test cases across multiple environments — such as different operating systems, browsers, or devices. This is essential for validating cross-platform compatibility, behavior under various configurations, and deployment consistency.
-
-You can run tests in multiple environments either in a single run, sequentially, or in parallel — depending on your project needs and available resources.
-
-## How to Configure Environments
-
-Configuring environments means defining different platforms, browsers, devices, or other variables where you want to run your tests. Managing environments centrally in the project settings ensures clarity, reduces errors, and improves reporting since all test results are linked to standardized environment names. This setup supports consistent and reusable environment definitions across manual test runs, automation, and CI/CD.
-
-To better structure and filter environments, you can organize them using categories (groups) in the format **{category}:{value}**:
-
-```
-Browser:Chrome
-OS:Windows
-Device:iOS
-Stage:Dev
-```
-
-This structure allows flexible combination and filtering of environments.
-
-### How to Add New Environments
-
-To get started with environments, you’ll need to add them in your project settings. Follow these simple steps:
-
-1. Navigate to **Settings** in the sidebar
-2. Click the **Environments**
-3. Enter an environment(s) per line
-4. Click the **Update** button
-
-![Environments updated](./images/att1_362.png)
-
-Need to update or edit your environments later? Just follow the same steps above to make changes anytime.
-
-## How to Run with Multi-Environments
-
-This section explains how to execute tests using different Multi-Environment configurations. After setting up environments in project settings, you can choose among several run modes depending on your testing strategy and infrastructure capabilities.
-
-Each Multi-Environment group creates a separate test run. All created runs are collected in a dedicated group for easier management and overview.
-
-### Run Multi-Environment Tests in One Run
-
-This mode runs a single test run where each test is executed across all configured environments within one group. For example, if you select **Browser: Chrome, OS: Windows, and Stage: Dev**, the tests will run with this combined environment configuration. Test results are shown grouped by these environment settings inside this single test run.
-
-How to run:
-
-1. Click the **Runs** in the sidebar
-2. Click on **Manual Run** button
-
-![Manual Run](./images/att2_362.png)
-
-3. Click **+** button to set environments for execution
-
-![Set environment button](./images/att3_362.png)
-
-4. Click on **-** button or Group 1, to trigger the dropdown list with all set up environments
-
-![dropdown list with environments](./images/gif1_362.gif)
-
-5. Select one or more environments from the **Environment** dropdown list for the first group (e.g., `Browser:Chrome`, `OS:MacOS`, `Stage:Dev`)
-6. Click the **Save** button
-7. Click **Launch** button to run the single test run
-
-![Launch single run with environments](./images/att4_362.png)
-
-After launch, manually set test results for each test with all configured environments. Details: [How to set test case results in Manual Run](https://docs.testomat.io/project/runs/running-tests-manually/#how-to-set-test-case-results-in-manual-run).
-
-![Launched run with test result](./images/att8_362.png)
-
-### Run Multi-Environment Tests Sequentially
-
-This mode creates separate runs for each environment group and executes them one after another in sequence.
-
-Use this mode when:
-
-- Infrastructure resources are limited
-- You need to control execution order
-- Sequential validation is required
-
-**Example:**
-
-You have the following environment configurations:
-
-- Group 1 - `Browser:Chrome + OS:Windows + Stage:Dev`
-- Group 2 - `Browser:Safari + OS:MacOS + Stage:Dev`
-
-Testomat.io will create two separate test runs:
-
-- Run #1 — Browser:Chrome + OS:Windows + Stage:Dev
-- Run #2 — Browser:Safari + OS:MacOS + Stage:Dev
-
-How to run:
-
-1. Click the **Runs** in the sidebar
-2. Click on **Manual Run**
-
-![Manual Run](./images/att2_362.png)
-
-3. Click **+** to set environments for execution
-
-![Set environment button](./images/att3_362.png)
-
-4. Click on Group 1 or **-** button, to trigger the dropdown with all set up environments
-
-![dropdown list with environments](./images/gif1_362.gif)
-
-5. Select one or more environments from the **Environment** dropdown list for the first group (e.g., `Browser:Chrome + OS:Windows + Stage:Dev`)
-6. Use **Add Environment** button to add multiple groups
-7. Select one or more environments from the **Environment** dropdown list for the next groups (e.g., `Browser:Safari + OS:MacOS + Stage:Dev`)
-8. Click the **Save** button
-
-![Save configured environments](./images/gif2_362.gif)
-
-Once environments are configured,
-
-9. Click **Launch in Sequence** button to start runs one after another, sequentially
-
-![Launch in Sequence](./images/att5_362.png)
-
-After launch, manually set test results for each run separately. Details: [How to set test case results in Manual Run](https://docs.testomat.io/project/runs/running-tests-manually/#how-to-set-test-case-results-in-manual-run).
-
-### Run Multi-Environment Tests in Parallel (Launch All)
-
-This mode runs tests simultaneously across all selected environment groups. Each group runs as a separate test run.
-
-Use this mode when:
-
-- You want to reduce testing time with parallel execution
-- You have sufficient infrastructure resources
-- You want independent access to results per environment group
-
-**Example:**
-
-You have the following environment configurations:
-
-- Group 1 - `Browser:Chrome + OS:Windows + Stage:Dev`
-- Group 2 - `Browser:Safari + OS:MacOS + Stage:Dev`
-
-Testomat.io will create two separate test runs:
-
-- Run #1 — Browser:Chrome + OS:Windows + Stage:Dev
-- Run #2 — Browser:Safari + OS:MacOS + Stage:Dev
-
-How to run:
-
-1. Click the **Runs** in the sidebar
-2. Click on **Manual Run**
-
-![Manual Run](./images/att2_362.png)
-
-3. Click **+** to set environments for execution
-
-![Set environment button](./images/att3_362.png)
-
-4. Click on first group or **-** button, to trigger the dropdown with all set up environments
-
-![dropdown list with environments](./images/gif1_362.gif)
-
-5. Select one or more environments from the **Environment** dropdown list for the first group (e.g., `Browser:Chrome + OS:Windows + Stage:Dev`)
-6. Use **Add Environment** button to add multiple groups
-7. Select one or more environments from the **Environment** dropdown list for each additional group (e.g., `Browser:Safari + OS:MacOS + Stage:Dev`)
-8. Click the **Save** button
-
-![Save configured environments](./images/gif2_362.gif)
-
-9. Click **Launch All** button to start the run tests simultaneously
-
-![Launch All button](./images/att6_362.png)
-
-Once the run is launched, set the test results for each test with all configured environments simultaneously.
-
-![Launch All](./images/att7_362.png)
-
-### Run Environments via CI/CD
-
-Testomat.io supports executing tests with specific environment configurations directly from your CI/CD pipelines. You can pass environment parameters at runtime via command line or API, enabling fully automated multi-environment testing. This allows triggering test runs based on CI context, like branches or deployment stages (dev, staging, production).
-
-For setup instructions and usage examples, refer to the official documentation:[Environment Configuration in CI/CD](https://docs.testomat.io/integrations/continuous-integration/#environment-configuration)
-
-## Key Benefits and Use Cases
-
-Using environments in Testomat.io enhances testing efficiency by:
-
-- Run tests across different browsers and OSs (Chrome, Safari, Windows, macOS, etc.) to ensure compatibility
-- Test on Android, iOS, and other devices
-- Separate runs for dev, staging, and production environments
-- Choose between sequential or parallel runs depending on resources and needs
-- Trigger test runs with environment parameters based on branches or other CI context
-- Define environments once and reuse across all runs without duplicating test cases
-- Filter and analyze test results by specific environments for clearer insights
-- Assign environment-specific test runs to different team members for faster feedback
-- Use clear groups like Browser, OS, or Stage and combine them for precise targeting
-- Set up key environments early in the project to save time and simplify processes