updated articles by release

astro.config.mjs

@@ -387,6 +387,7 @@ export default defineConfig({
 								{ label: 'AI-Powered Features', link: '/advanced/ai-powered-features/ai-powered-features' },
 								{ label: 'AI-Requirements', link: '/advanced/ai-powered-features/ai-requirements' },
 								{ label: 'AI-Agents', link: '/advanced/ai-powered-features/ai-agents' },
+								{ label: 'AI Skills', link: '/advanced/ai-powered-features/ai-skills' },
 								{ label: 'Voice Mode', link: '/advanced/ai-powered-features/voice-mode' },
 							],
 						},
@@ -463,6 +464,7 @@ export default defineConfig({
 								{ label: 'Telegram', link: '/integrations/report-notifications/telegram' },
 								{ label: 'Jira', link: '/integrations/report-notifications/jira' },
 								{label: 'Azure DevOps', link: '/integrations/report-notifications/azure-devops'},
+								{ label: 'Webhook', link: '/integrations/report-notifications/webhook' },
 							],
 						},
 						{
@@ -506,6 +508,7 @@ export default defineConfig({
 								],
 							},
 							{ label: 'Administration', link: '/management/company/administration' },
+							{ label: 'Clone Project Settings', link: '/management/company/clone-project-settings' },
 							{ label: 'Audit Log', link: '/management/company/audit-log' },
 							{ label: 'Trials', link: '/management/company/trials' },
 							{ label: 'Subscriptions', link: '/management/company/subscriptions' },

src/content/docs/advanced/ai-powered-features/ai-agents.md

@@ -39,11 +39,38 @@ These powerful AI-features are available in the **Enterprise plan**.
 - **Summarizes functional areas** by mapping tests to key modules or features.
 - **Identifies missing, never-executed, or placeholder tests**.
 - **Highlights critical gaps** in business logic, security, and performance testing.
-- **Assesses release readiness** based on test data from the last 14 days.
+- **Assesses release readiness** based on the test history for the period you choose (14 days by default).
 - **Provides actionable recommendations** to close gaps and improve completeness.
 
 ![Deep Analyze](./images/Deep_analyze.gif)
 
+#### Launch Deep Analyze
+
+1. Open the **Tests** page.
+2. Click the **⋯** button in the top-right corner, the last one next to **Chat with Tests**.
+3. Select **AI Agents**.
+
+![The Tests page menu with AI Agents selected](./images/ai-agents-menu.png)
+
+4. In the **Agents** window, select **Deep Analyze** in the list on the left. Its parameters open on the right.
+5. Set the parameters, or keep the defaults.
+6. Click **Launch Agent**.
+
+![The Agents window with Deep Analyze selected and its parameters](./images/deep-analyze-parameters.png)
+
+| Parameter | What it does |
+| --- | --- |
+| **Period (days)** | How many days of test history to analyze. 14 by default, up to 365. |
+| **Scope to suite** | Analyzes only one folder or suite and everything inside it. |
+| **Filter by label** | Focuses on tests with this label or custom field. |
+| **Filter by milestone** | Focuses on tests assigned to this milestone. |
+| **Min tests in suite** | Skips suites with fewer tests than this number. 5 by default. |
+| **Additional instructions** | Tells the agent what to focus on, for example "Focus on payment flows and ignore onboarding tests". |
+
+If the agent already ran in the last day, Testomat.io offers to open that result first. Click **Launch Anyway** to start a new run.
+
+On a large project, the analysis can take a while. You can close the window and find the result later in **Insights**.
+
 ---
 
 ### 2. 🍿 Mark Flaky Tests

src/content/docs/advanced/ai-powered-features/ai-powered-features.md

@@ -104,7 +104,7 @@ This feature makes it easier to create comprehensive test suites.
 If you have at least one previously created test case, you can use this AI-feature to generate more test cases.
 
 1. Open Test Suite that already contains Test Cases.
-2. Click **'Extra menu'** button.
+2. Click **⋯** button.
 3. Select **'Suggest Tests'** option from the dropdown list.
 
 ![Testomat.io - AI-powered](./images/AI_8.gif)
@@ -119,7 +119,7 @@ Testomat.io recommends adding only the necessary tests cases to your suite!
 You can also use this AI feature to suggest tests based solely on the Suite Description.
 
 1. Open Test Suite with a description.
-2. Click **'Extra menu'** button.
+2. Click **⋯** button.
 3. Select **'Suggest Tests'** option from the dropdown list.
 
 ![Testomat.io - AI-powered](./images/AI_Suggest_tests_1.gif)
@@ -197,7 +197,7 @@ If you have a "draft" description that is messy or lacks detail, the AI rewrites
 **How to use this feature:**
 
 1. Open Test Case with you want to refine.
-2. Click **'Extra menu'** button on 'Description' tab.
+2. Click **⋯** button on 'Description' tab.
 3. Select **'Suggest Better Description'** option from the dropdown menu.
 
 ![Testomat.io - Suggest Better Test Case Description](./images/Suggest_Better_Description_1.png)
@@ -207,6 +207,26 @@ If you have a "draft" description that is messy or lacks detail, the AI rewrites
 
 ![Testomat.io - Suggest Better Test Case Description](./images/Suggest_Better_Description_2.png)
 
+## Generate a Description from a Screenshot
+
+Turn the screenshots attached to a test into steps, expected results, and test data. This works in Classical projects, and the test needs at least one image attachment.
+
+![The menu next to Improve Description with Generate from Screenshot selected](./images/generate-from-screenshot.png)
+
+1. Open the test and attach the screenshots.
+2. On the **Description** tab, click the **⋯** button next to **Improve Description** (or **Suggest Description**, if the test has no description yet).
+3. Select **Generate from Screenshot**.
+4. Review the result on the **Suggested Action** tab. To compare it with what the test has now, open **Current test**.
+5. Click **Update Test Description**.
+
+![The Generate description from screenshot window with the analyzed screenshots and the suggested description](./images/generate-from-screenshot-result.png)
+
+The new steps are added below your existing description, so nothing you wrote is lost. Want a different result? Type what to change in the **Follow up** field and click **Follow Up**. 
+
+The same option works for suites: click **Update Suite Description** at the end.
+
+AI reads up to three new images at a time, each up to 10 MB. Screenshots that are already in the description are skipped.
+
 ## Generate Test Case Description Based on Test Code
 
 Use AI to analyze your test code and produce detailed test descriptions. Bridges the gap between technical code and human-readable documentation, improving collaboration between technical and non-technical team members:
@@ -227,17 +247,6 @@ Test Summary is created:
 
 :::
 
-## Generate Code Based on Test Case Description
-
-Provide a test description, and the AI generates the corresponding test automation code. Please note that generated code may be not completely comprehensive.
-
-Code will be created based on the project framework settings and other tests in this suite.
-Use it as boilerplate code only.
-
-To check your Project framework settings go to Project Settings page:
-
-![Testomat.io - AI-powered](./images/Project_settings.png)
-
 ## Test Case & Code Quality Review
 
 The AI-powered **Quality Review** feature can be used for for both manual test descriptions and automated test code. It allows you to analyze your tests and provides intelligent feedback with actionable advice to improve clarity, structure, and adherence to best practices.
@@ -272,7 +281,7 @@ This feature evaluates the quality of a manual test’s description, suggesting
 
 1. Go to 'Tests'.
 2. Select the Test Case with description you want to review.
-3. On 'Description' tab, click **'Extra menu'** button.
+3. On 'Description' tab, click **⋯** button.
 4. Select **'Test Quality Review'** option from the dropdown list..
 
 ![Testomat.io - AI-powered](./images/Test_quality_review_1.gif)
@@ -283,7 +292,7 @@ This feature reviews your automated test code to detect potential issues, enhanc
 
 1. Go to 'Tests'.
 2. Select Test Case with the code that you want to review.
-3. On 'Code' tab, click **'Extra menu'** button.
+3. On 'Code' tab, click **⋯** button.
 4. Select **'Test Quality Review'** option from the dropdown list..
 
 ![Testomat.io - AI-powered](./images/Test_code_review_1.gif)
@@ -300,7 +309,7 @@ To use this feature:
 
 1. Go to 'Tests'.
 2. Select a Test Case that you want to check for duplicates.
-3. On 'Description' tab, click **'Extra menu'** button.
+3. On 'Description' tab, click **⋯** button.
 4. Select **'Find Duplicates'** option from the dropdown list..
 5. Click **'Remove'** button to delete the identified duplicate tests from your project.
 
@@ -389,7 +398,7 @@ Testomat.io allows you to use AI-powered feature to analyze and summarize your f
 
 1. Go to 'Tests'.
 2. Select the Suite that you want to analyze.
-3. Click **'Extra menu'** button on 'Summarize' button.
+3. Click **⋯** button on 'Summarize' button.
 4. Select **'Analyze Suite'** option from the dropdown menu.
 
 ![Testomat.io - AI-powered](./images/AI_Analyze_Suite_1.png)
@@ -475,7 +484,7 @@ Results generated by AI-features are automatically saved to the **'Insights'** s
 **Access the 'Insights' Section:**
 
 1. Go to 'Tests' page.
-2. Click **'Extra menu'** button in the header.
+2. Click **⋯** button in the header.
 3. Select **'Insights'** option from the dropdown menu.
 
 ![Testomat.io - Insights](./images/Insights_2.png)
@@ -514,7 +523,7 @@ With just a few clicks, you can generate a professional, shareable PDF version o
 **How to export AI-report:**
 
 1. Go to 'Tests' page.
-2. Click **'Extra menu'** button in the header.
+2. Click **⋯** button in the header.
 3. Select **'Insights'** option from the dropdown menu.
 
 ![Testomat.io - Insights](./images/Insights_2.png)
@@ -523,7 +532,7 @@ With just a few clicks, you can generate a professional, shareable PDF version o
 
 ![Testomat.io - Insights](./images/Insights_5.png)
 
-5. Click **'Extra menu'** button within the report view.
+5. Click **⋯** button within the report view.
 6. Select **'Export as PDF'** from the dropdown menu.
 
 ![Testomat.io - Insights](./images/Insights_6.png)

src/content/docs/advanced/ai-powered-features/ai-requirements.md

@@ -16,7 +16,7 @@ Testomat.io introduces another AI-powered feature - **AI-Requirements** that hel
 
 A dedicated **'Requirements'** page brings all your requirements into a single, convenient workspace, where you can view, organize, and update all requirements in one place, eliminating the need to jump between different parts of a project.
 
-When you add a **Requirement source** (Jira issue, Confluence page, PDF file, etc.) in Testomat.io, the system analyzes the description and automatically generates a structured requirement summary. You can also view all suites linked to a requirement, the original source, and any added attachments directly from the 'Requirement details' page.
+When you add a **Requirement source** (Jira issue, Confluence page, Linear issue, PDF file, etc.) in Testomat.io, the system analyzes the description and automatically generates a structured requirement summary. You can also view all suites linked to a requirement, the original source, and any added attachments directly from the 'Requirement details' page.
 
 ![Testomat.io - AI-powered](./images/Requirement_page_details_1.gif)
 
@@ -69,7 +69,7 @@ You can enbable AI at any time on Company Settings page by following the instruc
 
 You can add requirements to a new project to drive test generation from the start.
 
-Once a project is created (BDD or Classical), set up the integration for your **Requirement Source** (see detailed instructions for [JIRA](https://docs.testomat.io/integrations/issues-management/jira/#connecting-to-jira-project) and [Confluence](https://docs.testomat.io/integrations/issues-management/confluence)). Then, proceed with adding requirements:
+Once a project is created (BDD or Classical), set up the integration for your **Requirement Source** (see detailed instructions for [JIRA](https://docs.testomat.io/integrations/issues-management/jira/#connecting-to-jira-project), [Confluence](https://docs.testomat.io/integrations/issues-management/confluence), and [Linear](https://docs.testomat.io/integrations/issues-management/linear)). Then, proceed with adding requirements:
 
 1. Open **'Requirements'** page.
 2. Click **'+New Requirements'** or **'+Add Requirement'** button.
@@ -162,6 +162,19 @@ Access **'Requirements'** page via **'Extra menu'** button on **'Tests'** page.
 
 ![Testomat.io - Confluence](./images/Confluence_Req_1.gif)
 
+## Linear as a Requirement Source
+
+Use a Linear issue as a requirement and build tests from it. First connect Linear to your project, see [Linear](https://docs.testomat.io/integrations/issues-management/linear).
+
+1. Go to the **'Requirements'** page.
+2. Click **'+ New'** and select **'New Linear requirement'**.
+3. Paste the Linear issue key, such as `ENG-123`, or its URL into **'Issue ID'**.
+4. Click **'Save'**.
+
+Testomat.io imports the issue title and description, and AI writes a summary of the requirement. From here, link an existing suite or let AI generate one.
+
+Linear requirements refresh once a day. To get the latest version right away, use [Refresh the Requirement](#refresh-the-requirement).
+
 ## Files & Text as a Requirement Source
 
 Testomat.io allows you to use not only Jira or Confluence as a Requirement Source, but also add text files, docs, spreadsheets or even screenshots and images.

src/content/docs/advanced/ai-powered-features/ai-skills.md

@@ -0,0 +1,76 @@
+---
+title: AI Skills
+description: Install Testomat.io AI Skills for Claude Code, Cursor, and Copilot. Each skill teaches your coding agent one testing workflow, from writing test cases to syncing them back to Testomat.io.
+type: article
+url: https://docs.testomat.io/advanced/ai-powered-features/ai-skills
+head:
+  - tag: meta
+    attrs:
+      name: keywords
+      content: Testomat.io, AI Skills, Claude Code, Cursor, Copilot, coding agent, skills CLI, test cases, QA workflow
+---
+
+Teach your coding agent how to test. Each AI Skill covers one testing workflow, such as writing test cases or finding duplicates. 
+
+**Before You Start**
+
+- Company should be on the Enterprise plan.
+- Use a coding agent such as Claude Code, Cursor, or Copilot.
+- Install Node.js is installed.
+
+## Open AI Skills
+
+1. Open the **Tests** page.
+2. Click the **⋯** button in the top-right corner, next to **Chat with Tests**.
+3. Select **AI Skills**. You'll find it in the AI group of the menu, below **AI Agents** and **MCP Server**.
+
+![The Tests page menu with AI Skills below AI Agents and MCP Server](./images/ai-skills-menu.png)
+
+The **Testomat.io AI Skills** panel opens on the right.
+
+:::note
+
+AI Skills are available on the Enterprise plan. On other plans, **AI Skills** is greyed out in the menu. See [Plan Features Comparison](https://docs.testomat.io/management/company/plan-features-comparison).
+
+:::
+
+## Install the Skills
+
+1. In the **Install** section, click the copy icon next to the install command.
+2. Run the command in your project:
+
+```bash
+npx skills add testomatio/skills
+```
+
+3. Pick the skills you want in the menu, and choose whether to install them for this project or for all projects.
+
+![The Testomat.io AI Skills panel with the install command and the list of skills](./images/ai-skills-page.png)
+
+Your agent now has the skills. Describe a task, for example "write test cases for the login page", and it uses the matching skill.
+
+## Update the Skills
+
+Run this command to get the latest version of the skills you installed:
+
+```bash
+npx skills update
+```
+
+## Available Skills
+
+| Skill | What it does |
+| --- | --- |
+| `qa-write-test-cases` | Writes test cases and checklists from requirements, tickets, or feature descriptions. |
+| `qa-thinking` | Looks at a feature the way a tester does: edge cases, negative flows, and unobvious scenarios. |
+| `qa-explain-behavior` | Answers questions about how the product behaves. |
+| `improve-test-cases` | Makes existing Markdown test cases clearer. |
+| `detect-duplicate-test-cases` | Finds duplicates, near-duplicates, and overlaps. |
+| `sync-test-cases-with-tms` | Syncs Markdown test cases between your project and Testomat.io. |
+
+For the full catalog and setup for each agent, see [testomat.ai/qa-skills](https://testomat.ai/qa-skills).
+
+## Next Steps
+
+- [MCP - Connect with a Config File](https://docs.testomat.io/tutorials/mcp-connection)
+- [AI-Powered Features](https://docs.testomat.io/advanced/ai-powered-features)

src/content/docs/advanced/api-access/index.md

@@ -112,6 +112,10 @@ GET /api/{project_id}/testruns?run_id={run_id}
 ## Public API v2
 
 Public API v2 uses the same request and response shape for every endpoint. That makes it easier to write an integration and easier for an AI agent to use. It supports requests to a branch, grouped counts, run statistics, analytics, and pagination. For additional information see [Testomat.io API Reference](https://app.testomat.io/docs/openapi).
+
+Public API v2 also lets you import suites from a CSV, XLS, or XLSX file, share tests and suites in bulk by their IDs or labels, and create and update milestones.
+
+Run responses also include when a run was launched and finished, and the test runs list can return the test version and description for each result.
 
 ### Testomat.io MCP Server v2.0
 

src/content/docs/advanced/milestones/index.md

@@ -63,6 +63,8 @@ Milestones are automatically grouped by type name in a case-insensitive manner.
 
 :::
 
+You can also create and update milestones through Public API v2. A milestone created this way belongs to that project only. See the [API Reference](https://app.testomat.io/docs/public-api#tag/milestones).
+
 ## Milestone types
 
 Milestones are grouped by type. Testomat.io ships with built-in types - **Milestone**, **Release**, and **Sprint** - and you can add your own.

src/content/docs/advanced/tql/index.md

@@ -153,6 +153,20 @@ By using the `in` operator, you reduce the risk of syntax errors (like missing a
 
 :::
 
+### Write a Query in Plain Words
+
+With AI features turned on, describe what you need and AI writes the query for you. The editor shows the hint "Enter your request as a text and AI will generate the query." It works in the query editors on the **Tests** and **Runs** pages.
+
+1. Click the **Query Language Editor** button next to the search field.
+2. Type your request, for example `manual runs that finished and have defects`.
+3. Click **Apply**.
+
+![The Tests Query Editor with a plain-language request and the AI Apply button](./images/tql-ai-query.png)
+
+AI turns your request into TQL and filters the list. If you type TQL yourself, it's used as is.
+
+If AI can't build a query, make the request more specific or write the TQL directly.
+
 ## Tests Variables
 
 In previous section we used `tag` in the query. `tag` is an allowed query variable. Here is a comprehenisve list of variables you can use in the query:

src/content/docs/getting-started/index.md

@@ -57,6 +57,10 @@ Use [Classical Project](https://docs.testomat.io/project/tests/classical-test-ca
 
 You have just created your first project! 
 
+Your new project appears on the **Dashboard** with your other projects. Each project card shows its avatar, test count, and project type, so you can find the one you need at a glance.
+
+![The Dashboard with project cards, each showing the project avatar, test count, and project type](./images/dashboard-projects.png)
+
 Now you can start creating suites and test cases for your projects.
 
 ## Create a Suite

src/content/docs/integrations/continuous-integration/index.mdx

@@ -51,6 +51,12 @@ CI configuration has 3 steps:
 
 Follow the guide for a corresponding CI to set it up.
 
+:::tip
+
+Before you save a CI connection, click **Test Connection** to check the values you entered. 
+
+:::
+
 :::note
 
 Please ensure that Testomat.io IP addresses are allowed to access your CI environment: 142.132.185.19, 5.75.250.20