diff --git a/src/left-nav-title.json b/src/left-nav-title.json index 2fbbbef0..639377db 100644 --- a/src/left-nav-title.json +++ b/src/left-nav-title.json @@ -453,9 +453,6 @@ "youtrack": { "/docs/integrations/bug-reporting/youtrack/": "Youtrack" }, - "zepel": { - "/docs/integrations/bug-reporting/zepel/": "Zepel" - }, "browserstack": { "/docs/integrations/test-labs/browserstack/": "BrowserStack" }, @@ -476,9 +473,6 @@ }, "trello": { "/docs/integrations/test-management/trello/": "Trello" - }, - "freshrelease": { - "/docs/integrations/test-management/freshrelease/": "Freshrelease" }, "clickup": { "/docs/integrations/test-management/clickup/": "Clickup" diff --git a/src/pages/docs/FAQs/web-apps/how-to-enable-ie-mode-in-microsoft-edge.md b/src/pages/docs/FAQs/web-apps/how-to-enable-ie-mode-in-microsoft-edge.md index 5395ff73..89d1eecb 100644 --- a/src/pages/docs/FAQs/web-apps/how-to-enable-ie-mode-in-microsoft-edge.md +++ b/src/pages/docs/FAQs/web-apps/how-to-enable-ie-mode-in-microsoft-edge.md @@ -77,9 +77,9 @@ IE mode may hang if Protected Mode settings are inconsistent across Windows secu | Key | Data Type | Value | | --- | --- | --- | - | ts.ieMode | String | true | + | ts.ieMode | Boolean | true | -  +  7. Click **Create Profile** to save the configuration. diff --git a/src/pages/docs/atto/generative-ai/overview.md b/src/pages/docs/atto/generative-ai/overview.md index 70cdc551..ad24f10c 100644 --- a/src/pages/docs/atto/generative-ai/overview.md +++ b/src/pages/docs/atto/generative-ai/overview.md @@ -31,7 +31,7 @@ Testsigma's Generative AI capabilities streamline and accelerate test creation With Testsigma Copilot, you can generate test cases in real-time using simple prompts. Copilot is embedded within Web, Mobile, and Live Editor, making it easy to quickly create, edit, and extend test cases. -Testsigma also integrates seamlessly with tools like Jira, Figma, Xray, GitHub, and qTest, enabling test generation directly from user stories, design, and requirements. +Testsigma also integrates seamlessly with tools like Jira, Figma, Xray, and qTest, enabling test generation directly from user stories, design, and requirements. diff --git a/src/pages/docs/integrations/bug-reporting/bugzilla.md b/src/pages/docs/integrations/bug-reporting/bugzilla.md index 0bed8e45..0dcc2840 100644 --- a/src/pages/docs/integrations/bug-reporting/bugzilla.md +++ b/src/pages/docs/integrations/bug-reporting/bugzilla.md @@ -40,15 +40,13 @@ Testsigma Mantis integration lets you create issues directly from the Testsigma ## **Integrating Bugzilla with Testsigma** 1. Navigate to **Settings > Integrations**. - - +  2. Enable toggle on **Bugzilla** widget. - - +  3. On the **Bugzilla details** prompt, **Account URL**, **API Key** and click on **Save & Enable**. - +  --- @@ -58,24 +56,20 @@ Testsigma Mantis integration lets you create issues directly from the Testsigma 1. Navigate to **Run Results > Test Case Result**, where you want to add a bug. - - +  2. Click on **Report Bug**. - - +  -3. Choose **Bugzilla** and enter details of the bug. +3. On the **Report** overlay, click the **Bugzilla** icon. +  -[[info | NOTE:]] -| - Only the bug reporting tools that have been enabled via the plugins page (add link) will be displayed here. -| - If you want to link to an existing issue on Bugzilla, click on the **Link to Issue** button, search for an existing issue in the search field, and click on **Link Issue** to add a link to an existing Issue on Bugzilla. Otherwise, enter the bug details in the form as required. - -4. Click on **Create Ticket**. +4. On the **Report** overlay, click **Report Bug**. +  -When the bug is created, some additional details regarding the test result, such as the test execution video and step screenshots, are automatically added to the issue on Bugzilla by Testsigma. This helps the developer who checks the issue in Bugzilla better understand the issue/bug with more context. - - +[[info | **NOTE**:]] +| - If you want to link to an existing issue on **Bugzilla**, click on the **Link to Issue** button, search for a current issue in the search field, and click on Link Issue to add a link to an existing Issue on **Bugzilla**. Otherwise, enter the bug details in the form as required. +| - When the bug is created, some additional details regarding the Test Result, such as the test execution video and step screenshots, are added automatically by Testsigma. This helps the developer who checks the issue in **Bugzilla** better understand the issue/bug with more context. --- \ No newline at end of file diff --git a/src/pages/docs/integrations/bug-reporting/mantis.md b/src/pages/docs/integrations/bug-reporting/mantis.md index e29a4c75..a584c918 100644 --- a/src/pages/docs/integrations/bug-reporting/mantis.md +++ b/src/pages/docs/integrations/bug-reporting/mantis.md @@ -40,14 +40,13 @@ Testsigma Mantis integration lets you create issues in Mantis directly from the ## **Integrating Mantis with Testsigma** 1. Navigate to **Settings > Integrations**. - - +  2. Enable toggle on **Mantis** widget. - +  3. On the **Mantis Bug Tracker details** prompt, **Account URL**, **API Key** and click on **Save & Enable**. - +  --- @@ -55,26 +54,19 @@ Testsigma Mantis integration lets you create issues in Mantis directly from the ## **Creating a Bug** 1. Navigate to **Run Results > Test Case Result**, where you want to add a bug. - - +  2. Click on **Report Bug**. - - - -3. Choose **Mantis** and enter the detailed information of your bug. - - - -[[info | NOTE:]] -| - Only the bug reporting tools that have been enabled via the plugins page (add link) will be displayed here. -| - If you want to link to an existing issue on Mantis, click on the **Link to Issue** button, search for an existing issue in the search field, and click on **Link Issue** to add a link to an existing Issue on Mantis. Otherwise, enter the bug details in the form as required. - -4. Click on **Create Ticket**. - +  -When the bug is created, some additional details regarding the test result, such as the test execution video and step screenshots, are automatically added to the issue on Mantis by Testsigma. This helps the developer who checks the issue in Mantis better understand the issue/bug with more context. +3. On the **Report** overlay, click the **Mantis** icon. +  +4. On the **Report** overlay, click **Report Bug**. +  +[[info | **NOTE**:]] +| - If you want to link to an existing issue on **Mantis**, click on the **Link to Issue** button, search for a current issue in the search field, and click on Link Issue to add a link to an existing Issue on **Mantis**. Otherwise, enter the bug details in the form as required. +| - When the bug is created, some additional details regarding the Test Result, such as the test execution video and step screenshots, are added automatically by Testsigma. This helps the developer who checks the issue in **Mantis** better understand the issue/bug with more context. --- \ No newline at end of file diff --git a/src/pages/docs/integrations/bug-reporting/zepel.md b/src/pages/docs/integrations/bug-reporting/zepel.md deleted file mode 100644 index a4411f55..00000000 --- a/src/pages/docs/integrations/bug-reporting/zepel.md +++ /dev/null @@ -1,87 +0,0 @@ ---- -title: "Zepel Bug Reporting Integration" -page_title: "Zepel Bug Reporting Integration in Testsigma" -metadesc: "How to integrate Testsigma with Zepel for real-time bug reporting during Test Runs | Push bugs directly from Testsigma to your Zepel's project" -noindex: false -order: 17.36 -page_id: "zepel-bug-reporting-integration" -warning: false -contextual_links: -- type: section - name: "Contents" -- type: link - name: "Prerequisites" - url: "#prerequisites" -- type: link - name: "Integrating Zepel with Testsigma" - url: "#integrating-zepel-with-testsigma" -- type: link - name: "Creating a Bug" - url: "#creating-a-bug" ---- - ---- - -With Testsigma Zepel integration, you can push bugs directly from Testsigma to your Zepel project, capture screenshots, annotate bugs, and share them with your teammates. - -In this document, we will discuss how to establish Integration with Zepel from your Testsigma account and create the first bug from Testsigma that can flow into Zepel. - ---- - ->
Prerequisites
-> -> Before you begin, ensure that: -> 1. To integrate Zepel with Testsigma, we need the following information from your Zepel account: -> - Account URL. -> - API Key (For more information, refer to creating your Zepel API token). -> 2. You have referred to the documentation on creating test plan runs and results. - ---- - -## **Integrating Zepel with Testsigma** - -1. Navigate to **Settings > Integrations**. - - - -2. Enable toggle on **Zepel** widget. - - -3. On the **Zepel details** prompt, **Account URL**, **API Key** and click on **Save & Enable**. - - - - ---- - - -## **Creating a Bug** - -1. Navigate to **Run Results > Test Case Result**, where you want to add a bug. - - - -2. Click on **Report Bug**. - - - -3. Choose **Zepel** and enter information about your bug. - - - -[[info | NOTE:]] -| Only the bug reporting tools that have been enabled via the plugins page (add link) will be displayed here. - -If you want to link to an existing issue on Zepel, click on the **Link to Issue** button, search for an existing issue in the search field, and click on Link Issue to add a link to an existing Issue on Zepel. Otherwise, enter the bug details in the form as required. - -4. Click on **Create Ticket**. - - - -When the bug is created, some additional details regarding the test result, such as the test execution video and step screenshots, are automatically added to the issue on Zepel by Testsigma. This helps the developer who checks the issue in Zepel better understand the issue/bug with more context. - - - - - ---- \ No newline at end of file diff --git a/src/pages/docs/integrations/collaboration/microsoft-teams.md b/src/pages/docs/integrations/collaboration/microsoft-teams.md index 4b20ed1c..91223b4b 100644 --- a/src/pages/docs/integrations/collaboration/microsoft-teams.md +++ b/src/pages/docs/integrations/collaboration/microsoft-teams.md @@ -36,15 +36,13 @@ Integrating Testsigma with Microsoft Teams is similar to integrating with other 1. Navigate to **Settings > Integrations**. - - +  2. Enable toggle on **MS Teams** widget. - - +  3. On the **MS Teams details** prompt, enter **Name**, **Connector URL** and click on **Save & Enable**. - +  --- @@ -56,26 +54,18 @@ Once the MS Teams integration is added, you can enable the MS Teams notification 1. On **Create Test Plan/Edit Test Plan** page, click on **Test Plan Settings**. - - +  2. Enable **Send Notification** toggle. - - + 3. Under the **Notify On** section, select the status for which you want to be notified. You can select multiple statuses from the list. - - + 4. Under the **Also send messages to** dropdown, select **MS Teams**. - - - + Here’s what the notification looks like on MS Teams:  - - - --- \ No newline at end of file diff --git a/src/pages/docs/integrations/overview.md b/src/pages/docs/integrations/overview.md index fd2d7a04..3137f909 100644 --- a/src/pages/docs/integrations/overview.md +++ b/src/pages/docs/integrations/overview.md @@ -34,7 +34,6 @@ Testsigma integrates with various tools in your software delivery cycle to make * [Documentation on integrating Testsigma with Backlog](https://testsigma.com/docs/integrations/bug-reporting/backlog/) * [Documentation on integrating Testsigma with Mantis](https://testsigma.com/docs/integrations/bug-reporting/mantis/) * [Documentation on integrating Testsigma with Youtrack](https://testsigma.com/docs/integrations/bug-reporting/youtrack/) - * [Documentation on integrating Testsigma with Zepel](https://testsigma.com/docs/integrations/bug-reporting/zepel/) * [Documentation on integrating Testsigma with Xray](https://testsigma.com/docs/integrations/test-management/xray/) --- @@ -50,7 +49,6 @@ Testsigma integrates with various tools in your software delivery cycle to make ### **4. Test Management** * [Documentation on integrating Testsigma with Azure DevOps Boards](https://testsigma.com/docs/integrations/test-management/azure-devops-boards/) * [Documentation on integrating Testsigma with Trello](https://testsigma.com/docs/integrations/test-management/trello/) - * [Documentation on integrating Testsigma with Freshrelease](https://testsigma.com/docs/integrations/test-management/freshrelease/) * [Documentation on integrating Testsigma with Clickup](https://testsigma.com/docs/integrations/test-management/clickup/) * [Documentation on integrating Testsigma with Linear](https://testsigma.com/docs/integrations/test-management/linear/) diff --git a/src/pages/docs/integrations/test-management/azure-devops-boards.md b/src/pages/docs/integrations/test-management/azure-devops-boards.md index fd2034d3..f8b8813e 100644 --- a/src/pages/docs/integrations/test-management/azure-devops-boards.md +++ b/src/pages/docs/integrations/test-management/azure-devops-boards.md @@ -42,14 +42,14 @@ The Testsigma Azure DevOps Integration allows you to create work items within yo ## **Steps to Integrate Azure DevOps with Testsigma** 1. Navigate to **Settings > Integrations**. - +  2. Enable the toggle on the **Azure DevOps Boards** widget. - +  3. On **Azure DevOps Boards details** prompt, enter **Organization URL**, **Access Key**, and click on **Save & Enable**. - +  --- @@ -58,24 +58,23 @@ The Testsigma Azure DevOps Integration allows you to create work items within yo ## **Creating Work Item on Azure from Testsigma** 1. Navigate to **Run Results > Test Case Result**, where you want to add a bug. - +  2. Click on **Report Bug**. - +  3. On **Report** overlay, click on the **Azure DevOps** icon. - +  -4. On the **Create New Issue** prompt, click on **Create Ticket**. - +4. On the **Report** overlay, click **Report Bug**. +  [[info | **NOTE**:]] | - If you want to link to an existing issue on Azure DevOps, click on the **Link to Issue** button, search for an existing issue in the search field and click on **Link Issue** to add a link to an existing Issue. -|  | - You can also link the Azure DevOps test case with Testsigma test case. Get the test case ID from Azure DevOps, navigate to **Create Tests > Test Cases > Test Case**, and enter the ID in the top right corner of the test case details page with the text box **Enter Azure DevOps ID**. The test case will be linked with the Azure DevOps test case. diff --git a/src/pages/docs/integrations/test-management/freshrelease.md b/src/pages/docs/integrations/test-management/freshrelease.md deleted file mode 100644 index f3401235..00000000 --- a/src/pages/docs/integrations/test-management/freshrelease.md +++ /dev/null @@ -1,94 +0,0 @@ ---- -title: "Freshrelease Bug Reporting Integration" -page_title: "Freshrelease Bug Reporting Integration in Testsigma" -metadesc: "How to integrate Testsigma with Freshrelease for real-time bug reporting during Test Runs | Push bugs directly from Testsigma to your Freshrelease project" -noindex: false -order: 17.54 -page_id: "freshrelease-bug-reporting-integration" -warning: false -contextual_links: -- type: section - name: "Contents" -- type: link - name: "Prerequisites" - url: "#prerequisites" -- type: link - name: "Creating Freshrelease API Key" - url: "#creating-freshrelease-api-key" -- type: link - name: "Integrate Freshrelease With Testsigma" - url: "#integrating-freshrelease-with-testsigma" -- type: link - name: "Creating a Bug" - url: "#creating-a-bug" ---- - ---- - -With Testsigma and Freshrelease integration, you can push bugs directly from Testsigma to your Freshrelease project, capture screenshots, annotate bugs, and share them with your teammates. - -This document will discuss how to establish Integration with Freshrelease from your Testsigma account and how to create the first bug from Testsigma, which can flow into Freshrelease. - ---- - ->Prerequisites
-> -> Before you begin, ensure that: -> 1. To integrate Freshrelease with Testsigma, you need the following information from your Freshrelease Account: -> - Freshrelease Organization URL -> - API Key -> 2. You have referred to the [documentation on executing test plan runs](https://testsigma.com/docs/runs/test-plan-executions/). - ---- - -## **Creating Freshrelease API Key** - -1. First, log into **Freshrelease Admin Account**. - -2. On the bottom left corner, click on **Profile Settings**. The profile settings page will have the **API Key** and the **URL** to which you have logged in is your **Account URL**. - ---- - -## **Integrating Freshrelease with Testsigma** - -1. Navigate to **Settings > Integrations**. - - - -2. Enable toggle on **Freshrelease** widget. - - - -3. On the **Freshrelease details** prompt, enter **Account URL**, **API Key** and click on **Save & Enable**. - - - ---- - -## **Creating a Bug** - - -1. Navigate to **Run Results > Test Case Result**, where you want to add a bug. - - - -2. Click on **Report Bug**. - - - -3. Choose **Freshrelease** and enter information about your bug. - - -[[info | NOTE:]] -| Only the bug reporting tools that have been enabled via the plugins page (add link) will be displayed here. - -If you want to link to an existing issue on Freshrelease, click on the **Link to Issue** button, search for an existing issue in the search field, and click on Link Issue to add a link to an existing Issue on Freshrelease. Otherwise, enter the bug details in the form as required. - -4. Click on **Create Ticket**. - - -When the bug is created, some additional details regarding the test result, such as the test execution video and step screenshots, are automatically added to the issue on Freshrelease by Testsigma. This helps the developer who checks the issue in Freshrelease better understand the issue/bug with more context. - - - ---- \ No newline at end of file diff --git a/src/pages/docs/reports/custom-dashboard/manage-custom-dashboard.md b/src/pages/docs/reports/custom-dashboard/manage-custom-dashboard.md index c866b680..bfd60c31 100644 --- a/src/pages/docs/reports/custom-dashboard/manage-custom-dashboard.md +++ b/src/pages/docs/reports/custom-dashboard/manage-custom-dashboard.md @@ -47,25 +47,32 @@ Dashboards are designed to be created quickly. A basic dashboard with 5–7 widg ## **Steps to Create a Dashboard** 1. On the **Dashboard**, click **Advanced** next to **Legacy**. +  2. A list of existing dashboards appears in tabs. If this is your first dashboard, the list will be empty. +  3. Click **Create Dashboard**. A tab opens prompting you to enter a dashboard name and select widgets. +  Alternatively, click **Create New +** in the top-right corner and select **Dashboard** from the dropdown menu. +  4. Enter a descriptive name for your dashboard. The name should convey its purpose and audience. +  - **Examples**: "Release Readiness - Q2 2026", "Mobile App Quality Dashboard", "Team Velocity Tracker" + **Examples**: *"Release Readiness - Q2 2026"*, *"Mobile App Quality Dashboard"*, *"Team Velocity Tracker"* **Tip**: Use names specific enough to be searchable but concise enough to fit in navigation menus. -5. Select **Widgets** from the library, which is organized into five categories: +5. Select **Widgets** from the library, which is organized into six categories: +  - **Executive Insights & Release Readiness** - **Reliability & Stability** - **Test Design & Team Productivity** - **AI Intelligence & Agentic ROI** - **Infrastructure & Performance** + - **Accessibility** [[info | **NOTE**:]] | You can choose multiple widgets from the same category and mix widgets from different categories. For more details, see the [Widgets Reference](https://testsigma.com/docs/reports/custom-dashboard/widgets-reference/). @@ -73,6 +80,7 @@ Dashboards are designed to be created quickly. A basic dashboard with 5–7 widg You can also click the eye icon next to any widget to preview it before adding it to your dashboard. 6. Click **Create Dashboard**. +  Your dashboard is now live. Widgets display data and update in real time as test executions complete. @@ -83,14 +91,17 @@ Your dashboard is now live. Widgets display data and update in real time as test 1. Open the **Dashboard**. 2. The filter controls appear at the top of the dashboard. +  3. Click any filter control to open its menu. 4. Select your desired value. The following filter dimensions are available: - - **Project**: Use the Project selector to scope data to a specific project, application, and version, or select **All Projects** to view aggregated data. +  - **Date range**: Use the Date range filter to define the time period for analysis. Available options include recent hours (3–24 hours), current periods (Today, This Week, This Month, This Quarter), and longer ranges (Last 3–60 days), or Custom Date. +  - **Interval**: Use the Interval filter to control how data is grouped. Options include Hourly, Daily, Weekly, Monthly, Quarterly, and Yearly. +  5. All widgets update to reflect your filter selection. @@ -103,17 +114,22 @@ After creating a dashboard, you can add widgets, remove widgets, or change the a 1. On the **Dashboard**, switch to the **Advanced** dashboard and click the dashboard you want to modify. 2. In the top-right corner, click the **Edit** button. +  3. Click **Add Widgets** to open the widget library. Select additional widgets from any category. Your current selections are highlighted. +  4. Hover over any existing widget to perform two actions: - **Delete**: Click the Delete icon to remove the widget from the dashboard. +  - **Rearrange**: Click, hold, and drag the Drag icon to reposition the widget. +  [[info | **NOTE**:]] | Removing a widget deletes it from your dashboard permanently. You can add it back later if needed. 5. Click **Save Changes** to apply your changes. +  Your dashboard updates immediately with the new widgets and layout. @@ -122,11 +138,14 @@ Your dashboard updates immediately with the new widgets and layout. ## **Share Dashboard** 1. On the **Advanced** dashboard you want to share, go to **More Options > Share**. +  2. In the **Share Dashboard** dialog, click **Create shareable link**. +  3. Click **Copy link** to share it with stakeholders. +  -Anyone with the link can view the dashboard in read-only mode. + Anyone with the link can view the dashboard in read-only mode. --- diff --git a/src/pages/docs/reports/custom-dashboard/overview.md b/src/pages/docs/reports/custom-dashboard/overview.md index c14ffdae..b1de0543 100644 --- a/src/pages/docs/reports/custom-dashboard/overview.md +++ b/src/pages/docs/reports/custom-dashboard/overview.md @@ -37,6 +37,7 @@ Dashboards update automatically as test executions complete, ensuring the data r - Click into failing tests to see step-by-step details and errors - Share dashboards with a shareable link for stakeholders - Update your dashboard anytime to match your changing needs +- Monitor accessibility compliance scores, issue trends, and remediation progress across your application --- @@ -52,5 +53,6 @@ You select widgets from a library and arrange them on your dashboard. Each widge - **Quality improvements**: Track flaky tests and error patterns to identify what to stabilize first. - **Team performance**: Monitor test authoring velocity and see who is contributing to test growth. - **Infrastructure planning**: See resource utilization and identify bottlenecks before they cause delays. +- **Accessibility compliance**: Monitor WCAG conformance scores, track how many issues remain open by severity, and measure remediation progress, all from a single view. --- diff --git a/src/pages/docs/reports/custom-dashboard/widgets-reference.md b/src/pages/docs/reports/custom-dashboard/widgets-reference.md index 5f4253ea..646448f8 100644 --- a/src/pages/docs/reports/custom-dashboard/widgets-reference.md +++ b/src/pages/docs/reports/custom-dashboard/widgets-reference.md @@ -1,6 +1,6 @@ --- title: "Widgets Reference" -page_title: "Custom Dashboard Widgets Reference | Testsigma" +page_title: "Custom Dashboard Widgets Reference in Testsigma" metadesc: "Detailed reference for all widgets available in Testsigma Custom Dashboards. Covers purpose, data displayed, interpretation, and recommended use cases for each widget." noindex: false order: 14.07 @@ -24,6 +24,9 @@ contextual_links: - type: link name: "Infrastructure & Performance" url: "#infrastructure--performance" +- type: link + name: "Accessibility" + url: "#accessibility" - type: link name: "Quick Dashboard Templates" url: "#quick-dashboard-templates" @@ -46,6 +49,7 @@ Widgets are grouped into categories based on their purpose to make navigation ea --- ## **Executive Insights & Release Readiness** +