testeiya 0.2.1 → 0.3.9

package/skills/testeiya/testomatio-docs/docs/advanced/jira-plugin/work-in-jira.md

@@ -1,267 +0,0 @@
----
-title: Work with Tests in Jira
-description: Learn how to integrate Testomat.io with Jira using the Jira plugin. This guide covers connecting Testomat.io projects to Jira, linking/unlinking tests, suites, and test plans to Jira issues, and running manual or automated tests directly from Jira. Manage BDD feature files, attach test reports, and utilize the traceability matrix for comprehensive test coverage in sprints.
-type: article
-url: https://docs.testomat.io/advanced/jira-plugin/work-in-jira
-head:
-  - tag: meta
-    attrs:
-      name: og:image
-      content: https://docs.testomat.io/_astro/125162422-5f93e400-e190-11eb-9959-140eca400cb9.BKJldTge_ZqM9vX.webp
-  - tag: meta
-    attrs:
-      name: keywords
-      content: Jira plugin, Testomat.io, test management, test coverage, BDD, feature files, automated tests, manual tests, Jira integration, traceability matrix, test reporting
----
-
-This guide explains how to create, edit, link, and manage **Suites**, **Tests**, and **Plans** in Jira using the **Testomat.io** plugin.
-
-## How to Work with Suites
-
-Create and manage Suites in Jira — organize related tests and link them to issues using the **Testomat.io** plugin.
-
-### How to Create a Suite
-
-1. Navigate to the **Suites** tab
-2. Click the **menu button (⋯)** and select **New Suite**
-
-![New Suite button](./images/att14_401.png)
-
-3. Enter the suite’s name and description below (optional)
-4. Click **Create** button
-
-![Create button](./images/att15_401.png)
-
-5. Select a parent suite from the dropdown or Root destination
-6. Click **Save** button
-
-![Save new suite](./images/att16_401.png)
-
-### How to Edit a Suite
-
-1. Navigate to the **Suites** tab
-2. Click the **pen icon** near the suite you want to edit
-
-![Edit icon for suite](./images/att23_401.png)
-
-3. Edit the suite (Suite title, description)
-4. Click **Update** button
-
-![Update button](./images/att24_401.png)
-
-### How to Link and Unlink a Suite
-
-**To link a suite to a Jira issue:**
-
-1. Navigate to the **Suites** tab
-2. Click the **menu button (⋯)** and select **Link Suite**
-
-![Link Suite](./images/att20_401.png)
-
-3. Select a parent suite from the dropdown
-4. Click **Save** button
-
-![Save linked suite](./images/att21_401.png)
-
-**To unlink a suite:**
-
-1. Navigate to the **Suites** tab
-2. Сlick the **trash can icon** next to the linked suite
-3. Once the modal window opens, confirm by clicking **Unlink** button
-
-![Unlink suite](./images/att25_401.png)
-
-### AI Actions for Suites
-
-Use AI to generate new test cases, or summarize the suite. Helps quickly expand test coverage, identify gaps, and create high-level insights about the suite without manual analysis.
-
-- **Suggest Tests** – Generate new test cases based on the patterns and structure of existing tests in this suite.
-- **Summarize** – Generate a concise summary of the test suite, highlighting key features, test coverage, and any notable findings.
-
-How to run AI Actions on a suite:
-
-1. Navigate to the **Suites** tab in the Jira Plugin
-2. Click the **AI Actions** button next to the specific suite
-3. Select and run the desired AI prompt
-
-![AI Actions for Suites](./images/att46_401.png)
-
-## How to Work with Tests
-
-Manage your tests directly in Jira — create, edit, and link them to issues or plans within the **Testomat.io** plugin.
-
-### How to Create a Test
-
-1. Navigate to the **Tests** tab
-2. Click the **menu button (⋯)** and select **New Test**
-
-![New Test button](./images/att17_401.png)
-
-3. Enter the test’s name and optional description
-4. Click **Create** button
-
-![Create button](./images/att18_401.png)
-
-5. Select a suite from the dropdown
-6. Click **Save** button
-
-![Save new test](./images/att19_401.png)
-
-### How to Bulk Create Tests
-
-Quickly create multiple tests at once directly from Jira.
-
-1. Navigate to the Tests tab
-2. Click the **menu button (⋯)** and select **Bulk Create**
-
-![Bulk Create](./images/att31_401.png)
-
-3. Select the existing suite from the dropdown list
-4. In the Add new tests field, enter test titles — each line corresponds to the title of a new test
-5. Click the **Create** button to add all listed tests to the selected suite
-
-![create multiple tests](./images/att30_401.png)
-
-### How to Edit a Test
-
-1. Navigate to the **Tests** tab
-2. Click the **pen icon** near the test you want to edit
-
-![pen icon](images/att26_401.png)
-
-3. Edit the test (Test title, description)
-4. Click **Save** button
-
-![Update test](./images/att27_401.png)
-
-### How to Link and Unlink a Test
-
-#### How to Link a Test
-
-1. Navigate to the **Tests** tab
-2. Click the **🔗 Test** button with the link icon
-
-![Test button](./images/att29_401.png)
-
-3. In the opened window, use filters to find the needed tests:
-
-- Select a suite in the Search a suite dropdown
-- Select a plan in the Search a plan dropdown
-- Optionally, enter a tag in the Type @tag and press 'Enter' field
-- Combine filters using AND or OR to refine search results
-
-4. From the list of found tests, click the **Link** button next to a test to connect it to the Jira issue
-
-- You can also click **Link All** to link all displayed tests
-
-![Link All tests](./images/att32_401.png)
-
-#### How to Unlink a Test
-
-You can unlink tests from a Jira issue in several ways:
-
-- via the **menu button (⋯)**
-- through the **🔗Test** button
-- using **Bulk Unlink** (recommended for mass actions)
-
-Option 1 — via the **menu button (⋯)**
-
-1. Navigate to the **Tests** tab
-2. Click the **menu button (⋯)** and select **Unlink Test**
-
-![Unlink Test button](./images/att33_401.png)
-
-3. Select tests to unlink:
-
-- By default, all tests are selected for unlinking
-- If you don’t want to unlink all tests — uncheck the box next to the specific tests
-- To unlink only selected ones, uncheck **All tests** first, then select individual tests you want to unlink
-
-4. Click the **Unlink** button to confirm
-
-![Unlink tests](./images/att34_401.png)
-
-Option 2 — through **🔗Test** button
-
-1. Navigate to the **Tests** tab
-2. Click the **🔗 Test** button with the link icon
-
-![Test button](./images/att29_401.png)
-
-3. In the opened window, find linked tests — Click **Unlink** next to the test you want to remove
-4. Or click **Unlink All** to detach all linked tests at once
-
-![Alt text](images/att35_401.png)
-
-Option 3: **Bulk Unlink** – via the **'multi-select'** button
-
-1. Navigate to the **Tests** tab
-2. Click the **'multi-select'** button at the bottom right corner
-3. Use the checkboxes to select individual tests:
-   - Click **Select All** to select all tests
-   - Click **Select None** to clear the selection
-4. Click the **Trash** icon to unlink the selected tests
-5. In the confirmation pop-up (**'Are you sure that you want to unlink # tests?'**), click **Unlink** to confirm
-
-![Confirmation pop-up](./images/att3_462.png)
-
-### AI Actions for Tests
-
-Automatically generate or improve individual test descriptions. AI Actions save time on writing or refining test documentation, ensure clarity and consistency across the project, and improve overall quality.
-
-- **Suggest Description** – Generate a clear and concise description for a test based on its title and a list of descriptions from similar tests.
-- **Improve Description** – Enhances formatting and readability using Markdown without changing the content, ensuring consistency and easy scanning.
-- **Suggest Better Description** – Rewords and reorganizes the existing description to make it clearer, more informative, and concise while preserving the original intent.
-
-How to run AI Actions on a test:
-
-1. Navigate to the **Tests** tab in the Jira Plugin
-2. Click the **AI Actions** button next to the specific test
-3. Select and run the desired AI prompt
-
-![AI Actions for Tests](./images/att47_401.png)
-
-:::note
-
-- For Suggest Description, the **Run** button is only active if the Description field is **empty**.
-- For Improve Description and Suggest Better Description, the **Run** button is only active if the Description field is **not empty**.
-
-:::
-
-## How to Work with Test Plans
-
-Link and execute Test Plans directly from Jira to track and manage testing progress.
-
-### How to Link a Test Plan
-
-1. Navigate to the **Plans** tab
-2. Click the **🔗 Plan** button or **menu button (⋯)** and select **Link Plan**
-3. Click **Link** button
-
-![Link a Plan](./images/att36_401.png)
-
-### How to Unlink from a Test Plan
-
-1. Navigate to the **Plans** tab
-2. Click the **🔗 Plan** button, or
-3. Click the **trash can icon** next to the linked plan
-4. Click the **Unlink** button to confirm
-
-![Unlink a plan](./images/att37_401.png)
-
-## How to Work with Feature Files (BDD)
-
-Edit and update BDD Feature Files from Jira and sync changes with your Testomat.io project.
-
-### How to Edit a Feature File
-
-1. Navigate to the **Test Coverage** tab
-2. Click the **menu button (⋯)** and select **Edit Feature**
-
-![Alt text](images/att38_401.png)
-
-3. Select the suite you want to edit in the Feature File
-4. Edit the **Feature File**
-5. Click the **Update** button
-
-![Update Feature File](./images/att39_401.png)

package/skills/testeiya/testomatio-docs/docs/advanced/living-doc/index.md

@@ -1,138 +0,0 @@
----
-title: Living Documentation
-description: Learn how to enable and embed Living Documentation in Testomat.io, a dynamic and real-time document generation tool for test projects. This guide covers embedding specific test suites, tests, or tests tagged with Jira IDs into websites or Confluence using iframes, offering enhanced visibility and collaboration for testing efforts.
-type: article
-url: https://docs.testomat.io/advanced/living-doc
-head:
-  - tag: meta
-    attrs:
-      name: og:image
-      content: https://docs.testomat.io/_astro/126028734-59df8280-2224-405f-960c-6a5de4a4b7d9.BNrl6wUZ_ZmAFLw.webp
-      
-  - tag: meta
-    attrs:
-      name: keywords
-      content: Living Documentation, Testomat.io, dynamic documentation, test management, Jira integration, test suites, embedding tests, iframe, real-time documentation, Confluence integration
----
-
-Living Documentation is a dynamic, always-up-to-date view of your tests, test suites and system behavior. Instead of relying on static documents that quickly become outdated, teams can use Living Documentation to share **test coverage, scenario details, and real-time results** directly within their development tools. Living Documentation provides a single source of truth that evolves with your code and test cases. In Testomat.io, this means your automated tests don’t just verify functionality — they also become readable, shareable, and traceable documentation that supports collaboration and decision-making across the team.
-
-- Non-technical stakeholders (e.g., Product Managers, Compliance Teams) can view test coverage and feature behavior without diving into code.
-Makes it easy to review acceptance criteria or BDD scenarios.
-
-- You can embed tests tied to specific Jira tickets directly in documentation or dashboards.
-Easily include documentation in Confluence pages, sprint reports, or product specs.
-
-- You can trace a test to a suite, feature, user story, or Jira ID.
-
-- In Behavior-Driven Development (BDD), living documentation becomes the specification.
-
-- Make tests or suites publicly viewable, or embed internally for team access.
-Useful for partners, clients, or external QA vendors.
-
-
-
-## How To Enable Living Documentation
-
-Living Documentation can be enabled in Project Settings:
-
-1. Go to Settings
-2. Click on the Project tab
-3. Enable **Share Living Docs** toggle
-4. See the confirmation and generated link for Living Documentation
-
-![Enabling Living Docs](./images/enabling_living_docs.png)
-
-## How To Embed Living Documentation
-
-Living documentation can be embedded into your website, you have a possibility to:
-
-- Embed specific suite
-- Embed specific test
-- Embed tests with a specific tag or Jira id
-
-## Suite
-
-To embed a suite you have to:
-1. Select a suite on a living documentation page.
-2. Open a drop-down menu under three dots (...) 
-3. Select **Copy embed URL** option.
-4. See the confirmation message that embed URL has been copied to your clipboard.
-
-![Embed a suite](./images/embed_suite.png)
-
-
-## Test
-
-To embed a test you have to :
-
-1. Select a specific test on a living documentation page.
-2. Open a drop-down menu under three dots (...) 
-3. Select **Copy embed URL** option.
-4. See the confirmation message that embed URL has been copied to your clipboard.
-
-![Embed a test](./images/embed_a_test.png)
-
-
-## Tests by Tag or Jira ID
-
-To embed tests by `@smoke` tag you need to follow this template (don't forget to replace {project_slug} with the real value):
-
-```
-<iframe src="https://app.testomat.io/docs/projects/{project_slug}/tests/embed?tag=@smoke"></iframe>
-```
-
-To embed test with Jira id you need to follow this template (don't forget to replace {project_slug} and {jira_id} with the real values):
-
-```
-<iframe src="https://app.testomat.io/docs/projects/{project_slug}/tests/embed?jira_id={jira_id}"></iframe>
-```
-
-## Tests parameters
-
-You can provide extra parameters in the query string:
-
-1. frame_params[expand_all] - expand all tests by default
-2. frame_params[hide_code] - hide code in tests
-3. frame_params[hide_description] - hide description in tests
-4. frame_params[hide_attachments] - hide attachments in tests
-
-Example
-
-```
-<iframe src="https://app.testomat.io/docs/projects/{project_slug}/tests/embed?tag=@smoke&frame_params[expand_all]=1&frame_params[hide_code]=1"></iframe>
-```
-
-## Embed Link For Confluence 
-
-With Testomat.io Living documentation, you can enrich your Confluence by adding tests or suites.
-This can be done within a Confluence page:
-
-1. Open your Confluence page editor - click Insert
-2. Type 'iframe' in search field
-3. Select Iframe plugin
-
-![Iframe plugin in Confluence](./images/confluence_iframe.png)
-
-4. Enter the embed URL you generated in the Living documentation
-5. Fill in the fields of your choice
-
-For example: display: block; border: none; height: 100vh; width: 100%; height:100%;
-
-![Embed URL in Confluence](./images/confluence_embed_URLD.png)
-
-6. Click Publish.
-
-
-## Search within Living Documentation
-
-You can search for specific tests within Living Documentation. The search functionality works the same way as it does in the Tests tab in Testomatio. You can search using two parameters:
-
-1. Search by tags – Type a tag into the search field. A list of tests that match the tag will be displayed under the search field.
-
-2. Search by keywords – Type a keyword into the search field. A list of tests that match the keyword will be displayed under the search field.
-
-![Search Within Living Documentation](./images/Living_Doc_Search.png)
-
-
-

package/skills/testeiya/testomatio-docs/docs/advanced/milestones/index.md

@@ -1,220 +0,0 @@
----
-title: Milestones
-description: Discover Testomat.io's Milestones feature to support structured test management across your development cycles. Learn how to create, activate, and assign milestones to track testing progress and generate analytics reports.
-type: article
-url: https://docs.testomat.io/advanced/milestones
-head:
-  - tag: meta
-    attrs:
-      name: keywords
-      content: Testomat.io, Milestones, test management, development cycles, testing scope, create milestone, assign milestone, milestone activation, state management, project scoping, milestone types, sprint tracking, release tracking, audit logs, milestone analytics, progress reports
----
-
-Testomat.io introduces **Milestones** to support structured test management across your development cycles.
-
-In software development, a **milestone** represents a significant checkpoint or phase in a project (e.g., release, sprint, or major delivery). It is used to group work, track progress, and evaluate results within a defined scope and timeline.
-
-**With Milestones in Testomat.io, you can:**
-
-- Create milestones to define testing scope for a specific phase.
-- Assign tests and test runs to a milestone.
-- Execute tests within the context of a milestone.
-- Generate reports based on milestone results.
-
-This enables end-to-end test management aligned with project phases, providing clear visibility into progress and outcomes for each milestone.
-
-## How to Create a Milestone
-
-**Milestone** lives at the **company-level** but can be scoped down to specific projects. It's a tracking mechanism (like a Sprint, Release, or Version) that can be linked to various items in the system (Tests, Suites, Plans, Runs, Rungroups, Requirements). Milestones help organize and track work across related items with state management, automatic propagation, and project scoping.
-
-**To create Milestone:**
-
-1. Navigate to **'Milestones'** tab from the main workspace dashboard.
-2. Click **'Create Milestone'** button.
-
-![Testomat.io - Create Milestone](./images/create_milestone_1.png)
-
-3. **Title:** Enter a name for your milestone (Required).
-4. **Type:** Enter a name of category (e.g., Sprint, Release, Iteration, Phase). Milestones are grouped by type. You can create multiple types. If left blank, the system defaults to the **'Milestone'** type.
-5. Fill in optional fields as needed:
-- **Start date & Release date:** Your start date must occur before or on the release date.
-- **Description & goals:** Detail what this milestone aims to achieve.
-- **External URL:** Link directly to your matching sprint in Jira, GitHub, or internal tracking documentation.
-- **Projects:** Select the specific projects that can access this milestone. By default, it is shared with all projects within the company.
-6. **Show milestone in lists:** (Enabled by default). When enabled, this milestone appears in the tests, suites, runs, and plans lists. Turn this off to hide deprecated, archived, or legacy milestones from daily dropdown selection menus while safely preserving historical links attached to old test runs or plans.
-7. Click **'Create'** button.
-
-![Testomat.io - Create Milestone](./images/create_milestone_2.png)
-
-After milestone is created, it automatically appears in the list on **'Milestones'** page and can be assigned to test, suites, plans and runs. Milestone can be activated at any time.
-
-:::note
-
-Milestones are automatically grouped by type name in a case-insensitive manner. For example, entering `"Sprint"` or `"sprint"` maps them to the exact same milestone type category. New milestones automatically inherit project scope settings from existing sibling milestones of the same type to keep your environment synchronized.
-
-:::
-
-## How to Edit & Delete Milestone
-
-You can modify or remove milestones at any point using two different ways: from main **'Milestones'** page and from the **'Milestone details'** page.
-
-**Edit a milestone from the main 'Milestones' page:**
-
-1. Click on three dot to open the extra menu for selected milestone.
-2. Click **'Edit'** button.
-
-![Testomat.io - Edit Milestone](./images/edit_milestone_1.png)
-
-3. Apply your updates in the **'Edit Milestone'** modal and click **'Save'**.
-
-![Testomat.io - Edit Milestone](./images/edit_milestone_2.png)
-
-**Edit a milestone from the 'Milestone details' page:**
-
-1. Click on milestone name.
-
-![Testomat.io - Edit Milestone](./images/edit_milestone_1a.png)
-
-2. Click **'Edit'** button.
-
-![Testomat.io - Edit Milestone](./images/edit_milestone_2a.png)
-
-3. Apply your updates in the **'Edit Milestone'** modal and click **'Save'**.
-
-![Testomat.io - Edit Milestone](./images/edit_milestone_3a.png)
-
-**Delete a milestone from the main 'Milestones' page:**
-
-1. Click on three dot to open the extra menu for selected milestone.
-2. Click **'Delete'** button.
-
-![Testomat.io - Edit Milestone](./images/delete_milestone_1.png)
-
-3. Click **'Delete milestone'** button to confirm your action.
-
-![Testomat.io - Edit Milestone](./images/delete_milestone_2.png)
-
-Milestone as well can be deleted from the **'Milestone details'** page:
-
-![Testomat.io - Edit Milestone](./images/delete_milestone_1a.png)
-
-:::note
-
-Deleting a milestone removes its association and unlinks it from all projects, tests, and runs. Your historical test execution results, runs, and core project data remain completely untouched.
-
-:::
-
-## How To Activate a Milestone
-
-To avoid confusion about what your team is currently working on, **only one milestone of the same type can be active at a time.**
-
-**To activate milestone:**
-
-1. Click **'Activate'** button.
-
-![Testomat.io - Activate Milestone](./images/activate_milestone_1.png)
-
-2. Confirm action on **'Activate Milestone'** modal.
-
-![Testomat.io - Activate Milestone](./images/activate_milestone_2.png)
-
-When you activate a milestone, Testomat.io automatically shifts any previously active milestone of that same type into a **Closed** state and timestamps the exact moment of closure (`closed_at`).
-
-![Testomat.io - Activate Milestone](./images/activate_milestone_3.png)
-
-### Expired Milestone Warnings
-
-If a milestone reaches its target **Release Date** but has not been manually marked as **Closed**, the system keeps it open but automatically flags it as **Expired**.
-
-This automatic status change provides a clear visual indicator on your team dashboards, helping you instantly spot slipping deadlines, overdue deliverables, or uncompleted tasks that require immediate attention.
-
-![Testomat.io - Expired Milestone](./images/expired_milestone.png)
-
-## How to Assign Milestones
-
-You can associate milestones with six distinct structural components: **Test, Suite, Plan, Run, Rungroup, Requirement**.
-
-**Core Rules of Milestone Linking:**
-
-1. **Smart Link Switching**
-
-An item can only belong to one milestone per type at a time. If a test case is currently linked to `Sprint 1` and you assign it to `Sprint 2`, the system automatically replaces it. Don't worry — milestones of other types (for ex. `Release v1.0`) will stay perfectly intact.
-
-2. **Automatic Downward Sharing (Cascading)**
-
-You don't need to manually assign a milestone to hundreds of individual test cases. When you link a milestone to a parent container, the system automatically shares it downwards to all nested elements in the background:
-
-- **Suites:** Assigning a milestone to a Suite cascades it to **all tests inside that suite**.
-
-- **RunGroups:** Assigning a milestone to a RunGroup cascades it to all test runs inside that group automatically.
-
-**Steps to Assign a Milestone:**
-
-1. Go to **'Tests'** page.
-2. Select the Suite or individual item you want to map.
-3. Click the **'Set milestone'** label in the details panel.
-4. Select one or more milestones across your available types.
-5. Click **'Save'** button.
-
-![Testomat.io - Assign Milestone](./images/assign_milestone_1.gif)
-
-Same logic applies to any other entity a milestone can be assigned to.
-
-## Filter by Milestone
-
-Testomat.io allows you to filter your tests, suites, runs, and plans by Milestone using either the regular interface filter or the advanced Testomatio Query Language (TQL) filter.
-
-### Using the Interface Filter
-
-1. Open the Tests, Runs, or Plans tab.
-2. Click on the **Filter dropdown** at the top of the list.
-3. Select your Milestone Type (e.g., Sprint or Release) and choose the specific milestone from the list.
-4. Click **'Apply'** button to apply selected filter.
-
-The workspace will dynamically update to show only the items linked to that milestone.
-
-![Testomat.io - Filter by Milestone](./images/filter_milestone_1.png)
-
-### Using Advanced TQL Filters
-
-For more complex queries or when building custom dashboards, you can use the TQL console to filter by milestone properties.
-
-1. Open the Tests, Runs, or Plans tab.
-2. Click 'Query Language Editor' icon at the header of the page.
-3. Enter filter query.
-4. Click **'Apply'** button.
-
-![Testomat.io - Filter by Milestone](./images/filter_milestone_2.png)
-
-## Milestone Analytics & Progress Reports
-
-### Version Tracking & Audit Logs
-
-Every time a milestone is linked or unlinked from an item, Testomat.io records an audit trail. This version record documents exactly who made the change, when it occurred, and which artifact was modified, making history tracking seamless.
-
-You can review this real-time history stream on the **'Pulse'** page.
-
-![Testomat.io - Audit log Milestone](./images/audit_log_milestone_1.png)
-
-### Milestone Dashboards
-
-Clicking on any **milestone name** opens three dedicated reporting views designed to measure your development and testing velocity:
-
-1. **Milestone Tests:** Displays an automated breakdown of test outcomes, detailing total execution history, pass/fail rates, and overall success percentages for the specific milestone scope.
-
-![Testomat.io - Milestone Tests Dashboard](./images/milestone_tests_dashboard.png)
-
-2. **Milestone Completion:** Evaluates overall readiness by tracking total assigned items against fully executed and partially executed tasks to calculate an overall milestone completion percentage.
-
-![Testomat.io - Milestone Tests Dashboard](./images/milestone_completion_dashboard.png)
-
-3. **Milestone Run Stats:** Provides deeper technical execution insights, detailing your automation vs. manual testing ratios, current defect/bug counts, and a helpful list of slow-running tests impacting pipeline speed.
-
-![Testomat.io - Milestone Tests Dashboard](./images/milestone_runstats_dashboard.png)
-
-:::note
-
-If a single milestone is shared across multiple projects, Testomat.io dynamically aggregates data from all participating projects into a unified, company-wide health report.
-
-![Testomat.io - Milestone Dashboard](./images/milestone_dashboard_1.png)
-:::

package/skills/testeiya/testomatio-docs/docs/advanced/shortcuts/index.md

@@ -1,48 +0,0 @@
----
-title: Keyboard Shortcuts
-description: This guide covers keyboard shortcuts in Testomat.io to enhance efficiency when creating and editing tests. It includes shortcuts for opening windows, saving, creating test cases or suites, and using markdown for formatting. Both Windows and macOS keyboard combinations are provided to streamline the workflow.
-type: article
-url: https://docs.testomat.io/advanced/shortcuts
-head:   
-  - tag: meta
-    attrs:
-      name: keywords
-      content: Testomat.io, keyboard shortcuts, test management, efficiency, test creation, markdown, Windows, macOS, test cases, test suites, productivity tools
----
-
-Keyboard shortcuts are combinations of keys that perform specific tasks more quickly than using a mouse, enhancing efficiency and productivity by allowing users to execute commands without navigating through menus.
-
-## Hint For Shortcuts
-
-You can use the hint for shortcuts on the **Tests** page.
-
-![Testomat.io - Hint For Shortcuts](./images/New_bKBlpFmw_2024-08-14.gif)
-
-## Shortcuts For Creating And Editing Tests
-
-You can use shortcut commands to create/edit Test Cases or Suites.
-
-| Function                                       | Windows            | macOS             |
-|------------------------------------------------|--------------------|-------------------|
-| Opens the window to create a new **Suite**     | `Ctrl + I`         | `Cmd + I`         |
-| Save & Create New Suite in create mode         | `Shift + Ctrl + S` | `Shift + Cmd + S` |
-| Save & View Suite in edit mode                 | `Shift + Ctrl + S` | `Shift + Cmd + S` |
-| Opens the window to create a new **Test Case** | `Ctrl + U`         | `Cmd + U`         |
-| Save & Create New Test Case in create mode     | `Shift + Ctrl + S` | `Shift + Cmd + S` |
-| Save & View Test Case in edit mode             | `Shift + Ctrl + S` | `Shift + Cmd + S` |
-
-## Markdown Shortcuts
-
-Use Markdown shortcuts to edit test case description quickly and easily.
-
-| Function       | Windows            | macOS             |
-|----------------|--------------------|-------------------|
-| Bold           | `Ctrl + B`         | `Cmd + B`         |
-| Italic         | `Ctrl + I`         | `Cmd + I`         |
-| Heading 2      | `Ctrl + 1`         | `Alt + 2`         |
-| Heading 3      | `Ctrl + 2`         | `Alt + 3`         |
-| Heading 4      | `Ctrl + 3`         | `Alt + 4`         |
-| Quote Block    | `Ctrl + Shift + K` | `Cmd + Shift + K` |
-| Link           | `Ctrl + U`         | `Cmd + U`         |
-| Ordered List   | `Ctrl + Shift + 7` | `Alt + ,`         |
-| Unordered List | `Ctrl + Shift + 8` | `Alt + .`         |