testeiya 0.2.1 → 0.3.1-0.1

package/skills/testeiya/testomatio-docs/docs/tutorials/Set-Up-Read-Only-Access.md

@@ -1,85 +0,0 @@
----
-title: Set Up Read-Only Access
-description: Learn how to give stakeholders a view-only look at your testing in Testomat.io. This guide walks you through inviting an external user with the Read-Only role, adding them to the right project, and sharing a run report or living documentation by link when they need no account at all.
-type: article
-url: https://docs.testomat.io/tutorials/set-up-read-only-access
-head:
-  - tag: meta
-    attrs:
-      name: og:image
-      content: https://docs.testomat.io/_astro/New_b1BS3EKN_2024-08-29.DGrFkMLR_ZOOgn1.webp
-
-  - tag: meta
-    attrs:
-      name: keywords
-      content: read-only access, Testomat.io, Read-Only user, user roles, permissions, invite users, external stakeholders, clients, auditors, project access, public reports, share report publicly, living documentation, view-only, test management, QA
----
-
-Welcome! 
-
-This tutorial shows you how to give someone outside your team a safe, look-but-don't-touch view of your testing. That could be a client, an auditor, or a stakeholder who wants to follow progress without the risk of changing anything.
-
-You have two ways to do this, and this tutorial covers both: add the person as a Read-only user, or share a single report or living documentation with them without an account at all.
-
-## Which option to pick
-
-![Testomat.io user access options chart](./images/read-only-access/read-only-access-options.png)
-
-* **Read-only user**. Best when the person needs ongoing access to browse tests, runs, and reports themselves. They log in but cannot change anything. It is free of charge on Professional and Enterprise plans.
-* **Public share**. Best for a one-off. You send a link to a report or living docs, and they need no Testomat.io account at all.
-
-## Invite an external user as Read-only
-
-Users are managed at the Company level, so you invite them there first.
-
-1. Open the **Companies** page and select your company.
-2. Invite the user by email.
-3. Assign the **Read-Only** role.
-
-![The company user invite with the Read-Only role selected](./images/read-only-access/1-invite-read-only.png)
-
-:::note
-
-Read-only members can view information but cannot make any changes. See [Users and Access](https://docs.testomat.io/management/company/users-and-permissions/#_top) for what every role can do.
-
-:::
-
-## Add them to the right project
-
-A company can hold several projects, so give the person access only to the one they need.
-
-1. Open the project you want to share.
-2. Go to **Settings**, then **Users**.
-3. Click **Invite**.
-4. Select the Read-only user and click **Send** to invite them to the project.
-
-![Adding the Read-only user to a project under Settings, Users](./images/read-only-access/2-invite-user-to-project.png)
-
-They can now sign in and browse that project, but every edit and run control stays locked for them.
-
-## Or share without an account
-
-If the person only needs to see one report or your living docs, skip the account and send a link.
-
-To share a run report:
-
-1. Open the run and click **Report**.
-2. Click the actions menu (`...`).
-3. Choose **Share Report by Email** to send it to specific people, or **Share Report Publicly** to create a link.
-4. For a public link, set an expiration date the default is 7 days, and keep the passcode on for security.
-
-![The Share Report Publicly options with expiration date and passcode](./images/read-only-access/3-share-report-publicly.png)
-
-:::note
-
-Public sharing is a two-level switch. Turn it on at the **Company** level first, then in **Project Settings** under the **Sharing** section, or the option stays greyed out. 
-
-:::
-
-To share living documentation, open it from the project and send its link the same way. This gives stakeholders an always-current view of what your tests cover, with no login.
-
-## Next steps
-
-* Review what each role can do in [Users and Access](https://docs.testomat.io/management/company/users-and-permissions/#_top).
-* Want stakeholders to follow coverage live? Share your [Living Documentation](https://docs.testomat.io/advanced/living-doc/#_top).
-* Want to present particular results? Send a [run report](https://docs.testomat.io/project/runs/reports/#how-to-share-run-report).

package/skills/testeiya/testomatio-docs/docs/tutorials/Using-AI-in-Testing.md

@@ -1,163 +0,0 @@
----
-title: Using AI in Testing
-description: Learn how to use AI across a full testing cycle in Testomat.io. This guide walks you through enabling AI, connecting a custom AI provider, adding a requirement, generating tests and descriptions from it, analyzing a run, and chatting with your analytics.
-type: article
-url: https://docs.testomat.io/tutorials/using-ai-in-testing
-head:
-  - tag: meta
-    attrs:
-      name: og:image
-      content: https://docs.testomat.io/_astro/New_b1BS3EKN_2024-08-29.DGrFkMLR_ZOOgn1.webp
-
-  - tag: meta
-    attrs:
-      name: keywords
-      content: AI in testing, Testomat.io, AI-powered features, AI Agents, AI requirements, generate tests from requirements, suggest test case description, custom AI provider, clusterize errors, analyze failed tests, chat with analytics, test coverage, test design, test management, software testing, QA
----
-
-Welcome! 
-
-This tutorial turns on Testomat.io's AI features and walks them through a full testing cycle: you start from a requirement, generate tests from it, describe them, then analyze the run and question your analytics. AI here is a helper that saves you typing and digging, not a replacement for your judgment.
-
-![Testomat.io AI capabilities chart](./images/working-with-ai/ai-capabilities.png)
-
-What you will do:
-
-1. Enable AI for your company.
-2. Add a requirement to your project.
-3. Generate tests from the requirement.
-4. Generate a test description.
-5. Analyze a run with AI.
-6. Chat with Analytics.
-
-## Before you start
-
-AI features are off by default. A Company Owner turns them on, and only your company's chosen AI provider sees the content you send.
-
-:::note
-
-Only enable AI if your test data is not sensitive. The AI provider processes the text you send it, so check your data privacy rules first.
-
-:::
-
-## Enable AI
-
-To integrate and begin working with AI features in your Testomat.io account, follow these steps:
-
-1. Open **Company Settings**.
-2. Go to the **Administration** section.
-3. Turn on the **AI Features**.
-
-![The AI toggle in Company Settings under Administration](./images/working-with-ai/1-ai-features-settings.png)
-
-Once enabled, the AI actions appear across your project. See [AI settings](https://docs.testomat.io/management/company/administration/#ai) for the details.
-
-### Use your own AI provider
-
-If your company prefers an AI provider it already trusts, Testomat.io can connect to a third-party service such as OpenAI, Anthropic, and others. You keep all the same AI features while choosing the provider that fits your security and compliance rules.
-
-1. In the AI settings, turn on the **Custom AI Provider** option.
-2. Select a provider from the dropdown.
-3. Enter the **API Key**.
-4. Enter the **Model** name.
-5. Enter **Max Tokens**, if your provider requires it.
-6. Click **Save Settings**.
-
-![The AI provider settings with a custom provider selected](./images/working-with-ai/2-custom-provider.png)
-
-:::note
-
-Once a custom provider is connected, every AI request runs through it. Testomat.io does not fall back to a shared provider — if your provider is unavailable, the request fails and you are notified. See [Custom AI Provider](https://docs.testomat.io/management/company/administration/#custom-ai-provider) for the full reference.
-
-:::
-
-## Add a requirement
-
-Requirements are what your tests exist to cover, so the cycle starts here. Link one to your project and AI can generate tests from it.
-
-First, set up the integration for your requirement source. See [Jira](https://docs.testomat.io/integrations/issues-management/jira/#connecting-to-jira-project) or [Confluence](https://docs.testomat.io/integrations/issues-management/confluence) for the steps. Then add the requirement:
-
-1. Open the **Requirements** page.
-2. Click **+ New Requirements** or **+ Add Requirement**.
-3. Select your requirement source, for example Jira.
-4. Enter the source identifier, such as the **Jira Issue ID**.
-5. Click **Save**.
-
-![The Requirements page with a new requirement being added from Jira](./images/working-with-ai/3-add-requirement.png)
-
-:::note
-
-You can add a requirement to an ongoing project at any time using the same steps. See [AI-Requirements](https://docs.testomat.io/advanced/ai-powered-features/ai-requirements/) for other sources, including files and plain text.
-
-:::
-
-## Generate tests from the requirement
-
-With the requirement linked, AI reads it and proposes the test cases that cover it, so you start from a draft instead of a blank suite.
-
-1. Open the **Requirements** page and click your requirement.
-2. On the **Summary** tab, click **Analyze Requirement**.
-3. Click **Add tests to {Suite_name} Suite**.
-4. Review the suggested cases and click **Add** on the ones you want.
-
-![The suggested test cases generated from a requirement](./images/working-with-ai/4-generate-tests-from-requirement.png)
-
-Click **Suggest More Tests** if you need extra cases, and double-click any suggested title to edit it before adding.
-
-:::note
-
-Nothing is added automatically. You always choose which cases to keep.
-
-:::
-
-## Generate a test description
-
-A test name tells you what to check, but not how. AI writes the description from the name, or improves the one you already have.
-
-1. Open a test case.
-2. Click **Suggest Description**.
-3. Review the result, edit it if needed, then save.
-
-![The AI-generated description on a test case](./images/working-with-ai/5-suggest-description.png)
-
-:::note
-
-This works the same way in BDD projects. On the **Scenario description** tab, click **Suggest Description** and AI turns your Given/When/Then steps into a readable overview.
-
-:::
-
-## Analyze a run with AI
-
-Once your tests have run, AI groups the failures so you read a handful of causes instead of a wall of errors.
-
-1. Go to the **Runs** page.
-2. Open a finished automated run.
-3. Click **Clusterize Errors**.
-
-:::note
-
-**Clusterize Errors** appears only on finished automated runs with 5 or more failures.
-
-:::
-
-## Chat with Analytics
-
-Analytics answers questions you already know to ask. Chat with Analytics lets you ask in plain language instead of hunting through dashboards.
-
-1. Go to the **Analytics** page.
-2. Open **Chat with Analytics**.
-3. Ask your question and send it.
-
-Ask things like which tests are most unstable, which areas fail most often, or how execution trends changed over time.
-
-:::note
-
-Metrics are calculated over a 30-day window unless you specify a different range.
-
-:::
-
-## Next steps
-
-* Want to expand your AI capabilities? Try setting up [AI Agents](https://docs.testomat.io/advanced/ai-powered-features/ai-agents/).
-* See every generative feature across suites, tests, and code in [AI-Powered Features](https://docs.testomat.io/advanced/ai-powered-features/ai-powered-features/).
-* Drive your test design from product requirements with [AI-Requirements](https://docs.testomat.io/advanced/ai-powered-features/ai-requirements/).

package/skills/testeiya/testomatio-docs/docs/tutorials/Working-with-Jira.md

@@ -1,125 +0,0 @@
----
-title: Working with Jira
-description: Learn how to work with Jira in Testomat.io. This guide walks you through connecting your project to Jira, linking tests, suites, and plans to Jira issues, creating issues from failed tests, running tests directly from Jira, attaching reports, and tracking coverage with the traceability matrix.
-type: article
-url: https://docs.testomat.io/tutorials/working-with-jira
-head:
-  - tag: meta
-    attrs:
-      name: og:image
-      content: https://docs.testomat.io/_astro/New_b1BS3EKN_2024-08-29.DGrFkMLR_ZOOgn1.webp
-
-  - tag: meta
-    attrs:
-      name: keywords
-      content: Jira, Testomat.io, Jira plugin, Jira integration, test management, link tests to issues, Jira issues, defects, bug tracking, traceability matrix, test runs in Jira, test reports, sprints, QA
----
-
-Welcome! 
-
-This tutorial connects Testomat.io to Jira and walks you through the everyday flow: link a test to a Jira issue, report a defect from a run, and see testing status back in Jira. Once this is set up, tests and Jira issues stay tied together, so the team can see what is tested and what is failing.
-
-![Jira - Testomat.io integration flow](./images/working-with-jira/testomatio-jira-flow.png)
-
-What you will do:
-
-1. Connect your Jira project.
-2. Link a test to a Jira issue.
-3. Report a defect from a run.
-4. See the status synced back in Jira.
-
-## Before you start
-
-Make sure you have:
-
-* Jira profile access, with administrator rights in the Jira workspace.
-* A Manager or Owner role in your Testomat.io project.
-* The [Testomat.io Jira Plugin](https://docs.testomat.io/advanced/jira-plugin/) is installed in Jira.
-
-:::note
-
-Connecting requires Jira admin rights. The person who sets up the integration in Project Settings must have them, or the project cannot be connected. See [Integrations](https://docs.testomat.io/integrations/issues-management/jira) for the full reference.
-
-:::
-
-## Connect your Jira project
-
-1. In your Testomat.io project, open **Settings** in the sidebar.
-2. Click **Jira Integration**.
-3. Click **Add Jira project**.
-4. In the **New Jira project** panel, select the connection type and enter the details.
-
-![Jira Integration settings with the Add Jira project button](./images/working-with-jira/1-new-jira-project.png)
-
-Pick the connection type based on who should see testing data in Jira:
-
-| The account type | Tests and results are visible to |
-|---|---|
-| **Administrator account** | Linked tests and results are visible to all Jira users through the plugin, while editing and running still require a Testomat.io login.<br><br>Use this if you want everyone in Jira to see coverage. |
-| **Regular account** | Linked tests and results are visible only to logged-in Testomat.io users.<br><br>Use this if you need to restrict access. |
-
-Once saved, your Jira project is connected and ready.
-
-## Link a test to a Jira issue
-
-Linking ties a test to the story or bug it covers, so coverage shows on both sides.
-
-1. Select the test, or several tests, on the Tests page.
-2. Click **Link**.
-3. Type in the Jira issue to link them to.
-
-![The Link to Issue button and the Jira issue picker](./images/working-with-jira/2-link-to-issue.png)
-
-The link now appears on both the test and the Jira issue. You can also link a test to the Jira issue by hovering over the test and clicking the link icon.
-
-:::note
-
-You can also link tests from inside Jira. The [Jira Plugin](https://docs.testomat.io/advanced/jira-plugin/) lets you link and unlink tests, suites, and plans to an issue without leaving Jira.
-
-:::
-
-## Report a defect from a run
-
-When a test fails during a run, you can create a Jira bug without leaving Testomat.io.
-
-1. In the run, open the failed test.
-2. Choose to report a defect and enter the Jira issue link.
-3. If needed, you can create a new issue and link the defect to it:
-    1. Click **Create new issue**.
-    2. Select **Jira profile** and **Jira Issue type**.
-    3. Enter the issue **Title** and **Description**.
-
-![Create new Jira issue in Testomat.io](./images/working-with-jira/3-link-defect.png)
-
-4. Click **Create Jira issue**. The new issue has been created in Jira and linked to the test.
-
-![Reporting a defect to Jira from a failed test in a run](./images/working-with-jira/4-create-new-issue.png)
-
-:::note
-
-To prefill the bug summary and description, set up a Defect template first. See [Templates](https://docs.testomat.io/management/project/templates/#applying-templates-to-defects).
-
-:::
-
-## See the status synced back in Jira
-
-With the plugin in place, your Jira issues show the linked tests and their latest results, so a product owner can open an issue and see whether it passed or failed.
-
-1. Open the linked issue in Jira.
-2. View the Testomat.io panel to see linked tests, coverage, and the latest run status.
-
-![Testomat.io panel inside a Jira issue showing linked tests and status](./images/working-with-jira/5-jira-issue-w-testomatio-panel.png)
-
-With the [Jira Plugin](https://docs.testomat.io/advanced/jira-plugin/) in place, your Jira issues show the linked tests and their latest results, so a product owner can open an issue and see whether it passed or failed.
-
-If something looks out of date, use [Synchronize with Jira](https://docs.testomat.io/integrations/issues-management/jira/#how-to-connect-to-jira-project) from the integration to refresh the link.
-
-The link between the test and the Jira issue can be viewed in the run next to the reported defect.
-
-![Run view with the defect reported in Jira](./images/working-with-jira/6-test-connected-to-jira.png)
-
-## Next steps
-
-* Want cleaner bug reports? Set up a [Defect](https://docs.testomat.io/management/project/templates/#applying-templates-to-defects) template in Templates.
-* Setting up other tools? See [Integrations](https://docs.testomat.io/integrations/issues-management/).
-* Working mostly inside Jira? See the [Jira Plugin](https://docs.testomat.io/advanced/jira-plugin/) for running tests and managing suites without leaving Jira.