testeiya 0.2.0 → 0.3.1-0.1

package/skills/testeiya/testomatio-docs/docs/project/import-export/import/import-tests-from-testrail.md

@@ -1,82 +0,0 @@
----
-title: Import Tests From TestRail
-description: Learn how to export tests from TestRail using three different methods CSV export, the built-in UI tool, and the migration script. This guide walks you through the process of exporting test cases from TestRail, whether you're using the CSV export feature for easy data transfer, the intuitive UI tool for streamlined export, or the migration script for more advanced needs. Each method is explained in detail, allowing you to choose the best option for exporting your test data efficiently.
-type: article
-url: https://docs.testomat.io/project/import-export/import-tests-from-testrail
-head:
-  - tag: meta
-    attrs:
-      name: og:image
-      content: https://docs.testomat.io/_astro/import_from_testrail_button.CWNnrpnC_JhLel.webp
-      
-  - tag: meta
-    attrs:
-      name: keywords
-      content: Testomat.io, CSV, TestRail, test import, TestRail migration, manual tests, automated tests, test management, custom XLS
----
-
-> If you have existing tests in TestRail and wish to migrate to Testomat.io, this guide will walk you through the process of importing your tests into Testomat.io.
-
-Currently, Testomat.io supports three methods for exporting tests from TestRail
-
-- Import via CSV
-- Built-in UI tool (via API)
-- API migration script
-
-## How to Import Tests from CSV
-
-> Use CSV Import for quick imports without attachments. It’s ideal for straightforward migrations, especially when you don’t need to include test attachments or extra metadata.
-
-1. Navigate to your project in Testomat.io.
-2. Click on the **Imports** tab.
-3. Select the **Import From TestRail** button.
-
-![image Import from TestRail button](./images/import_from_testrail_button.png)
-
-4. Click on the **Import tests from CSV file** link. 
-
-![image Import from CSV file](./images/import_tests_from_CSV_link.png)
-
-5. From the dropdown menu, choose **TestRail**.
-6. Select the CSV file containing your exported TestRail tests.
-7. Click the **Create** button to complete the import.
-
-![image Import from Testrail CSV](./images/import_testrail_csv.png)
-
-## Example Files For Import 
-
-Below is a sample of the supported format:
-
-[TestRail](https://testomatio-artifacts.ams3.cdn.digitaloceanspaces.com/documentation/TestRail.csv)
-
-
-## Import TestRail Project via Build-in UI Tool (via API)
-
->If you have a small or medium-sized TestRail project (up to 1000 tests) that you'd like to import into Testomat.io, you can easily use our intuitive built-in UI tool, which imports tests via the API.
-
-1. Navigate to your project in Testomat.io.
-2. Click on the **Imports** tab.
-3. Select the **Import From TestRail** button.
-4. Enter your valid TestRail credentials in the provided fields.
-5. Click the **Import Tests** button to begin the import process.
-
-![image Import from Testrail via API](./images/import_testrail_project_via_API.png)
-
-> Make sure that you have enabled API in the administration area in TestRail under Administration > Site Settings > API.
-
-## Import TestRail Project via API Migration Script
-
->Use the API Migration Script when migrating large TestRail projects (more than 1000 tests) that include attachments or require more customization than the built-in UI tool can handle. This method is ideal for transferring extensive datasets, ensuring that all test cases, including attachments, are accurately imported into Testomat.io.
-
-1. Navigate to your project in Testomat.io.
-2. Click on the **Imports** tab.
-3. Select the **Import From TestRail** button.
-4. Click on the **Import Locally** link to access the [migration script instructions](https://github.com/testomatio/migrate-testrail).
-
-
-![image Import from Testrail via API](./images/testrail_migration_script_link.png)
-
-
-
-
-

package/skills/testeiya/testomatio-docs/docs/project/import-export/import/import-tests-from-xray.md

@@ -1,55 +0,0 @@
----
-title: Import Tests From XRay
-description: Learn how to import tests from XRay into Testomat.io using the migration script that utilizes the XRay API.
-type: article
-url: https://docs.testomat.io/project/import-export/import-tests-from-xray
-head:
-  - tag: meta
-    attrs:
-      name: keywords
-      content: Testomat.io, CSV, XRay, test import, XRay migration, manual tests, automated tests, test management
----
-
-> If you have existing tests in XRay and want to migrate to Testomat.io, you can use our migration script, which pulls test cases via the XRay API and converts them into Testomat.io’s format.
-
-## Import XRay Project via Migration Script
-
-This method is ideal if you need to migrate test cases directly from XRay, including custom fields or complex structures.
-
-### Steps:
-
-1. Open your project in Testomat.io.  
-2. Go to the **Imports** tab.  
-3. Click the **Import from CSV** button.
-
-![Import from CSV button](./images/import_fromcsv_button.png)
-
-4. From the dropdown, select **XRay**.  
-5. Follow the instructions in the [advanced XRay migration script](https://github.com/testomatio/migrate-xray) to export your tests via API and convert them into a CSV format compatible with Testomat.io.
-
-![Import from XRay Script](./images/XRay_script.png)
-
-## How to Import Tests into Testomat.io
-
-1. If you're creating a brand new project, the **Import from Spreadsheet** button will be available under the Test tab.
-
-![image Import from Spreadsheet button](./images/import_from_spreadsheet_button.png)
-
-2. If you're working in an existing project, open it in Testomat.io.
-3. Click the **Imports** tab.
-4. Click the **Import from CSV** button.
-
-![image Import from CSV button](./images/import_from_csv_button.png)
-
-5. From the dropdown menu, choose **Testomatio**.
-6. Select the file generated by the migration script.
-7. Click the **Create** button to complete the import.
-
-![image Import Testomat](./images/import_testomat.png)
-
-
-
-
-
-
-

package/skills/testeiya/testomatio-docs/docs/project/plans/index.md

@@ -1,334 +0,0 @@
----
-title: Test Plans Overview
-description: Explore how to create and manage test plans in Testomat.io. This guide covers manual, automated, and mixed test plans, detailing how to organize test cases, run tests on CI, and combine manual and automated test reports. Learn how to configure Continuous Integration and use filters for efficient test management.
-type: article
-url: https://docs.testomat.io/project/plans
-head:
-  - tag: meta
-    attrs:
-      name: keywords
-      content: test plans, test plan creation, test plan execution, manual testing, automated testing, mixed test plans, CI/CD, CLI, continuous integration, test case management, QA, Testomat.io, testing strategy, test reports
----
-
-**Test Plan** defines the scope, structure, and execution model of a run. It helps teams clearly understand which tests will be executed, how they are grouped, and how results will be reported.
-
-In Testomat.io, Test Plans allow you to organize tests, control how they are executed (manually, automatically, or both), and keep test results consistent and transparent for all stakeholders.
-
-The **Plans** page is the central place where you create, manage, and organize all test plans. From here, you can:
-
-1. **Filter by label** – Narrow down plans by labels for better organization
-2. **Search** – Quickly find plans by name
-3. **+ New plan** – Create Manual, Automated, or Mixed plans
-4. **Multiselect** – Select multiple plans to apply bulk actions
-5. **Filter by type** – Narrow down plans by types (Manual, Automated, Mixed, or Generated)
-6. **Labels** – Assign or remove labels to one or multiple plans
-7. **Link to Issue** – Link plans to issues individually or in bulk
-8. **Delete** – Remove one or multiple plans using multiselect
-
-![Overview Plans page](./images/att3_6256.png)
-
-This overview helps you quickly navigate, filter, and manage test plans before working with plan details and runs.
-
-## Types of Test Plans
-
-Testomat.io supports three main types of test plans. Each type is designed for a specific testing goal and execution model. Choosing the right plan type depends on how your tests are executed and how results should be reported.
-
-- **Manual** – for executing tests manually and reporting results from the UI
-- **Automated** – for running automated tests via CI or CLI and reporting results automatically
-- **Mixed** – for combining manual and automated tests in a single plan and report
-
-Below, we’ll walk through each plan type and explain how and when to use it.
-
-### Manual Plans
-
-**Manual Plans** are designed for tests that are executed manually by testers.
-
-They are typically used when:
-
-- Tests require human validation or judgment
-- Exploratory or usability testing is performed
-- Manual regression or acceptance testing is needed
-
-#### Add Automated Tests as Manual
-
-Manual Plans include an optional toggle: **Run Automated as Manual**.
-
-**When enabled:**
-
-- Automated tests can be added to a Manual Plan **using the same selection logic as manual tests** (test tree, folders/suites, or filters)
-- These tests are executed manually, and test run statuses (**Passed / Failed / Skipped**) are assigned manually during the run
-
-**When disabled:**
-
-- Automated tests are not selectable
-
-This toggle is the **only exception** to the strict plan-to-test-type mapping.
-
-![Run Automated as Manual toggle](./images/gif4_5256.gif)
-
-### Automated Plans
-
-**Automated Plans** are designed for running automated tests and sending their results to Testomat.io.
-
-They are typically used when you:
-
-- Want to run a fixed or predefined set of automated tests
-- Execute tests automatically via a **Continuous Integration (CI) service** or **from CLI**
-- Need tests to run regularly (e.g., nightly, on every commit, or before a release)
-- Want test results reported automatically, without manual intervention
-
-With Automated Plans:
-
-- Only **automated tests** can be added to the plan
-- Test execution is triggered via a CI pipeline or CLI command
-- Execution results are sent automatically to Testomat.io
-
-To use an Automated Plan:
-
-- Tests must have **IDs**
-- IDs can be generated using the `--update-ids` option during test import
-- Each plan has a **Plan ID**, which can be used to run this specific collection of tests
-
-For example,
-
-`TESTOMATIO={API_KEY} npx @testomatio/reporter run 'actual run command' --filter 'testomatio:plan={Plan_ID}'`
-
-- `{API_KEY}` – your Testomat.io Reporting API key
-- `{Plan_ID}` – ID of the plan you want to run
-- `'actual run command'` – your test framework command (e.g., `npx codeceptjs`)
-
-#### How to Launch an Automated Run from a Plan
-
-Once your Automated Plan is created, you can start an automated run from the **'Plans'** page.
-
-If you want to run tests automatically on a CI service:
-
-1. Go to the **'Plans'** page
-2. Open your Automated Plan
-3. Click the **'Launch'** button → you will be redirected to the **Runs** page
-4. A new run **'Run automated tests in CI'** will be triggered in the sidebar
-
-![Launch from Automated Plan from Plan](./images/gif5_5256.gif)
-
-:::note
-
-The **'Launch'** button on the Plans page will **not be active** if Continuous Integration is not configured. Make sure CI is set up first. Learn more on the [Continuous Integration page](https://docs.testomat.io/usage/continuous-integration/).
-
-:::
-
-### Mixed Plans
-
-**Mixed Plans** combine both manual and automated tests in a single plan.
-
-They are typically used when you:
-
-- Include automated tests that run via CI or via CLI
-- Have other tests that still require manual execution
-- Want a **single report** for the entire testing scope
-
-With Mixed Plans:
-
-- Both **manual and automated tests** can be added in the same plan
-- Automated tests can be executed via CI or triggered via CLI
-- Manual tests are executed manually
-- Results from both test types are combined into a single run report
-
-This makes Mixed Plans suitable for flexible or transitional testing strategies.
-
-#### How to Launch a Mixed Run from a Plan
-
-Once your Mixed Plan is created, you can start a run directly from the **'Plans'** page. When triggered:
-
-1. Go to the **'Plans'** page
-2. Open your Mixed Plan
-3. Click the **'Launch'** button → you will be redirected to the **Runs** page
-4. A new run **'New Mixed Run'** will be triggered in the sidebar
-5. You can choose whether to **enable or disable CI build** for this run
-
-:::note
-
-The **'Launch'** button on the Plans page will **not be active** if Continuous Integration is not configured. Make sure CI is set up first. Learn more on the [Continuous Integration page](https://docs.testomat.io/usage/continuous-integration/).
-
-:::
-
-![Launch from Mixed Plan from Plan](./images/gif6_5256.gif)
-
-## How to Create a New Plan
-
-This section explains how to create a Test Plan in Testomat.io and configure its basic settings. You can create a plan from different parts of the application, depending on your workflow.
-
-### Ways to Create a Test Plan
-
-There are two ways to create a Test Plan in Testomat.io:
-
-1. **From the Plans page**  
-   This is the standard way to create and manage plans. It is suitable for all plan types and is described in detail below.
-
-2. **From the Runs page**  
-   You can also create a plan directly while launching a run.  
-   In this case:
-   - The plan creation settings are **identical** to creating a plan from the Plans page
-   - The newly created plan is **automatically pre-selected** for the current run
-   - This is the **only supported way** to create a plan during **Manual or Mixed run**
-
-![Create Plan from Runs page](./images/gif1_7641.gif)
-
-Regardless of where you start — from the **Plans** page or directly from the **Runs** page — the plan creation and configuration flow remains the same.
-
-### Common Flow for All Plan Types (Including All Tests)
-
-Before selecting test cases for any plan, the creation process follows the same initial steps for all plan types:
-
-1. Go to the **'Plans'** page
-2. Click the **'+ New plan'** dropdown
-3. Choose one of the following options from the dropdown:
-
-- **Manual**
-- **Automated**
-- **Mixed**
-
-![Type plan](./images/att1_6256.png)
-
-4. Enter a **Title** (required)
-5. Add a **Description** (optional)
-
-The description helps clarify the plan’s purpose, scope, and objectives. It can also be viewed later in the plan details or when inspecting Runs.
-
-6. Enable the **'Run Automated as Manual'** toggle (optional)
-7. Click the **'+ All tests'** button, then confirm
-
-:::note
-
-Clicking 'All tests' adds all tests to the collection and clears any other filters.
-
-:::
-
-8. Click the **'Save'** button
-
-![save New plan](./images/att2_6256.png)
-
-## How to Work with Test Collections
-
-| Feature / Action              | Description                                 | Notes / Logic                                                                                                                                                                                                                   |
-| ----------------------------- | ------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| **Enable/Disable collection** | Toggle to show/hide tests in the collection | No restrictions                                                                                                                                                                                                                 |
-| **Add filter**                | Adds filters within a collection            | **AND** logic is applied between filters inside a single collection. <br> Cannot add any filters in a collection where **Tests** are already selected <br> To use filters, apply different filters or create another collection |
-| **Delete filters**            | Removes filters from the collection         | If the **last remaining filter** is removed while the collection toggle is enabled, <br> **all tests are included in the collection**.<br> Removing one of multiple filters works as expected                                   |
-| **All tests**                 | Includes all tests in the collection        | All tests are included in the collection; removes any active filters                                                                                                                                                            |
-| **Add collection**            | Adds a new collection with its own filters  | Allows combining different sets of filters across collections; **OR** logic applies between collections                                                                                                                         |
-| **Delete collection**         | Deletes the collection                      | Removes the collection along with all its filters. The first (default) collection cannot be deleted                                                                                                                             |
-
-### Filter-based selection
-
-Filters allow you to dynamically **include or exclude tests in a plan** based on metadata. Adding or removing tests via filters directly affects the plan, not just the collection.
-
-**Include Tests by Filters**
-
-- Adds tests to the collection **and the plan** that match any of the selected filters
-- Supported filters for Include:
-  - Suites & folders
-  - Tags
-  - Priority
-  - Assignees
-  - Labels
-  - Custom labels
-  - Query
-- Logic: **AND** within a collection, **OR** between collections
-- All tests selected by the filters are displayed in the **Matched tests** tab
-
-**Exclude Tests by Filters**
-
-- Removes tests from the collection **and the plan** that match selected filters
-- Supported filters for Exclude:
-  - Suites & folders
-  - Query
-- Works in combination with **Include Tests by Filters**
-- Logic: **AND** within a collection
-
-:::note
-
-**Tests** is a chosen mode, not a filter. It cannot be combined with **supported filters** in the same collection.
-
-:::
-
-![Collections & filters](./images/att8_5256.png)
-
-## Managing Plans
-
-Efficient management of test plans is key to keeping your testing organized and transparent. In Testomat.io, you can group and organize plans using **Labels**, making it easy to filter, find, and manage multiple plans at once.
-
-### Benefits of Using Labels for Plans
-
-By assigning labels to your plans, you can:
-
-- Organize plans by category, team, or purpose – e.g., 'Regression', 'Smoke', 'QA'
-- Filter plans quickly – instantly narrow down the list of plans by selecting specific labels
-- Maintain consistency across projects – ensure all plans follow a structured labeling system
-- Apply bulk actions easily – assign or remove labels from multiple plans at once using multi-selection
-
-Labels provide a flexible way to group and manage plans according to your workflow.
-
-### How to Assign Labels to Plans
-
-1. Go to the **Plans** page
-2. Open a plan or select multiple plans using multi-selection mode
-3. Click the **Labels**
-4. Select the labels you want to assign
-5. Click **Add** button
-
-![Assign Labels to Plans](./images/gif1_518.gif)
-
-:::note
-
-You can create new labels or manage existing ones in [Settings → Labels & Fields](https://docs.testomat.io/advanced/tags-labels/labels-and-custom-fields/#how-to-add-labels--custom-fields). Make sure to set the Scope to Plans so labels are applied correctly.
-
-:::
-
-### Filtering Plans by Labels
-
-Testomat.io offers two convenient ways to filter your plans using **labels**:
-
-1. Using the **Filter Bar**:
-
-- Click the **filter** icon next to the search bar
-- Apply one or multiple labels
-- This method allows multi-label filtering, showing only plans that match all selected labels
-
-![Filter Bar](./images/att2_7821.png)
-
-2. Using the **Quick Filter Panel**
-
-- All labels currently in use are displayed
-- Select a single label from this list to quickly filter plans
-- This method is ideal for fast, one-label filtering
-
-![Quick Filter Panel](./images/att3_7821.png)
-
-:::note
-
-Use the **Filter Bar** for more advanced multi-label filtering, and the **Quick Filter Panel** for fast access to frequently used labels.
-
-:::
-
-### Tree View for Plans
-
-Plans can be displayed in a hierarchical tree structure that mirrors the test organization. To switch to tree view, open a plan and click the tree view icon in the top right corner of the test list.
-
-You can:
-
-* Expand folders
-* Collapse sections
-* Navigate large test sets faster
-* Focus on specific areas of a project
-
-:::note
-
-This is particularly useful for large projects containing hundreds or thousands of tests.
-
-:::
-
-### Example Use Cases
-
-- QA lead wants to see only Regression plans – assign a 'Regression' label to all relevant plans and filter by it
-- A team working on Frontend tests can quickly access all their plans by using the 'Frontend' label
-- During release planning, project managers can filter plans by priority or milestone labels to focus on relevant test coverage

package/skills/testeiya/testomatio-docs/docs/project/pulse/index.md

@@ -1,104 +0,0 @@
----
-title: Pulse
-description: Pulse in Testomat.io tracks all changes to tests, test suites, test plans, and test runs, providing transparency and control over project modifications. It tracks creation details, updates, and offers a history of changes. With its recovery feature, deleted items can be easily restored. The Bulk Restore option allows users to recover multiple deleted tests, suites, or plans simultaneously.
-type: article
-url: https://docs.testomat.io/project/pulse
-head:
-  - tag: meta
-    attrs:
-      name: keywords
-      content: Pulse, Testomat.io, test tracking, test suite monitoring, test plan tracking, test run tracking, version history, change tracking, test recovery, Bulk Restore, test management, suite restoration, plan monitoring
----
-
-**Pulse** is a powerful feature in [Testomat.io](https://app.testomat.io) that brings full visibility, traceability, and control to your QA workflow. It tracks every change made within your projects — including **tests, suites, plans, and runs** — giving you a clear picture of how your testing assets evolve over time.
-
-Pulse provides instant visibility into team activity and testing progress. This helps **QA Leads** and **Project Managers** stay informed without manually requesting status updates.
-
-## What is Pulse
-
-Pulse acts as your **project’s activity log** and **version history**, automatically recording all modifications across **tests, suites, plans, and runs**. It’s designed to ensure transparency, accountability, and easy recovery, so your team can work confidently knowing that every action is tracked and reversible.
-
-Every action related to these entities is recorded, providing full visibility into how your testing assets evolve over time.
-
-With Pulse, you can:
-
-- See **who made a change**, **what was changed**, and **when** it happened.
-- Review the history of edits, additions, or deletions for any test, suite, plan, or run.
-- **Restore deleted items** or roll back to previous versions with a single click.
-
-For **QA Engineers**, this means full control over versioned work. For **managers**, it offers a reliable audit trail and a clear view of project momentum over time.
-
-This ensures you’ll never lose important test data or struggle to understand how your project has evolved — Pulse keeps your QA process transparent and your history intact.
-
-## How Pulse Works
-
-You can access Pulse directly from the **Pulse** tab in your Testomat.io project. There, you’ll find a chronological list of all activities recorded over the last **90 days**. Each entry contains detailed information about the change, including timestamps, item type, and the responsible team member.
-
-Pulse allows you to track every action across your QA workflow, giving you a clear picture of how tests, suites, plans, and runs evolve over time.
-
-### Activity Types
-
-Activity tracking applies to all main QA entities in your project. For each entity, Pulse records **who performed the action** and **when it happened**:
-
-- **Suite** — tracking full **CRUD** activity for suites, with versioned changes, before/after diffs, including title and description updates, attachment changes, bulk edits within a suite, and suite restore.
-- **Test** — tracking full **CRUD** activity for tests, with versioned changes, before/after diffs, including title and description updates, attachment and priority changes, test state updates (manual, automated), and test restore.
-- **Run** — tracking activity for runs, with versioned changes, before/after diffs, including manual or automatic purge, run restore, and permanent removal.
-- **Plan** — tracking full **CRUD** activity for plans (manual, automated, mixed), with versioned changes, before/after diffs, including filter updates, included/excluded suites and tests, query changes, manual/automated state changes, and plan restore.
-
-**QA Leads** can use this overview to identify active contributors, while **PMs** can quickly assess whether recent changes align with sprint goals or release timelines.
-
-:::note
-
-Every recorded event provides a clear snapshot of the change and supports **rollback functionality**, so you can revert to a previous version or recover deleted items when needed.
-
-:::
-
-## Filtering and Navigation
-
-Pulse includes powerful filters to help you quickly find the information you need. You can narrow down activities based on:
-
-- **Item Type** – filter logs by **Suite, Test, Run, or Plan**.
-- **Date Range** – filter changes within a specific time window.
-- **Changed By** – see actions performed by a particular user.
-
-![Testomat.io - Pulse Activity Tabs](./images/Pulse_filters.gif)
-
-Each filter can be applied individually or in combination, enabling precise tracking of team activity and project evolution.
-
-![Filters](./images/att1_7104.png)
-
-This makes it easy to monitor specific team members’ contributions or isolate changes from a given testing phase.
-
-In addition to filters, Pulse provides activity tabs that allow you to switch between:
-
-- **Created** — new tests, suites, or plans added to the project.
-- **Changed** — updates to existing items.
-- **Deleted** — items removed from the project, including tests, suites, plans, or runs.
-
-These tabs instantly filter the activity feed by action type, making navigation faster and more intuitive.
-
-![Testomat.io - Pulse Activity Tabs](./images/Pulse_activity_tabs.gif)
-
-## Diff
-
-Pulse provides a Diff view for items with the **Changed** action. It allows you to compare different versions of the same item and clearly see what was modified between them.
-
-![Diff](./images/att2_7104.png)
-
-## Bulk Restore
-
-Bulk Restore is a great extension for Pulse. It is designed to save you time and effort by allowing you to restore multiple deleted tests and suites at once.
-
-With Bulk Restore, you can:
-
-- **Batch Restore:** Quickly and efficiently recover multiple deleted tests and suites at once, eliminating the need to restore each item individually.
-
-- **Multi-Selection Mode:** Easily activate multi-select mode, choose the tests and suites you wish to restore, and bring them all back with a single action.
-
-![Testomat.io - Bulk Restore](./images/New_85QaXaUI_2024-07-30.gif)
-
-:::note
-
-**Runs activity in Pulse** tracks all purge actions for transparency. Permanently deleted Runs cannot be restored. Full details: [Runs Activity Tracked in Pulse](https://docs.testomat.io/project/runs/managing-runs/#runs-activity-tracked-in-pulse).
-
-:::