testeiya 0.2.1 → 0.3.10

package/skills/testeiya/testomatio-docs/docs/project/runs/temporary-tests-notes.md

@@ -1,223 +0,0 @@
----
-title: Temporary Tests - Notes
-description: Learn how to use Notes in Testomat.io to create, manage, and convert temporary test cases directly during manual test runs. This guide covers creating Notes at the global or suite level, converting them into permanent test cases, and their automatic inclusion in test plans.
-type: article
-url: https://docs.testomat.io/project/runs/temporary-tests-notes
-head:
-  - tag: meta
-    attrs:
-      name: keywords
-      content: temporary tests, notes, manual runs, create notes, convert notes, convert to test, temporary test cases, ad-hoc tests, corner case testing, test plan updates, manual test execution, Testomat.io
----
-
-**Notes** in Testomat.io cover most key features of an ideal **Temporary Test Case**, providing QA teams with clear benefits and practical use cases. Notes are temporary tests that can be created directly within a test run, allowing testers to capture observations, ad-hoc scenarios, or corner-case tests quickly and efficiently, without cluttering the main test repository. Notes can later be converted into permanent test cases if they prove valuable, ensuring important tests are preserved and included in future test plans.
-
-### Benefits
-
-- **Quick creation during a test run**: Notes can be created directly during the test run, allowing instant capture of new scenarios or discovered issues without leaving the current context.
-- **Isolation from the main repository**: Notes are localized in a global **Notes** suite, keeping them separate from permanent test cases.
-- **Visual distinction in the UI**: Notes are marked with an icon and highlighted in purple, making them easy to identify at a glance.
-- **Convertible to permanent test cases**: Notes can be converted during a run or from the run report, enabling important scenarios to be added to regression without data loss.
-- **Automatic inclusion in test plans after conversion**: If the suite where the Note was created is part of a test plan, the converted note to test is automatically added and updates the plan.
-
-### How to Create Notes Within a Run
-
-During a test run, **Notes** can be created at two different levels, depending on whether you want them tied to a specific suite or remain global:
-
-- **Global Notes for the Run**: These Notes are stored in the main **Notes** suite for the run and are not associated with any specific suite or functionality. They are useful for capturing observations or ad-hoc scenarios that apply across the entire test run.
-
-- **Suite-Level Notes**: These Notes are created within **a specific suite**, allowing you to document observations directly related to particular tests or functionalities. This makes it easier to track and manage Notes associated with individual suites.
-
-#### Global Notes for the Run
-
-Let's go step by step to see how it works for **Global Notes for the Run:**
-
-1. Navigate to the **Runs** page
-2. Click the **Manual Run** button to start a new manual run
-
-![Manual Run button](./images/att1_1364.png)
-
-3. Select a **test plan**
-
-:::note
-
-For detailed run configuration, see [How to Configure a Manual Run.](https://docs.testomat.io/project/runs/running-tests-manually/#how-to-configure-a-manual-run)
-
-:::
-
-4. Click the **Launch** button
-
-![Launch a test plan](./images/att2_1364.png)
-
-5. Click the **Create notes +** button to add your first note
-
-![first note creation](./images/att3_1364.png)
-
-6. When the **Create note** window opens, fill in the following information:
-
-- **Note title** (required)
-- **Status:** Passed, Failed, Skipped (optional)
-- **Sub-status** (optional)
-- **Result message** (optional)
-
-7. Click the **Save note** button to save your note
-
-![Save a single note](./images/att4_1364.png)
-
-8. Or, enable the **Bulk mode** to create multiple notes at once
-9. In Bulk mode, fill in the following information:
-
-- **Note titles:** each line corresponds to the title of a new note (required)
-- **Status:** applied to all notes (Passed, Failed, Skipped) – (optional)
-- **Sub-status:** (optional)
-- **Result message:** (optional)
-
-10. Click the **Save # notes** to save all notes at once
-
-![Create bulk notes](./images/att5_1364.png)
-
-#### Suite-Level Notes
-
-Let's go step by step to see how it works for **Suite-Level Notes:**
-
-1. Navigate to the **Runs** page
-2. Click the **Manual Run** button to start a new manual run
-
-![Manual Run button](./images/att1_1364.png)
-
-3. Select a **test plan**
-
-:::note
-
-For detailed run configuration, see [How to Configure a Manual Run.](https://docs.testomat.io/project/runs/running-tests-manually/#how-to-configure-a-manual-run)
-
-:::
-
-4. Click the **Launch** button
-
-![Launch a test plan](./images/att2_1364.png)
-
-5. Click the **Add note to suite** button next to the specific suite
-
-![Create a note to suite](./images/att6_1364.png)
-
-:::note
-
-If the **Add note to suite** button doesn't appear next to the suite, please enable **'Show Creation Buttons'** mode in the extra menu.
-
-![Show Creation Buttons](./images/att12_1364.png)
-
-:::
-
-6. When the **Create Note** window opens, fill in the following information:
-
-- **Note title** (required)
-- **Status:** Passed, Failed, Skipped (optional)
-- **Sub-status** (optional)
-- **Result message** (optional)
-
-7. Click the **Save note** to save your note
-
-![Save a single note](./images/att4_1364.png)
-
-8. Or, enable the **Bulk mode** to create multiple notes at once
-9. In Bulk mode, fill in the following information:
-
-- **Note title:** each line corresponds to the title of a new note (required)
-- **Status:** applied to all notes (Passed, Failed, Skipped) – (optional)
-- **Sub-status:** (optional)
-- **Result message:** (optional)
-
-10. Click the **Save # notes** to save all notes at once
-
-![Create bulk notes](./images/att5_1364.png)
-
-#### Quick Actions
-
-To make the process of creating and managing Notes even faster, you can use the following quick actions:
-
-- Press **Enter** to create a Note — when adding a single Note (not in Bulk mode), simply type the title and press Enter to create it instantly, without clicking the Save note button.
-- Double-click to edit a Note title — you can quickly rename an existing Note by double-clicking its title directly in the Notes window.
-
-These shortcuts speed up the workflow and make it easier to capture insights during manual test runs.
-
-### How to Convert Notes to Tests
-
-Notes can be converted into permanent test cases:
-
-- During a manual run
-- After the manual run is finished, in the Run Report
-
-When converting a Note:
-
-- All information is preserved, including title, status, sub-status, result message, linked defects, edited metafields, and attachments
-- You can modify the test title, description, or any other details both during and after conversion
-- If the suite where the Note was created is part of a test plan, the new test case is automatically added to that plan
-
-#### Converting During a Run
-
-1. Open the **created note** within the test run
-2. Click the **Convert to test** button
-
-![Convert to test](./images/att7_1364.png)
-
-3. When the **Select suite for test** window opens, search suite by title or select the specific suite manually
-4. Click the **Select** button
-
-![Select destination for test](./images/att8_1364.png)
-
-5. When **Add Description** window opens,
-
-- Update a title of a test (or leave it as it is)
-- Add description (optional)
-
-6. Click the **Save test** button
-
-![Save test](./images/att9_1364.png)
-
-The Note is removed automatically after conversion. The test is saved in the selected suite and becomes visible both in the ongoing run and on the Tests page.
-
-#### Converting from the Run Report
-
-Notes can be converted into permanent tests directly from the Run Report. There are two ways to open the report for a completed run:
-
-- Option 1: Via sidebar in the completed run
-- Option 2: Via Run Report
-
-Both options lead to the same interface containing the list of Notes. To convert a Note:
-
-1. Open the **Run Report** for the completed test run with created notes
-2. Click the **Convert to test** button at the right side
-
-**Via sidebar in the completed run**
-
-![Convert to test via sidebar](./images/att10_1364.png)
-
-**Via Run Report**
-
-![Via Run Report](./images/att13_1364.png)
-
-3. When the **Select suite for test** window opens, search suite by title or select the specific suite manually
-4. Click the **Select** button
-
-![Select destination](./images/att11_1364.png)
-
-5. When the **Add Description** window opens,
-
-- Update a title of a test (or leave it as it is)
-- Add description (optional)
-
-6. Click the **Save test** button
-
-![Save test](./images/att9_1364.png)
-
-The Note is removed automatically after conversion. The test is saved in the selected suite and becomes visible both in the ongoing run and on the Tests page.
-
-### Use Cases
-
-- Capture ad-hoc or unexpected scenarios immediately during execution
-- Document results of manual testing without creating permanent test cases
-- Identify coverage gaps and mark additional checks for future regression testing
-- Promote temporary Notes to permanent test cases that automatically join test plans
-
-Notes provide quick creation, isolation, visual distinction, and flexible conversion, helping QA teams capture and manage valuable testing insights efficiently.

package/skills/testeiya/testomatio-docs/docs/project/steps-snippets/snippets.md

@@ -1,68 +0,0 @@
----
-title: Snippets
-description: A snippet - is a piece of text or collection of steps that can be used as autocompletion during creating tests. This can be used for any part of a test case. 
-type: article
-url: https://docs.testomat.io/project/steps-snippets/snippets
-head:
-  - tag: meta
-    attrs:
-      name: keywords
-      content: Testomat.io, Snippets, Test Management, QA Tools
----
-
-A snippet - is a piece of text or collection of steps that can be used as autocompletion during creating tests. This can be used for any part of a test case. 
-
-When a new test case or suite needs to be created, you can simply call a previously created snippets, to add information that you need with one click. This makes test creation faster and simplier.
-
-As well you can use snippets for creating and managing test data.
-
-## How to Create a Snippet
-
-1. Go to **'Steps'** page.
-2. Click **'+'** icon.
-3. Select **'Snippet'** option from the dropdown.
-
-![Testomat.io - Snippet](./images/Create_snippet_1.png)
-
-4. Enter **'Title'** for snippet.
-5. Add a piecce of text or steps.
-6. Click **'Save'** button.
-
-![Testomat.io - Snippet](./images/Create_snippet_2.png)
-
-After snippet is created you can use it during your test case creation.
-
-:::note
-
-You can find your snippets in the relevant section on 'Steps' page and update them at any time.
-
-![Testomat.io - Snippet](./images/Snippet.png)
-
-:::
-
-## How to Add Snippet to Test Case
-
-1. Go to **'Tests'** page.
-2. Click **'+Test'** button to add a new test case (or open the one that you want to edit).
-
-![Testomat.io - Snippet](./images/Create_snippet_3.png)
-
-3. Select the Suite.
-4. Click **'Select'** button.
-
-![Testomat.io - Snippet](./images/Create_snippet_4.png)
-
-5. Add test case title.
-6. Click **'Trigger suggestions'** button.
-
-![Testomat.io - Snippet](./images/Create_snippet_5.png)
-
-7. Select the snippet that you want to use from the suggested list.
-
-![Testomat.io - Snippet](./images/Create_snippet_6.png)
-
-The snippet content is successfully added to the test case.
-
-![Testomat.io - Snippet](./images/Create_snippet_7.png)
-
-[![CleanShot 2022-05-27 at 20 15 05@2x](./images/170756914-83b1e618-b039-45f5-b051-7f6fab0821aa.jpg)](https://youtu.be/k8WVtGDiUjs)

package/skills/testeiya/testomatio-docs/docs/project/steps-snippets/steps.md

@@ -1,181 +0,0 @@
----
-title: Steps Database
-description: Learn how to utilize the Steps Database in Testomat.io to store, reuse, and auto-complete test steps across projects. This guide covers creating, editing, renaming steps, and using snippets for efficient test writing. Save time and maintain consistency by leveraging the Steps Database during test creation, including both classical and BDD-style tests.
-type: article
-url: https://docs.testomat.io/project/steps-snippets/steps
-head:  
-  - tag: meta
-    attrs:
-      name: keywords
-      content: Testomat.io, Steps Database, test steps, step reuse, test management, BDD tests, classical tests, test automation, QA tools, step autocompletion
----
-
-Testomat.io offers functionality for test steps re-using and autocompletion. This feature helps you save time during test cases creation and make the process faster.
-
-## How to Add a New Step to the Steps Database
-
-There are few ways to create steps in the **Steps Database** from the **'Steps'** page:
-
-**Option 1**
-
-1. Open **'Steps'** page.
-2. Enter the step into the empty field.
-3. Click **'Create'** button.
-
-![Testomat.io - Add Steps](./images/Add_step_1.png)
-
-**Option 2**
-
-1. Open **'Steps'** page.
-2. Сlick **'Plus'** button.
-3. Select **'Step'** option from the dropdown list to add context to the step.
-
-![Testomat.io - Add Steps](./images/Add_step_2.png)
-
-After the **'New Step'** screen is displayed:
-
-4. Add the step.
-5. Add a step description to describe in which context this step can be used (optional).
-6. Click **'Save'** button.
-
-![Testomat.io - Add context to the step](./images/Add_step_3.png)
-
-The new step has been created!
-
-![Testomat.io - New step created](./images/Add_step_4.png)
-
-:::note
-
-You can create Steps for **BDD Projects** in the same way as for Classical Projects, following the same rules.
-
-![Testomat.io - New step created](./images/Add_BDD_step_1.png)
-
-:::
-
-## How to Add a New Step in Editor for Classical Tests
-
-Create your steps while writing your classical tests! Testomat.io Editor gives the ability to save your test description as steps directly to the **Steps Database**.
-
-Open Test Case Editor and create new steps by starting the line with the asterisk sign `*` or a numbered list (e.g., `1.`).
-
-![Testomat.io - Add Steps](./images/Add_step_5.png)
-
-Save the test, and the new steps will be added in the Database.
-
-![Testomat.io - Add Steps](./images/Add_step_6.png)
-
-:::note
-
-Only steps created in the Test Editor using `*` or `number list` under a step header (e.g., `## Steps`) will be created/saved in the **Steps Database**.
-
-:::
-
-:::note
-
-If your recently added steps are not displaying in the autocomplete list, you need to refresh steps in the **Steps Database** to see them. To do this:
-
-Open **'Steps'** page (1) -> Click **'Extra menu'** button (2) -> Select **'Refresh Steps'** option (3).
-
-![Testomat.io - Refresh Steps](./images/Refresh_Steps.png)
-
-:::
-
-## How to Reuse Steps from Steps Database
-
-Testomat.io recommends reusing steps instead of creating new ones.
-
-Next time you need to use the same step, start typing the step inside the Editor. Use the asterisk sign `*` for an unordered list or number with dot (e.g., `1.`) for an ordered list. The Editor will display the autocomplete list with matching steps.
-**Select** the step from the autocomplete list to add it to your test case.
-
-![Testomat.io - Re-use Steps](./images/Reuse_step_1.png)
-
-You can also use the **'Add Steps (ordered)'** or **'Add Steps (unordered)'** buttons in the Editor panel to trigger the autocomplete list with all available steps.
-
-![Testomat.io - Re-use Steps](./images/Reuse_step_2.png)
-
-:::note
-
-When you use the **'Add Steps (ordered)'** or **'Add Steps (unordered)'** buttons the **'## Steps'** header will be added automatically if it wasn't previously added manually or via a template.
-
-:::
-
-## How to Add a New Step in Editor for BDD Tests
-
-The Testomat.io BDD Editor automatically creates steps and adds them to the Steps Database once a Scenario or Feature File is saved. You do not need to add BDD steps separately.
-
-![Testomat.io - Steps in BDD](./images/BDD_Steps_1.png)
-
-:::note
-
-Don't include Given/When/Then in a step. Each step can be used in any of these contexts.
-
-:::
-
-![Testomat.io - Steps in BDD](./images/BDD_Steps_2.png)
-
-## How To Rename A Step
-
-You may need to update existing steps to suit new project requirements. You can rename required steps on the **'Steps'** page. This action automatically updates all tests containing changed step, so you do not need to change each test individually.
-
-1. Open **'Steps'** page.
-2. Click on the Step you want to update.
-3. Click **'Edit'** button in the displayed window.
-
-![Testomat.io - Steps Update](./images/Update_Steps_1.png)
-
-4. Update the Step's name.
-5. Click **'Save'** button.
-
-![Testomat.io - Steps Update](./images/Update_Steps_2.png)
-
-6. Confirm the action on the displayed pop-up.
-
-![Testomat.io - Steps Update](./images/Update_Steps_3.png)
-
-7. Check description for related Test Cases after the Step is renamed.
-
-![Testomat.io - Steps Update](./images/Update_Steps_4.png)
-
-[![Testomat.io - Steps](./images/170752475-7899459d-0533-45b4-904e-1f88e9f61c2c.jpg)](https://youtu.be/z5C3GYtl_HU)
-
-## How to Merge Steps
-
-There might be a situation when there are a few similar steps in the Steps Database. You can use **'Merge'** feature to unite them into one step, to keep your tests clean. This feature is available for **Classical** and **BDD** projects.
-
-1. Open **'Steps'** page.
-2. Enable **'Multi-select'**.
-3. Select the Steps you want to merge.
-4. Select **'Merge'** option from the bottom menu panel.
-
-![Testomat.io - Merge Steps](./images/Merge_Steps_1.png)
-
-5. Enter the Step that you want to keep (the first step will be pre-selected by default, but you can change it manually based on your needs).
-6. Click **'Merge'** button.
-
-![Testomat.io - Merge Steps](./images/Merge_Steps_2.png)
-
-:::note
-
-After your steps are **Merged**, the description of all tests where these steps are used will be updated.
-
-:::
-
-![Testomat.io - Merge Steps](./images/Merge_Steps_3.png)
-
-## How to Delete Unused Steps
-
-It might be the case when you deleted some test cases, and now some steps are unnecessary. To keep your **Steps Database** clean, you can delete unused steps.
-
-1. Open **'Steps'** page.
-2. Click **'Extra menu'** button.
-3. Select **'Delete Unused Steps'** option.
-
-![Testomat.io - Delete Unused Steps](./images/Delete_Steps_1.png)
-
-4. Confirm action on the displayed menu.
-
-![Testomat.io - Delete Unused Steps](./images/Delete_Steps_2.png)
-
-All unused Steps deleted from **Steps Database**.
-
-![Testomat.io - Delete Unused Steps](./images/Delete_Steps_3.png)

package/skills/testeiya/testomatio-docs/docs/project/tests/bdd-test-case-editor.md

@@ -1,98 +0,0 @@
----
-title: BDD Test Case Editor
-description: Learn how to write and manage BDD test scenarios using Testomat.io. This guide explores creating Gherkin-based tests, editing feature files, and using BDD workflows to improve collaboration, traceability, and test automation.
-type: article
-url: https://docs.testomat.io/project/bdd_editor
-head:
-  - tag: meta
-    attrs:
-      name: keywords
-      content: test design, test cases, test management, test automation, testing techniques, Testomat.io, BDD, Gherkin, Cucumber, test scenarios, project workflow, software testing
----
-
-## Test Case Editor
-
-Test Case Editor is a dynamic interface, designed to accommodate the diverse requirements of test case formulation. Through this platform, testers wield the power to architect meticulously structured test scenarios, encompassing a range of variables, actions, expected results, and potential outcomes.
-
-Regarding test case creation, Testomat.io offers two distinct editor types: the **Classical** Editor and the **BDD** (Behavior-Driven Development) Editor. Each caters to different testing methodologies and user preferences, enabling testers to choose the approach that best aligns with their needs.
-
-Let's have a look at **BDD** Editor.
-
-## BDD Editor Review
-
-As you embark on the journey of crafting and refining BDD scenarios, this innovative platform empowers you to shape narratives into meticulously executable tests. At its core, the BDD Editor encapsulates the essence of collaboration, precision, and agility, delivering a comprehensive solution for modern testing workflows. Here, you'll create user stories, scenarios, and document expected behaviors with an eloquence that bridges the gap between technical and non-technical stakeholders.
-
-**Feature File Editor**
-
-In the context of BDD, the Feature File serves as the canvas upon which your software's behavior is painted.
-
-Let's see what we have here!
-
-![Edit Feature File](./images/BDD_edit_suite.png)
-
-1. **Editing Area** – Displays the Feature File with Given/When/Then steps.  
-2. **Attachments** – Upload supporting files via the attachments dialog.  
-3. **Extra Menu** – Access additional options.  
-4. **Autocomplete Steps** – Toggle step suggestions.  
-5. **Autocomplete Snippets** – Toggle snippet suggestions.  
-6. **Autocomplete Tags** – Toggle tag suggestions.  
-7. **Fullscreen** – Enter a distraction-free workspace.  
-8. **Format** – Structure Scenarios into Gherkin format.  
-9. **Set Labels** – Assign existing labels or create custom fields.  
-10. **Save** – Save your work.  
-11. **Go Back** – Return to the previous screen.  
-12. **Close** – Exit the editor.
-
-**Scenarios Editor**
-
-Beyond Feature Files lies the individual tests. Here, the BDD Editor grants you the ability to sculpt scenarios with precision, breaking down user behaviors into granular steps and verifiable outcomes. Each test becomes a symphony of detail, harmonizing the user's journey with the software's responses. By editing separate tests within the BDD Editor, you orchestrate complex interactions, validations, and expectations.
-
-![Edit scenario](./images/BDD_edit_test.png)
-
-1. **Editing Area** – Displays Scenarios with Given/When/Then steps.  
-2. **Attachments** – Upload supporting files via the attachments dialog.  
-3. **Extra Menu** – Access additional options.  
-4. **Autocomplete Steps** – Toggle step suggestions.  
-5. **Autocomplete Snippets** – Toggle snippet suggestions.  
-6. **Autocomplete Tags** – Toggle tag suggestions.  
-7. **Fullscreen** – Enter a distraction-free workspace.  
-8. **Set Labels** – Assign existing labels or create custom fields.  
-9. **Change State** – Update the test state (e.g., manual to automated).  
-10. **Save** – Save your work.  
-11. **Go Back** – Return to the previous screen.  
-12. **Close** – Exit the editor.
-
-
-**Saving changes in the feature file as a draft**
-
-There is an option to save unfinished changes in the feature file as a draft. This is useful when the scenario isn't finalized yet and may contain syntax errors.
-
-Drafts can be applied at both the suite and test levels - in other words, Feature and Scenario description.
-When editing a test, if the editor prevents you from saving changes (e.g., due to syntax errors), the relevant error message will appear at the bottom of the screen. If you plan to fix the scenario later but don’t want to lose your changes, you can use the **Save to Draft and View Test** option:
- 
-![Save To Draft and View Test option](./images/Save_To_Draft_and_View_Test.png)
-
-The next time you open the test in edit mode, you will see two additional buttons:
-
-1. **Apply Draft to Description** – Applies the last saved draft to the scenario text section.
-
-2. **Delete Draft** – Deletes the existing draft.
-
-![ Apply Draft to description and Delete Draft buttons](./images/apply_draft_or_delete_buttons.png)
-
-> **Note:** Only one draft can be saved at a time.
-
-
-## Cross-Linking Tests, Suites and Folders
-
-Another useful feature that allows you to cross-link test cases, suites, and folders by embedding their unique IDs directly into the description of another test or suite. This functionality provides you with clickable links to other related items within your project, and clicking on it displays a dynamic preview of the linked test, suite or folder in an additional window. 
-
-This feature is available for Classical and BDD projects but have a difference in formating.
-
-### For BDD Project
-
-In the projects that use BDD format, you need to follow certain rules to maintain your test structure.
-If you want to add clickable references to a test or suite in a BDD project, use **#** followed by their IDs. Clicking the link will open the test or suite in detail view, making navigation and traceability more seamless.
-
-![Testomat.io - Use ID In Tests](./images/link_bdd.gif)
-