testeiya 0.2.0

package/skills/testeiya/testomatio-docs/docs/advanced/tags-labels/labels-and-custom-fields.md

@@ -0,0 +1,201 @@
+---
+title: Labels and Custom Fields
+description: Learn how to use labels and custom fields in Testomat.io to organize and categorize tests, suites, runs, plans, and steps. This guide covers creating and setting up labels with specific scope and visibility, as well as configuring custom fields with List, Number, and String types. It also explains how to assign labels in bulk, make them required by default, filter by them, and manage user permissions for enhanced project organization and security.
+type: article
+url: https://docs.testomat.io/advanced/tags-labels/labels-and-custom-fields
+head:
+  - tag: meta
+    attrs:
+      name: keywords
+      content: Testomat.io, tags, labels, custom fields, Filter visibility, List visibility, Assign Labels, Mass-assign labels, filter by labels, Required Labels, Labels Permission, test management, categorization, testing workflow, custom data, test organization, filter tests, QA, test case management
+---
+
+## How to Add Labels & Custom Fields
+
+Labels can be easily added in Project Settings
+
+1. Go to Settings.
+2. Select Labels & Fields.
+3. Enter a title for the label.
+4. Click Create button.
+
+![Testomatio - Add Label](./images/Create_Labels.png)
+
+## How to Setup a Label
+
+Before setting up Labels & Custom Fields we need to learn about **Scope** and **Visibility** parameters.
+
+**Scope** defines what pages you want to apply the Label & Custom Field. Here you can define on what pages you want to use it. You can apply it to tests, suites, runs, plans, steps and templates.
+
+![Testomatio - Setup Label](./images/Labels.png)
+
+**Visibility** defines how a Label & Custom Field should be shown in UI.
+
+- Filter visibility will show a Label or Custom Field in the Filter Bar, so you can sort your items quickly.
+- List visibility will show a Label or Custom Field in the tests tree, a list of runs, plans, or steps.
+
+![Testomatio - Setup Label](./images/Visibility_Labels.png)
+
+Now it's time to set up your label!
+
+1. Scope - pick entities you want this label to be applied.
+2. Visibility - labels can be shown in the Filter bar, in the list of entities, or in both views.
+3. Custom Field - expand label capability to a custom field.
+
+![Testomatio - Setup Label](./images/Setup_Labels.png)
+
+## How to Setup a Custom Field
+
+There are such Field Types in Custom Fields: List, Number, and String. Let's take a look at each type.
+
+### Custom Field: List
+
+Custom Field with List type allows creating a list of your choice. You can put there any values to meet your testing needs.
+
+1. Select a List type of Custom Field.
+2. Add a new item per line.
+3. Toggle **Hide custom field title if value is set** if you don't want to show Custom Field title.
+4. Click Save button.
+
+![Testomatio - Custom Field List](./images/Custom_Field_List.png)
+
+### Custom Field: Number
+
+1. Select a Number type of Custom Field.
+2. Toggle **Hide custom field title if value is set** if you don't want to show Custom Field title.
+3. Click Save button.
+
+![Testomatio - Custom Field Number](./images/Custom_Field_Number.png)
+
+### Custom Field: String
+
+1. Select a String type of Custom Field.
+2. Toggle **Hide custom field title if value is set** if you don't want to show Custom Field title.
+3. Click Save button.
+
+![Testomatio - Custom Field String](./images/Custom_Field_String.png)
+
+## How to Assign Labels & Custom Fields
+
+- Add labels on the entity level
+
+1. Open a Suite/ Test.
+2. Click Extra button.
+3. Click Labels.
+
+![Testomatio - Assign Label & Custom Field](./images/Assing_Label.png)
+
+4. Select Labels.
+5. Click Add Custom Field.
+6. Select Custom Fields.
+7. Click Save button.
+
+![Testomatio - Assign Label & Custom Field](./images/Set_Labels.gif)
+
+OR:
+
+1. Open a Suite/ Test.
+2. Click Set Labels button the title name.
+3. Select Labels & Custom Fields.
+4. Click Save button.
+
+![Testomatio - Assign Label & Custom Field](./images/Set_Labels_2.gif)
+
+- Mass-assign labels using our multiselection mode
+
+1. Enable multiselection mode.
+2. Select Tests/ Suites.
+3. Click Labels button.
+
+![Testomatio - Multi-assign Label & Custom Field](./images/Mass_assign.png)
+
+4. Select Labels & Custom Fields.
+5. Click Add.
+
+![Testomatio - Multi-assign Label & Custom Field](./images/Mass_assign_set_1.png)
+
+:::note
+
+To edit Labels & Custom fields or add a new one click **Manage labels** button directly from **Set Labels** page -> it will redirect you to **Labels** page.
+
+:::
+
+![Testomatio - Multi-assign Label & Custom Field](./images/Manage_Labels.png)
+
+## How to Set Up Labels and Custom Fields as Required
+
+If you want to have some **Custom Fields** as required by default when creating Test Cases or Suites, create a Template with those **Custom Fields** and set it up as the default:
+
+1. Go to Settings -> Templates.
+2. Open an existing Template or create a new one.
+3. Enable Default option.
+4. Select **Custom Fields** you want to make required.
+5. Click Update button.
+
+![Testomatio - Required Labels](./images/Required_Labels.png)
+
+6. Go to Tests.
+7. Click '+' to create new Test Case.
+8. Add values to Custom fields via Set Labels page.
+
+![Testomatio - Required Labels](./images/Required_Labels_2.gif)
+
+## How to Filter by Labels and Custom Fields
+
+You can click the Label on the Filter Bar
+
+![Testomatio - Filter Label & Custom Field](./images/Filter_by_label_1.png)
+
+Or enable Filters, pick fields and values then click Apply
+
+![Testomatio - Filter Label & Custom Field](./images/Filter_by_label_2.png)
+
+:::note
+
+In case you need to filter your test cases by a few Labels and Custom Fields with multiple values, Testomat.io recommends using TQL for such search queries.
+
+:::
+
+## Multiple Values for Custom Fields
+
+There might be cases where you need to assign the same label with different values to the same test case or suite.
+
+To address this, Testomat.io enhanced the flexibility of Custom Fields by allowing multiple values to be assigned to test cases, suites, steps, etc.
+
+Lets see how this works:
+
+1. Open Test Case or Suite.
+2. Click Extra button.
+3. Click Labels.
+4. Select Custom Field with multiple values.
+5. Choose values from the displayed list for List Custom Field (or type a few values, separated by "," for Custom Field String).
+
+![Testomatio - Multi-select Custom Field](./images/Multi-select_custom_field.gif)
+
+Testomat.io also allows you to filter your test cases by one or a few Custom Field values.
+
+![Testomatio - Multi-select Custom Field Filtering](./images/Custom_field_filter.gif)
+
+## Permissions for Labels and Custom Fields
+
+To manage Labels and Custom Fields at the Project level, Testomat.io introduces 'Labels Permission' feature, which allows you to have a better control over metadata, maintain consistency, and prevent unauthorized modifications of Labels and Custom Fields.
+
+By default, this permission is disabled, allowing all users to create, edit, or delete Labels and Custom Fields. However, if the **Labels Permission** is enabled, only users with the **Owner** or **Manager** roles can create, edit, or delete Labels and Custom Fields. Team members with lower access levels can still use existing Labels and Custom Fields but will not be able to alter them.
+
+This feature improves project organization, enhances security, and streamlines collaboration by ensuring structured and standardized test management.
+
+To enable **Labels Permission** on Project level:
+
+1. Open your project and go to Settings.
+2. Select Project.
+3. Enable **Labels permission**.
+
+![Testomatio - Label Permission](./images/Permissions.png)
+
+:::note
+
+The **Owner** and **Manager** roles should be assigned to users in **Project Settings -> Users**.
+
+:::
+
+![Testomatio - Users](./images/Users.png)

package/skills/testeiya/testomatio-docs/docs/advanced/tags-labels/tags-or-labels.md

@@ -0,0 +1,94 @@
+---
+title: Tags or Labels
+description: Discover how to use labels, custom fields and tags in Testomat.io to enhance your test management. This guide explains how to categorize and organize tests with tags, labels, define custom fields for tailored test information, and filter by these fields for improved workflow efficiency. Learn to configure tags, labels and custom fields to streamline testing and improve data accessibility.
+type: article
+url: https://docs.testomat.io/advanced/tags-labels/tags-or-labels
+head: 
+  - tag: meta
+    attrs:
+      name: keywords
+      content: Testomat.io, tags, labels, custom fields, test management, categorization, testing workflow, custom data, test organization, filter tests, QA, test case management
+---
+
+**Tags, Labels & Custom Fields** are powerful features in a test management system that allow users to categorize and organize their testing data.
+
+**Tags and Labels** are keywords or phrases that can be applied to individual tests or test suites to provide an at-a-glance summary of the test's status, type, priority, or any other relevant information. They make it easy for users to filter and sort their tests to quickly find what they need.
+
+**Custom fields**, on the other hand, are user-defined fields that can be added to a test case to capture specific information. For example, custom fields can be used to store information such as the tester's name, the expected result, the test environment, or the date the test was last run. Custom fields make it possible for users to tailor the test management system to their specific needs, and to store and retrieve data in a consistent and meaningful way.
+
+Tags, Labels & Custom Fields can help users to streamline their testing process, increase the accuracy of their test data, and make it easier to find and analyze the information they need.
+
+## Tags vs Labels: What to Choose
+
+While both **Tags** and **Labels** help organize and categorize your tests, they serve slightly different purposes and excel in different situations. Understanding these differences can help you make the most of them.
+
+**Tags** are typically used to assign a specific keyword or category to test cases, making it easier to group, filter, or search for related tests. They are often used for ad-hoc categorization and usually have no strict hierarchy. 
+For example, Tags can represent various attributes, such as the type of test (for ex., `@Regression`, `@Smoke`, `@E2E`), associated features, or testing phases.
+
+In automation testing, a **Tag** is a segment of extra metadata that you can include on an individual test case or a group of tests. These tags are directly embedded in the test code, and allows you to specify additional information for your tests, which you can use to enhance your test runs. The testing tool will execute only tests containing that piece of information, as almost all modern testing tools and frameworks have integrated support for running a subset of tests, using tags. For example, execute all tests tagged as `@Regression` but skip `@Smoke` tests.
+
+![Testomatio - Tag in BDD](./images/Tags_in_BDD.png)
+
+On another side, **Labels** tend to be more structured than tags and can be used to signify specific statuses or groupings (for ex., priority, severity, localization), mark test case status or ownership. Also Testomat.io allows you to add multiple values to the same label. For example, you can create a Type label to categorize tests by type.
+They are more flexible, easy to change and manage, you can rearrange created and selected labels, as well as delete them from your project, from **Settings -> Labels&Fields** page, read more about how to set up labels below.
+
+![Testomatio - Labels](./images/Labels_1.png)
+
+#### Key Differences:
+
+| Criteria | Tag | Label |
+|---|---|---|
+| Purpose | To categorize and/or organize tests | To identify meta data related to tests or object |
+| Generality | More general | More specific |
+| Applications | More for automated tests less for manual | More for manual tests, less for automated |
+| Usage | Less flexible for describing specific details. More constant | More flexible, easy to change and manage, can have complex types and multiple values |
+| Use cases | Categorization, filtering, search, test plans, coverage, analytics | Track the progress, maintain, review, steps, runs, collaboration |
+
+The choice between **Tags** and **Labels** depends on your specific needs. For automated tests and broad categorization, Tags are the better choice.
+
+Conversely, Labels offer greater flexibility. You can mark test cases/ suites without altering their titles, customize Labels with various data types, and even assign multiple values to a single Label. 
+
+By understanding their strengths, you can leverage both Tags and Labels effectively to organize and manage your testing efforts.
+
+:::note
+
+Learn how to create and assign **Tags** in Testomat.io to organize your test cases and suites on the [Tags](https://docs.testomat.io/advanced/tags-labels/tags) page.
+
+Learn how to use **Labels** and **Custom Fields** in Testomat.io to organize and categorize tests, suites, runs, plans, and steps on the [Labels and Custom Fields](https://docs.testomat.io/advanced/tags-labels/labels-and-custom-fields) page.
+
+:::
+
+## Tags vs. Labels: Inheritance and Management
+
+To effectively organize your testing workspace, it is crucial to understand how **Tags** and **Labels** behave. Both follow a top-down inheritance model, meaning their configuration at the Suite level directly impacts the individual tests within that suite.
+
+### Inheritance Logic
+
+Both **Tags** (`@tag`) and **Labels** (`Key:Value pairs`) utilize the same inheritance behavior in Testomat.io:
+
+- **'Top-Down' Propagation:** Any Tag or Label applied to a Suite is automatically inherited by every test inside that suite.
+
+- **Management Constraint:** If you attempt to remove a tag or label from an individual test and it persists after saving, it is likely assigned to the **Parent Suite**. As long as the suite holds a specific tag/label, the test will inherit it. To remove it from the test, you must remove it from the suite level.
+
+:::note
+
+**Best Practice:** Only assign Tags and Labels at the Suite level if they are universal to every test in that folder. For more granular control, apply them directly to tests using the multi-select tool to avoid inheritance conflicts.
+
+:::
+
+### How to Properly Remove Inherited Attributes
+
+If a **Tag** or **Label** is assigned at the Suite level but should not apply to one specific test, follow this workflow:
+
+1. **Remove from Suite:** Navigate to the Suite settings and delete the Tag or Label. This will remove it from all tests in that folder.
+
+2. **Re-apply via Bulk Management:** Enable Multi-select mode in your project.
+
+- Select all tests that should have the attribute (excluding the one you want to keep clean).
+- Use the **'bulk action menu'** to add the Tag or Label back to the selected group.
+
+:::note
+
+Visit [Managing Inherited Tags](https://docs.testomat.io/advanced/tags-labels/tags/#managing-inherited-tags) section for more information.
+
+:::

package/skills/testeiya/testomatio-docs/docs/advanced/tags-labels/tags.md

@@ -0,0 +1,243 @@
+---
+title: Tags
+description: Learn how to create and assign tags in Testomat.io to organize test cases and suites. This guide explains the process of adding tags directly in the title, using autocomplete for existing tags, and refreshing the tag list. It also covers how to filter test cases by one or more tags for efficient test management and searching.
+type: article
+url: https://docs.testomat.io/advanced/tags-labels/tags
+head:
+  - tag: meta
+    attrs:
+      name: keywords
+      content: Testomat.io, tags, labels, custom fields, test management, filter by tags,categorization, testing workflow, custom data, test organization, filter tests, QA, test case management.
+---
+
+## How to Create and Assign Tags
+
+Tags help organize and categorize Test Cases and Suites for easier filtering, reporting, and management. You can create tags directly in titles or assign them in bulk using the multiselect feature. Tags applied at the Suite or Folder level automatically propagate to nested items, ensuring consistent organization across your project.
+
+### Create Tags via Title Field
+
+You can easily create tags directly to Test Cases or Suites via their titles.
+
+1. Open Test Case/Suite.
+2. Click the **Edit** button.
+3. Create tag starting with **@** symbol, directly within the Test Case or Suite title.
+4. Click the **Save** button.
+
+![Testomatio - Add tag](./images/Add_Tag.gif)
+
+All previously created tags are automatically saved in the system. To reuse a tag, simply type the **@** symbol in the Test Case title field and select the desired tag from the autocomplete dropdown.
+
+![Testomatio - Autocomplete tag](./images/Autocomplete_tag.png)
+
+:::note
+
+In case if you don't see a previously created tag in the autocomplete dropdown, refresh the page. Alternatively, go to **Settings -> Project** and click the **'Recalculate Tags'** button.
+
+:::
+
+![Testomatio - Recalculate Tags](./images/Recalculate_Tags.png)
+
+### Create Tags via Multiselect
+
+You can also create tags for multiple Suites or Tests at once using the **Multi-select** feature.
+
+1. Go to the **Tests** page.
+2. Enable **Multi-select** mode by clicking the **Multi-select** button.
+3. Select one or more Folder/Suites or Tests using the checkboxes.
+4. Click the **@ Tags** button in the bottom action bar.
+
+![Tags button](./images/att1_bulk_tag.png)
+
+5. In the **Select tags for suites** window, click **Create new tags**
+
+![Create new tags link](./images/att3_bulk_tag.png)
+
+6. Enter a new tag name starting with the **@** symbol and click **Add** button
+
+![New tag is created](./images/att4_bulk_tag.png)
+
+This method allows you to **create** and immediately **apply a new tag** to multiple items in just a few clicks. It helps you save time, speed up routine actions, and maintain consistent tagging across a large number of test cases or suites — without having to open them individually.
+
+## How to Bulk Update/Remove Tags
+
+Using the same **Multi-select** feature, you can manage tags for multiple **Folders/Suites** or **Tests** at once — adding or removing tags in bulk.
+
+1. Go to the **Tests** page.
+2. Enable **Multi-select** mode by clicking the **Multi-select** button.
+3. Select one or more Folder/Suites or Tests using the checkboxes.
+4. Click the **@ Tags** button in the bottom action bar.
+
+![Tags button](./images/att1_bulk_tag.png)
+
+5. In the **Select tags for suites** window, choose the tag(s) you want to manage:
+
+- To assign a tag, search for it and/or select it from the list.
+- To remove a tag, search for it and/or select it from the list.
+
+6. Click **Add** to assign the selected tag(s).
+7. Click **Remove** to delete the selected tag(s).
+
+![Add or Remove tags](./images/att2_bulk_tag.png)
+
+This method allows you to efficiently manage tags across multiple items, ensuring consistent organization and saving time.
+
+## Managing Inherited Tags
+
+Tags applied directly at the **Suite** or **Folder** level follow a **'top-down'** rule:, all nested elements (child Suites or Tests) automatically inherit these tags. Because these tags belong to the parent, they cannot be deleted from individual child tests. You can only remove the tags at the same level where they were originally applied.
+
+:::note
+Partial removal (e.g., deleting a few tags from a single test inside a tagged Suite) is not supported.
+:::
+
+**To 'remove' an inherited tag from a single test, you must follow these steps:**
+
+1. **Remove the tag from the Parent:** 
+- Navigate to the Suite/Folder details page.
+- Click **'Edit'** button (or double-click on suite title).
+- Remove the tag on Suite level. 
+
+![Testomat.io - Remove tags](./images/Remove_suite_tag_1.gif)
+
+This will remove it from all nested items.
+
+2. **Re-apply to specific tests:** If the other tests in that suite still need the tag, you must re-apply it to them **individually** or via **Multi-select**. For multi-select:
+- Enable **Multi-select** mode by clicking the **Multi-select** button.
+- Select one or more Tests using the checkboxes.
+- Click the **@ Tags** button in the bottom action bar.
+- Select tag from the list or create a new one.
+- Click **'Add'** button.
+
+![Testomat.io - Remove tags](./images/Remove_suite_tag_2.gif)
+
+### Bypassing Inheritance: Bulk Tagging at the Test Level
+
+If you want to tag every test in a suite but maintain the flexibility to remove them individually later, apply the tag to the Tests directly rather than the Suite itself:
+
+1. Enable **Multi-select** mode by clicking the **Multi-select** button.
+2. Click **'Select All Tests'** option.
+
+![Testomat.io - Add tags](./images/Add_suite_tag_1.png)
+
+3. Click the **@ Tags** button in the bottom action bar.
+4. Select tag from the list or create a new one.
+5. Click **'Add'** button.
+
+![Testomat.io - Add tags](./images/Add_suite_tag_2.png)
+
+This method ensures the tag exists on the test level, giving you total control to add or remove it from any specific case at any time.
+
+![Testomat.io - Add tags](./images/Add_suite_tag_3.gif)
+
+## How to Filter by Tags
+
+1. Enable Filters
+2. Select one or a few Tags from **Tag** dropdown list
+3. Click Apply button
+
+![Testomatio - Filtering by Tags](./images/Tag_filtering.png)
+
+## Tag Extraction Rules in Titles
+
+When writing titles, Testomat.io automatically detects tags marked with the `@` symbol. However, not every `@` occurrence is considered a valid tag.
+Below are detailed examples showing when tags **are recognized** and when they are **ignored**.
+
+**✅ Valid Tag Examples**
+
+```text
+"title with a simple @tag and some other @tag1"
+→ tags: ["tag", "tag1"]
+
+"@tag1 supertitle with leading tag and @tag inside title"
+→ tags: ["tag1", "tag"]
+
+"title with commed taglist @tag1: @tag2."
+→ tags: ["tag1", "tag2"]
+
+"title with commed taglist @tag1, @tag2.asd"
+→ tags: ["tag1", "tag2.asd"]
+
+"title @tag1. zxc"
+→ tags: ["tag1"]
+
+"title @tag1.asd zxc"
+→ tags: ["tag1.asd"]
+```
+
+**🚫 Ignored or Invalid Tags**
+
+```text
+"title with email test@test.test"
+→ tags: []
+
+"some_text_@tag"
+→ tags: []
+
+"some_text-@tag"
+→ tags: []
+
+"some_text*@tag"
+→ tags: []
+```
+
+**➕ Math Operators in Tags**
+
+```text
+"title with commed taglist @tag1+@tag2=@tag3"
+→ tags: ["tag1"]
+
+"title with commed taglist @tag1-@tag2=@tag3"
+→ tags: ["tag1"]
+
+"title with commed taglist @tag1*@tag2=@tag3"
+→ tags: ["tag1"]
+
+"title with commed taglist @tag1=@tag2=@tag3"
+→ tags: ["tag1"]
+
+"'title @tag1=:-.( asd"
+→ tags: ["tag1"]
+
+"'title @tag1=:-.) asd"
+→ tags: ["tag1=:-.)"]
+```
+
+**🔗 Tags Inside and Outside Brackets**
+
+**Outside brackets (ignored):**
+
+```text
+"some_text (sometext)@tag1 [sometext]@tag3"
+→ tags: []
+```
+
+**Inside brackets (partially detected):**
+
+```text
+"title (text @tag1)asda other text"
+→ tags: ["tag1)asda"]
+
+"title (text @tag1) asda"
+→ tags: ["tag1)"]
+
+"title (text @tag1( asda"
+→ tags: ["tag1"]
+
+"title [text @tag1]asda"
+→ tags: ["tag1"]
+
+"title [text @tag1] asda"
+→ tags: ["tag1"]
+```
+
+With these rules, you can better understand how tags are parsed from titles and avoid common pitfalls such as emails, operators, or invalid symbols.
+
+## Best Practices for Using Tags in Titles
+
+To ensure your tags are recognized consistently and remain easy to manage:
+
+- **Use simple words** → keep tags short, lowercase, and descriptive (e.g., `@smoke`, `@regression`).
+- **Avoid special characters** → symbols like `+`, `-`, `*`, `_`, or `=` can break parsing or truncate tags.
+- **Don’t use emails or URLs** → anything in the form `name@domain.com` is ignored.
+- **Separate tags with spaces or commas** → `@smoke, @ui` is correctly detected, while `@smoke@ui` may not be.
+- **Prefer placing tags at the end of titles** → improves readability and reduces the chance of misparsing inside brackets or punctuation.
+- **Keep consistency across your project** → agree on a common set of tags within your team to make filtering and reporting easier.

package/skills/testeiya/testomatio-docs/docs/advanced/test-artifacts/index.md

@@ -0,0 +1,135 @@
+---
+title: Artifacts
+description: Learn how Testomat.io handles test artifacts and attachments, such as screenshots, videos, and logs, to enhance test management and reporting. This guide explains how to add and manage attachments during test case creation, manual testing, and automated test execution with S3 cloud storage support. It also covers features like in-platform artifact preview and integrations with various frameworks and tools to streamline debugging and project documentation.
+type: article
+url: https://docs.testomat.io/advanced/test-artifacts/artifacts
+head:
+  - tag: meta
+    attrs:
+      name: keywords
+      content: test artifacts, test attachments, screenshots, videos, test management, test reporting, debugging, manual testing, automation testing, S3 storage, AWS, DigitalOcean, Azure, Google Cloud, CI/CD, preview attachments, suite-level attachments, folder-level attachments, readme section, Jira Integration, Video Capturing, Automated Tests Analytics
+---
+
+Testomat.io offers various ways to handle test artifacts and attachments, such as screenshots, videos, logs, documents, etc. These features enhance test management, reporting, and debugging by providing visual evidence and supporting documentation.
+
+You can add test artifacts and attachments during **test case creation**, **manual testing**, or **automation testing**.
+
+## Add Attachments to Test Cases
+
+Testomat.io allows you to add attachments, including screenshots, files, and videos to your test cases. It helps to visualize tests, make them more clear and offer additional information for QA managers, developers, other QAs, or stakeholders.
+
+You can add attachments during test case creation or editing by directly **dragging & dropping** them, using the hot key **CTR+C/CTR+V** for copy/past or by using the **browse a file** option.
+
+![Testomat.io - Add attachment](./images/Add_attachment_1.gif)
+
+For more details on adding and managing attachments, refer to the [Add Attachments to Test](https://docs.testomat.io/project/tests/test-case-creation-and-editing/#add-attachments-to-test).
+
+You can also manage attachments across Testomat.io by adding them to **suites**, **folders**, and the **readme section**. This streamline workflows by keeping all relevant files and documentation in one place. Whether you’re sharing important notes, reference materials, or test data, you can now attach them directly to the relevant test structures for easy access.
+
+**Use cases:**
+
+- **Suite-level attachments:** Attach detailed test execution reports or configuration files to specific test suites for easy reference by team members.
+- **Folder-level attachments:** Add relevant project documentation or setup instructions to test folders, ensuring that all files related to a specific testing area are easily accessible.
+- **Readme section attachments:** Include critical resources or additional context in the readme section, such as diagrams, code samples, or links to external resources, improving overall clarity for team members.
+
+## Delete Attachments
+
+If you no longer need your attachments, you can delete them.
+
+Go to [How to Delete Attachment from Test Case](https://docs.testomat.io/project/tests/test-case-creation-and-editing/#how-to-delete-attachment-from-test-case) section to read more about this feature.
+
+:::note
+
+You can delete attachments from Suite, Folder and Readme section in the same way you would from a Test Case.
+
+:::
+
+## Restore Attachments
+
+Before the attachment is permanently deleted from the store, you can restore it. 
+
+Go to [How to Restore Deleted Attachment](https://docs.testomat.io/project/tests/test-case-creation-and-editing/#how-to-restore-deleted-attachment) section to read more about this feature.
+
+:::note
+
+All deleted Attachments are stored for 30 days before being permanently deleted.
+
+:::
+
+## Add Test Arfifacts During Manual Testing
+
+Attaching a short video or screenshots is highly useful for manual testing, especially for failing tests. These artifacts provide comprehensive information, making it easier for the QA tester to understand what went wrong.
+
+To add test artifacts during manual tests execution:
+
+1. Launch a run.
+2. On manual run window, select the test case.
+3. **Drag&drop** the test evidence into the **'Attachments'** section (or use **browse a file** or **copy/paste** option).
+
+![Testomat.io - Add attachment](./images/Add_attachment_2.gif)
+
+## Preview Attachments
+
+Attachments are available for viewing without downloading. To preview an attachment, select it in the Test Case Attachment section to view it in the open dialog window.
+
+![Testomat.io - Preview attachment](./images/Preview_attachment_2.gif)
+
+Testomat.io also allows you to watch attached video or screenshots directly from the **Report** page.
+
+![Testomat.io - Preview attachment](./images/Preview_attachment_1.gif)
+
+Additionally, you can switch between list and tile views to make reviewing test artifacts easier.
+
+![Testomat.io - Preview attachment](./images/Preview_attachment_3.gif)
+
+## Add Test Arfifacts During Automation Testing
+
+Testomat.io also allows you to add test artifacts during automation testing.
+Test artifacts, which include screenshots and video files, provide a complete picture of your test results as soon as autotests are completed, helping you understand the root cause of a problem.
+
+### Support Artifacts Storing to S3
+
+This kind of implementation of **Video recording** or **Screenshots** artifacts is possible due to our integration with many **S3 Storages**: AWS, DigitalOcean, Azure, and Google Cloud. After a test run is completed, video and other artifacts are uploaded to the chosen storage, and from there, they automatically go to Testomat.io.
+
+Testomat.io provides the ability to download unlimited data by choosing one of the available S3 Storages depending on your company’s priorities or the location of your preferred CI\CD service. 
+
+:::note
+
+All cloud providers charge for their services. Be sure to check their rates in detail before starting.
+
+:::
+
+Thanks to **S3 Cloud Services** integration, you can easily find any test artifacts stored in the test project structure on your local PC or in the cloud when running tests on Github, Jenkins, or any other CI\CD service.
+
+### How Artifact Recording Works
+
+1. **Get test artifacts when you run autotests:** To enable this, you need to set the right parameters – specify the configuration of your cloud storage. As a result, all screenshots or video files from S3 Storage will be placed in the test report, helping you prioritize issues. You can configure artifacts to be collected from failed, passed, or all tests, whatever status was assigned to them after the end of the run. This parameter is typically configured within your testing framework (e.g., Cypress, Playwright), not in Testomat.io.
+
+:::note
+
+Read how to **Set up S3 Bucket** on the relevant [Test Artifacts](https://docs.testomat.io/test-reporting/artifacts/) page.
+
+:::
+
+2. **Upload a public or private test artifacts:** These processes are identical; the artifact travels the same path in both cases. But if a private format is selected, additional settings and data encryption are used. This feature is used by companies that pay special attention to data privacy and security of their projects or when company policy forbids public access to their projects. The necessary settings are set in the **'Artifacts'** tab and apply to all tests of a particular project. For more detail, visit the [Privacy](https://docs.testomat.io/test-reporting/artifacts/#privacy) section in the Docs.
+
+3. **Preview or download test artifact:** You can view videos or screenshots directly on the platform or download them on your device. The latter is relevant if you need to share the test results with stakeholders.
+
+:::note 
+
+If you share a private artifact, your recipient will receive a message that they do not have permission to view the file.
+
+:::
+
+### Associated Test Screenshot-Recording Features
+
+- **Reporters by Popular Testing Frameworks** – real-time reports supporting of popular programming languages give you a complete picture of the software product’s quality level. With Advanced Reporters by popular testing frameworks, you can see the results of end-to-end, integration, unit testing, and API testing. Thanks to the integration with many S3 Storages, our SaaS test management solution retrieves test artifacts (including screenshots during a test runs) and uploads them to the report in a convenient format.
+
+- **Automated Tests Analytics**  – all test results of test executions are used for in-depth analytics. Determining the percentage of test automation, the total number of tests, the ratio of tests to uncompleted tests, failed tests, [flaky tests](https://docs.testomat.io/project/analytics/#flaky-tests), never-run tests help prioritize daily tasks and make the process transparent to all Agile team members.
+
+- **Jira Integration** – after installing the [Jira plugin](https://docs.testomat.io/advanced/jira-plugin/), you have the ability to run test cases from Atlassian Jira and work on projects directly from either Jira or Testomat.io.; switching between tools is no longer necessary. You can also navigate from Jira to the Run Report to view a specific artifact.
+
+- **Video Capturing Artifacts** – in addition to saving screenshots, you can also save videos from tests (passed, failed, or all completed, regardless of the result). From Test Runner and Reporter, video files, like screenshots, are uploaded to S3 Storage and then displayed in the test management system in a user-friendly format, where they can be viewed or downloaded.
+
+- **Artifact S3 Support** – you can store [Test Artifacts](https://docs.testomat.io/test-reporting/artifacts/) in the cloud and choose the provider your company or CI\CD tool is comfortable working with: AWS, DigitalOcean, Azure, and Google Cloud.
+