Content Comparison

Build 8.17.1.1 - Release Date: 2024-09-20

Summary: Bug Fixes

• Fixed bug that removed auto-generated test cases created with QI from the QI statistics after updating the test case steps.

• Fixed a bug that intermittently removed the updated step execution comment after saving it on the test execution screen.

Build 8.17.1 - Release Date: 2024-07-27

Summary: New Features, Improvements & Bug Fixes

Generate Test Cases using QMetry Intelligence (Currently in Beta):

Testers can now generate functional test cases using QMetry Intelligence (QI) directly from a requirement or user-provided description. QI will also enable testers to generate test case details and steps for an existing test case using the same inputs, with the option to update the existing test case or create a new version.

• Key benefits: The auto-generation feature accelerates the test case authoring phase by swiftly creating test cases with steps aligned to specified requirements. This ability reduces the manual effort of testers, allowing them to focus more on test case execution and validation. As a result, the feature saves valuable time during the testing lifecycle and enables teams to deliver releases faster.

• How it works: The QI model extracts relevant details from a requirement or user-provided description to generate modular functional test cases with adequate coverage, ensuring thorough validation of the acceptance criteria.

  • For QI to generate test cases with higher accuracy, the requirement description must provide sufficient information in a structured use case format. The description should also contain acceptance criteria that clearly define the expected behaviour of the feature; decomposed stories will yield better results. These details enable QI to analyze the context and accurately identify test scenarios.

  • Testers can accept, modify, or reject the generated test cases before approving them for creation into the project's test case library.

  • For projects integrated with external trackers like Jira, Rally, or Azure to sync their requirements with QMetry, project administrators can configure up to two issue fields as input descriptions for QI to generate test cases.

• Activation instructions: To enable all users to auto-generate test cases using the QI feature, the QMetry Super Administrator must activate the feature from the General Settings.

• Usage Statistics: The administrators and testers can also view statistics on how the auto-generated test case feature is helping save time and effort for both them and their project teams.

Report Enhancements

• System and custom report charts now display the total record count, making it easier for users to analyze the data.

• PDF and Word exports of test cases and test executions now comply with FDA guidelines for regulated industries by displaying 'N/A' for empty fields and sections.

Administrative Enhancements

• QMetry Super Administrators can now disable the feature at instance level that lets users generate and share embedded URLs for report dashboards with unrestricted access, in line with organizational policies.

• When cloning a project, a confirmation pop-up is provided to remind administrators that the project will be in read-only mode until cloning is complete, helping them avoid initiating cloning during peak times.

Miscellaneous Enhancements

• The default order for the Extent of Testing list has been updated so that a higher RPN indicates more intensive testing requirements. Similarly, the Risk Likelihood and Risk Impact lists have also been adjusted to align with this change.

• In projects with the test case dependency feature enabled and auto-propagate status settings configured, the execution status of a dependent test case will automatically be marked as 'blocked' if its predecessor test case fails.

• The 'Copy Link' button has been relocated from the Share pop-up to the details screen, and positioned next to the asset key, for easier access.

• When exporting executions to PDF and Word formats, execution dependencies between test cases will now appear in a separate section for clearer organization.

Bug Fixes

• Fixed a bug that blocked bulk copying of test cases when the source project had risk-based testing enabled.

• Fixed a bug that caused tabular gadgets to lose their size and fail to display data correctly when enlarged on the custom dashboard.

• Fixed a bug that prevented the 'Create Issue' screen from displaying for Jira-integrated projects when the Jira field name had a trailing space.

• Fixed a bug that prevented all test cases linked directly to a Jira defect from displaying within QMetry's Test Case section on the Jira issue page.

• Fixed a bug that caused Open API calls with a trailing forward slash to fail, resulting in a 404 error response upon execution.

• Fixed a bug that prevented filtering test cases, test suites, requirements, and linked issues count with 0.

• Fixed a bug that prevented filtering a custom gadget simultaneously on multiple date-type fields when designing it using Visual Reports.

• Fixed a vulnerability due to the Apache library "commons-text-1.9.jar" used in the automation container by upgrading it to v1.11.

• Fixed a bug that prevented archived projects from appearing on the Edit Fields configuration screen.

• Fixed a bug that caused the steps to export in the incorrect order in the Excel file exported from the test case module.

• Fixed a bug that prevented setting the system "read only" role as a default for newly created LDAP/SAML users.

• Fixed a bug that prevented versioning test cases containing shareable steps and simultaneously syncing them for execution.

Build 8.17.0.1 - Release Date: 2024-06-11

Summary: Bug Fixes

• Fixed a bug that prevented cycles from appearing under the cycle filter for the filtered releases under custom gadgets.

• Fixed a bug that prevented save and discard buttons from appearing for Actual Outcome and Comments fields on the execution screen for parameterized test cases.

• Fixed a bug that incorrectly reset the value of the Associated Cycle field to "None" for issues updated through a bulk update.

Build 8.17.0 - Release Date: 2024-06-01

Summary: New Features, Improvements & Bug Fixes

New Features

Test Case Dependency

• Test case dependency refers to the relationship where the outcome of one test case depends on the successful execution of another. Managing these dependencies is crucial for ensuring a logical and organized testing process, especially for complex test scenarios.

  • Testers can now define execution dependencies between test cases as Predecessor orSuccessor relationships. This dependency ensures that the predecessor test case must be executed successfully before executing its successor. During execution, testers can automatically notify the execution assignees of successor test cases when their test cases are blocked or unblocked for executions. 

  • Introduced Test case and Test Execution dependency reports that showcase the dependency relationship between multiple test cases and their executions.

  • Project Administrators can choose to enable the feature for defining dependency relationships between test cases and configure the related execution settings. They can also opt to auto-propagate the execution status of predecessor test cases to successor test cases.

SCIM 2.0 Support for User Provisioning and Deprovisioning

• QMetry now supports System for Cross-domain Identity Management (SCIM) 2.0, enabling seamless integration with identity providers, specifically OKTA, for automated user provisioning and de-provisioning. This feature ensures that only authorized users have access to QMetry, managed through a centralized user management process, maintaining compliance with security policies.

  • The following provisioning actions are currently supported: Push New Users, Push ProfileUpdates, and Push Groups.

  • Users will be automatically created and assigned to respective Projects and Roles when added to OKTA groups and automatically deactivated when removed from OKTA groups.

  • User attribute management, including modifying Username, First Name, Last Name, Alias, and Email ID, is also supported with this feature and can be made only through the identity provider platform.

  • Once SCIM 2.0 is enabled, user updates, creation, or deactivation, as well as project and role assignments, can only be done from the identity provider platform. Project Admins or other users with managing user permissions cannot make these changes directly withinQMetry.

​​
Risk-Based Analysis

• Introduced the Risk-Based Testing feature to enhance the testing process by empowering testing teams to systematically identify, assess, and prioritize risks linked with requirements and test cases. This feature enables teams to focus their testing efforts on features with the highest likelihood of risks and potential defects.

  • Risk Definition: Project Administrators can activate the Risk-Based Analysis feature for their project. This functionality automatically creates the necessary risk fields and enables admins to define risks and other related factors, thereby ensuring comprehensive risk management.

  • Risk Association: Testers associate risks with requirements and test cases, assigning their likelihood and impact.

  • Determining the extent of testing: QMetry automatically computes the risk priority number and assigns the appropriate level of testing required for each risk.

  • Reports: Introduced Risk Traceability reports to assist testers in tracing risk factors associated with the requirements and their corresponding test cases, and vice versa.

  • To enable viewing risk-based fields in Jira, an install or upgrade of the QMetry Jira Integration latest app (v2.2.7) is required for the Jira Server and Data Center installations. For customers using Jira Cloud, the add-on will be auto-upgraded.

QMetry Intelligence (Only on Cloud)
Increase Testing Confidence with Flaky Score & Success Rate Metrics.

• Flaky Score: QMetry Intelligence uses AI to assess the flakiness of test cases by calculating "Flaky Score" derived from their previous executions. This score empowers testers to identify test cases whose future execution result is non-deterministic. A flaky test case exhibits non-deterministic behavior when executed repeatedly under the same conditions, resulting in intermittent successes and failures. Identifying flaky tests is pivotal for maintaining control over testing processes, as they can impede testing pipelines and undermine confidence. Traditionally, determining test case flakiness requires manually comparing test results from multiple runs, which is time-consuming. With QMetryIntelligence, this is automated, saving testers and developers valuable time and effort. QA Managers can define and configure settings according to their specific testing processes for calculating the flaky score, aligning it with their unique testing methodologies.

• Success Rate: Introducing the "Success Rate" metric for test cases, derived from their previous executions, that has significant importance in the testing process. For QA teams, the test case success rate is a crucial indicator for evaluating test case execution performance. A high success rate signifies a robust and dependable test case, providing confidence in its performance. On the other hand, a low success rate highlights potential issues or areas of improvement, signaling the need for further investigation and refinement.

Enhancements to Jira Integration

• Project admins can now deactivate syncing for specific Jira System Fields within QMetry Requirements and Issues for selected Jira Issue Types. These fields include Description, Component, Fix Version, Priority, Labels, Attachments, Affected Version, Environment, and Assignee.

• Project admins can now sync separate Jira Issue fields for viewing issue details in QMetry and creating issues from QMetry when configuring Jira Issue Types as QMetry Issues.

• Users should upgrade their QMetry Exploratory Testing plugin to the latest version per the above enhancements and comply with QTM release 8.17. The latest versions of add-ons are as follows: Chrome 1.2.6, Firefox 1.1.0, and Edge 1.0.6.

Improvements to the Test Case Module

• The latest execution status of a test case is now displayed on all Test Case List screens across the product. This status gives testers immediate visibility into whether a specific test case has been executed and displays its recent execution state. Project admins can configure parameters to tailor this display, allowing them to choose the display of the latest execution status based on the most recent execution within the current project or across projects. They can also decide whether to include only the recent or all the test case versions for determining the latest test case status.

Bug Fixes

• Fixed a bug that prevented reordering linked test cases while creating a test suite.

• Fixed a bug that prevented cloning projects containing test suites with cross-project test cases.

• Fixed a bug that prevented filtering issues based on cycles within the issue module when a release has one of its cycles archived.

• Fixed bug that displayed an incorrect message during login when a deleted user previously authenticated via SSO attempts to log in.

• Fixed a bug that caused test cases export from a cloned project to display an incorrect username in the "created by" field.

• Fixed a bug that prevented the display of the QMetry Test Case links in the Azure Work Item Links when test cases are associated with requirements from the details page.

Build 8.8.1.3- Release Date: 2021-10-15

Bug Fix

• Fixed a bug that prevented upload of automation test executions results if the test suite is reused, and the combination of linked platform and cycle exceed 100.

Build 8.8.1.2- Release Date: 2021-09-25

Bug Fixes

• Fixed a bug that prevented QMetry <> Jira integration when authenticated using QMetry Jira Integration Addon for Jira server. Users will need to upgrade or install the QMetry Jira Integration app v2.1.6 from the Atlassian Marketplace.

• Fixed a bug that prevented upload of test cases and test executions for Cucumber automation results in the following scenarios:

• • When the "line" attribute in the result file is empty or null. QMetry does not utilize the line attributes and will not parse them anymore.

  • When the "name" attribute for a test step in the result file is empty, the "keyword" attribute gets imported as the step description.

• Fixed a bug that prevented users with default Tester role to access the "My Dashboard" and other System Dashboards.

Build 8.8.1.1- Release Date: 2021-09-04

Improvement & Bug Fixes

Improvement

• Images added to the description and test steps will appear as thumbnails and opens full image on click.

Bug Fixes

• Fixed a bug that prevented the upload of attachments having the .tcc file extension.

• Fixed a bug that prevented the syncing of Jira labels to the issue module.

Build 8.8.1- Release Date: 2021-08-07

Improvements & Bug Fix

Improvements

• Upload an attachment with a file size of up to 100 MB.

• Large text fields improvements

  • Attach images up to 1 MB in size.

  • Insert tables with the ability to add/delete rows and columns.

• Test case steps improvements

  • Bulk-delete test case steps.

  • Add hyperlinks while authoring test case steps details.

• For QMetry projects that are integrated with an external tracker, the "Error message" and "Trace" for the automated test case get added as an attachment to the bug created for the execution.

• Custom dashboard improvements

  • Copy your dashboard along with its gadgets and view permissions.

  • Share dashboard to individual users/projects-roles or by generating embedded URLs from the edit dashboard view.

• Layout management improvements

  • Set a section as default for the newly created user-defined fields on the layout.

  • Replace existing fields on the layout with a spacer to preserve the current view while defining the layout.

• Exploratory Testing improvements

  • For projects using the internal issue module, the create bug screen will now display only the fields enabled for the issue module
    layout.

  • Release 8.8.1 requires users to install/upgrade the latest version of QMetry Test Management – Exploratory Testing extension on Chrome (v1.1.1), Firefox (v1.0.6), and Edge (v1.0.2) browsers.

• Release 8.8.1 upgrade requires to install/upgrade the latest version v2.1.4 of Jira Integration - QMetry Enterprise App in Jira. For customers using Jira Cloud, the add-on will be auto-upgraded.

• QMetry Automation Agent will support Open JDK 11.0.11.

Bug Fix

• Fixed a bug that prevented archiving a few list values of system fields for the default project created along with the installation.

Build 8.7.1.4 - Release Date: 2021-05-01

Bug Fixes

• Fixed a bug that prevented the display of BitBucket folder structure repository in requirements BDD tab, if branch contained a forward slash '/' in its name.

• Fixed a bug that prevented the display of complete folder structure in the selected branch of the BitBucket repository.

• Fixed a bug that prevented the display of full folder names for the selected branch of the BitBucket repository. Up to 70 characters are now displayed in the folder name. Complete folder names are visible on hover.

Build 8.7.1.3 - Release Date: 2021-03-20

Bug Fixes

• Fixed a bug that utilized all available threads on the server leading to downtime for cloud users.

• Fixed a bug that prevented QMetry Agent to start on Mac OS with Open JDK v11.0.2.

• Fixed a bug that prevented the import of JUnit files that have an empty test suite with no test cases.

• Fixed a bug that restored default column sizes in all list views for new users on refresh.

• Fixed a bug that caused a delay while successively updating test case execution status.

• Fixed a bug that intermittently displayed an incorrect count of issues to be synced from Jira in the scheduler.

Build 8.7.1.2 - Release Date: 2021-03-06

Bug Fixes

• Fixed a bug that was updating Due Date to the previous day of the selected Date in QMetry after an issue was created from QMetry to Jira.

• Fixed a bug that prevented syncing of some requirements and issues for the Jira server edition.

• Fixed a bug that was preventing the display of the full name of users on the Users screen.

• Fixed a bug that was preventing users to log into Azure from QMetry using the standard URL or extended URL.

Build 8.7.1.1 - Release Date: 2021-02-20

Improvements & Bug Fixes

General Improvements 

• Support for Azure AD for SAML Integration.

Bug Fixes

• Fixed a bug that prevented creation of duplicate requirements from Jira to QMetry.

• Fixed a bug that caused “QMetry section/panel” hide in new Jira issue view.

Build 8.7.1 - Release Date: 2021-01-30

Improvements & Bug Fixes

General Improvements

• QQBot Insights is renamed as QQBot Prediction.

• Export an exploratory testing session into a PDF.

• Download all attachments of a test case/test step and their execution in just one click.

• Jira server and data center app - "Jira Integration - QMetry Enterprise" v2.1.1 compatible with QMetry v8.7.1 released.

Bug Fixes

• Fixed a bug that did not display the applied filters and tags on gadgets while viewing them on embedded URL or shared dashboards.

• Fixed a bug that prevented the display of pie chart gadgets when filtered only on Jira fields.

• Fixed a bug that prevented adding attachments while creating Rally issues from QMetry.

• Fixed a bug that prevented rich text from being displayed correctly on cross table custom gadgets.

• Fixed a bug that prevented test cases from appearing in the QMetry Insights reports if the test case folder is moved to another folder.

Build 8.7 - Release Date: 2020-12-19

New Features, Improvements & Bug Fixes

General Improvements

• QMetry now supports any International Language (available on request). Currently added support for Español (Spanish). - Introduced Internationalization App.

• Bulk-export up to 50 test cases to a single PDF file. 

• QMetry Automation Agent is now supported on Open JDK 11. 

• Archive individual test executions to prevent them from getting altered due to changes made to the scope of test suite when reusing test suite for future executions.

• • Test cases added to the test suites are not added to the archived test executions. 

  • Test case linked to archived executions can’t be unlinked from the test suites.

Integration Improvements 

• Integrate Azure & Rally to sync work items in QMetry to get complete traceability for Requirements -> Test cases -> Test Suites -> Test Executions -> Bugs.

• • Sync Azure/Rally Work Items like User Story/Feature/Epic etc in QMetry as Requirements. The integration is unidirectional, changes made to work items sync real time to QMetry. 

  • Sync Azure/Rally Work Items like Defect/Issue/Bug etc in QMetry as Issues. The integration is bidirectional, changes made to work items sync real time to QMetry and vice versa. Existing work items can be linked to executions or New work items can be created directly from the test case execution screen. 

• Improved Issue traceability in Requirements - Issues linked to test case executions are now auto linked to QMetry requirement under issue tab & also under Jira issue link for stories synced from Jira.

• `Jira Integration - QMetry Enterprise` app v2.1.0 is released compatible with QTM 8.7. Customers using Jira Server/DC need to update the app manually, while it is automatically upgraded for Jira Cloud.

 Report Improvements

• New Report - “User Project Role Summary” added to “Login Summary” Dashboard - displays list of all users assigned to different projects along with their roles and status.

• Improved Traceability Report - 

• • Trace by Requirements/Test Cases/Issues can filtered by any System or External Tracker fields. 

  • Added “Trace by Test Executions” that allow users to view traceability by filtering executions with specific release/cycles/platform combination.  

  • Filters applied or columns selected on module grids will apply to traceability report by default. This helps users to reuse the module filters instead of applying those filters again. 

• Filter icon on the report gadget displays count of filters applied & hovering the filter icon displays the applied filter.

• Archived Test Executions Runs are excluded from system reports. 

• Link to ER diagram for Release 8.7 - Added “isExecutionArchived” in “test execution” which denotes the status of Test Execution as “Archived” or “Unarchived”. 

Exploratory Testing Improvements

• “Exploratory Testing” extension is now available on Firefox. This Firefox extension is compatible with release 8.7 and above. Click here to download - QMetry Test Management Exploratory Testing for Firefox (v1.0.3)

• With release 8.7 upgrade users will be required to upgrade the compatible latest version v1.0.8 of QMetry Test Management – Exploratory Testing extension on chrome browser

Introducing QQBot with AI capabilities

QQBot provides insights to the end user by finding redundant test assets while creating, editing and viewing test cases and requirements through an intelligent duplicate detection algorithm. 

• QQBot provides suggestions for possible duplicates by displaying the test case and requirement matches with the matching percentage.

• QQBot predicts test cases that could possibly match a requirement and vice versa. 

• QQBot is currently available only for SaaS customers that have the feature enabled. – QQBot app.

End of Support for Internet Explorer 

• We are retiring IE support for QMetry Test Management – Cloud and Server products on 30th June 2021. End of support means we will not fix bugs that are specific to IE and new features will not be supported for IE. QMetry will continue to provide support on Edge.  We are expecting all of our customers using QMetry on IE to shift to Edge or Chrome/Firefox. Our support can help you along the way in this transition.

• In 2015, Microsoft released Edge as the browser to supersede Internet Explorer (IE). To allow us to continue to take advantage of modern web standards to deliver improved functionality and the best possible user experience across all of our products, we have decided to end support for IE.

Bug Fixes

• Fixed a bug that did not display test case steps in the correct order of execution when a same shareable test case is used multiple times along with data parameter in the test case.

• Fixed a bug that prevented syncing of deleted labels to QMetry Insights database. 

• Fixed a bug that displayed incorrect release and cycles dates due to day light saving changes.

• Fixed a bug that did not export test case entity key for Test Result Log Report.

• Fixed a bug that reset the date filters to default when columns were sorted in the Test Result Log Report.

• Fixed a bug that synced same Jira issues multiple times to QMetry causing them to duplicate in some cases.

• Fixed a bug that prevented auto sync of newly created Jira field values to QMetry filters.

API Changes

The following is the Summary of APIs modified. For more details, click /wiki/spaces/QPro/pages/1990590469

Build 8.6.4.2 - Release Date: 2020-11-11

Bug Fixes

• Fixed a bug that prevented integrating with bitbucket repository with correct credentials.

• Fixed a bug that caused users to get logged out abruptly while working in QMetry.

• Fixed a bug that prevented the test cases in folders from loading for users who had a custom field enabled on the grid view which was deleted later.

Build 8.6.4.1 - Release Date: 2020-10-24

Improvements & Bug Fixes

Improvements

• "Jira integration - QMetry Enterprise" app is now compatible with Atlassian's site rename feature.

Bug Fixes

• Fixed a bug that did not display assignee information when Test Execution Summary Report by Assignee is exported.

• Fixed a bug that scrolled up the grid header while linking assets through bulk operation.

• Fixed a bug that prevented users from logging in to QMetry if password contains plus(+) character.

• Fixed a bug that displayed an error while applying filter to the 'Test Execution Summary by Folder' report.

• Fixed a bug that prevented navigating through test cases using previous and next buttons.

• Fixed a bug that prevented loading of the default dashboard for SAML authenticated users after login.

• Fixed a bug that forcefully logged out users after 15 mins of session idle time when multiple tabs are open.

Build 8.6.4 - Release Date: 2020-10-10

Improvements & Bug Fixes

Improvements

Improvements to Test Case and Test Execution

• Summary and Entity Key are now separate columns on all link test asset screens to allow better sorting and filtering.

• Enhanced test case steps edit experience with an option to open step details in maximized mode.

• Users can view shareable test case steps in the test case without scrolling.

• Test executions with archived release/cycle will be hidden by default.

• Filter requirements by External key while linking them to Test cases and Test Suites. 

• Users can hide test steps “Input data” and “Expected Outcome” fields on the execution screen to utilize the space effectively.

• Link Test case to Test suite panel now displays more test cases on the page. 

Improvements to Jira Integration

• QMetry authentication from `Jira Integration - QMetry Enterprise` app now supports Open API key (part of Open API app) and two step verification.

• Jira field mapping configuration is now separate for each integrated issue type.

• Test case panel, test case details view and test execution sections in Jira issues now have resizable columns.

• Test case details view in Jira now displays all user defined fields.

• `Jira Integration - QMetry Enterprise` app v2.0.9 is released compatible with QTM 8.6.4. Customers using Jira Server/DC need to update the app manually, while it is automatically upgraded for Jira Cloud. Server customers need to sync the meta data for all the projects integrated with Jira.

Improvements to Reports

• Advance Query Reports database schema tables `Requirements` and `Issues` having field names starting with “Jira” are updated with “Ext”. (part of Advance Report app)

• • Download the new ER Diagram 8.6.4.

  • For more details refer this page.

• Users will now be able to set any system or custom dashboard as their default dashboard seen after logging in to QMetry.

• Introduced new report `Count of API Requests by User` which shows number of Open API or Automation API calls made by each user at a given time.

• Share dashboards with specific users or all users of a specific role, project combination. (part of Advance Report app)

Improvements to Automation API, Bamboo/Jenkins/Maven Plugins

• Upload automation results of Robot framework.

• Added support for uploading automation results from a Bamboo remote agent server.

• skipWarning parameter have been added that allows to import test cases by truncating summary having more than 255 characters.

• QMetry Test Management for Bamboo (v1.0.9), QMetry Test Management Plugin for Jenkins (v1.10) & QMetry Test Management Plugin for Maven has been released with above supported improvements.

Improvements to QMetry Administration

• QMetry Admin can now enforce two step verification for all users by making it mandatory. (part of Customization app)

• Password expiry related email notifications will be sent to QMetry authenticated users in advance. Organization who have subscribed for customization app can even configure the advance number of days. (part of Customization app)

• Users having two step verification enabled can now use recovery codes to regain access to the accounts. 

• Easily filter and find users having two step verification enabled on users list page. 

• QMetry Admin using On premise installation can now set a maintenance message that will be displayed on login screen to notify users about a scheduled maintenance. (part of Customization app).

General Improvements

• Export exploratory testing session details, documented test steps and associated defects to a word document. (part of Exploratory Testing app)

• Share defect details over email to users even outside of QMetry.

• Import test cases with longer summaries now truncated to 255 characters using option to `Import with Warning`.

• Gitlab support for BDD integration.

Bug Fixes

• Fixed a bug that prevented cloning of a project when the project has test case or requirement with attachments moved from another project.

• Fixed a bug that prevented auto linking of requirements to testcases when requirement key is specified in the automation result file.

• Fixed a bug that did not display assignee information when Execution Summary Assignee report is exported as PDF.

• Fixed a bug that prevented display of all records for a tabular view gadget when dashboard is shared using embedded URL.

• Fixed a bug that displayed the test case execution for a deleted parameter value combination for custom reports generated using the Advanced Query module.

• Fixed a bug that displayed html tags for large text user defined field when test case is exported to a PDF.

• Fixed a bug that prevented proper loading of test case when accessed using URL with test case id.

Summary of Open Rest API Changes

The following APIs have been modified. /wiki/spaces/QPro/pages/1789820948. (part of Open API app)