Release Notes 8.4.x

Visual analytics reporting now supports custom fields.

User can create "new folder" while performing bulk copy/move of test assets.

"Ask Me Anything" now search data in test steps i.e. step summary, expected outcome and input data.

Provided option to bulk approve (e-sign) test case & bulk approve/close (e-sign) test suite executions.

Released QMetry Exploratory Testing Add-on v1.3.7 on Chrome store.

Increased limit for uploading attachment to test assets up to 30 MB for server installations.

"Include Entities from Sub-Folder" will be auto-enabled for all the modules.

User can define "Test suite summary" while importing automation results via Automation API/Jenkins/Bamboo/Maven.

QMetry displays "resolution", "fix version" & "affected version" fields for requirements imported from Jira

User is warned before closing the test case authoring screen to prevent accidental data loss.

QMetry Voyager is renamed as QMetry Exploratory Testing.

View subsequent test assets using Next/Previous button on details screen Improved UI that allows easy scrolling of folder tree, asset grid & pagination on module grids.

Improved UI that allows quick filter of Test assets on module grids.

Issue Leakage Report can be drilled down to get list of the missed issues.

New Report - "Issue Average Ageing" Report that displays the average age of unresolved issues for a selected time frame.

Added External Id column in Issue reports to differentiate between internal and Jira issues.

Task notification displays the number of test assets on which bulk operations are performed.

Improved performance for bulk copy/move/link TC/Unlink TC to Test suite operations.

Actual Results and Test Step Status of failed testcases will be added to issue description when raised from execution screen.

Issues created from execution screen will have summary as 'Test case ID + Test Case summary'.

Issues linked at Test Steps will be displayed at Test Case on the execution screen.

The avatar/indicator of username is deprecated across all screens in the Product.

Users can associate release & cycle to test cases, requirements & test suites only if modify project permission is provided.

Search results in Microsoft Edge does not reset after clearing the search text.

Fixed bug with horizontal scroll bar on all the module girds and link screens.

Test suite export does not include parameterized values for Test Steps.

Post editing test cases/test suite/requirement the focus on selected folder gets reset.

Bulk delete in Issue Module allows deletion of Jira issues added/linked from within QMetry.

Performance improvement with support for 2000 users

Simplified menu options for quick navigation

Schedule emails for system reports - daily, weekly or monthly

Import Test cases/Requirement/Issues using xls/csv/xlsx up to 10 mb in size (earlier it was 2 mb).

Filter Test cases/Requirement/Issues by their Folder Path or Labels while linking and during bulk operations.

Added project level configuration to identify the issues as resolved based on their workflow statuses. This configuration will define issue reports.

For eSignature enabled projects, Testcase PDF export includes details of approvals.

Execute custom commands as per your automation framework using QMetry Agent, without a need to provide details like Project Path, Result file Path, Framework or Build in the Test suite. Read the difference here.

Schedule automation executions using Automation Agent with support to set recurrence.

Test executions are differentiated as Automated/Manual. Test suites are no more differentiated as automated or manual.

The API response for Get Info Service is changed, till v8.4.1 the response included data for all the projects from v8.4.2 the response would include data for a single project.

The API request & response for Get Requirement Folders under a given folder is changed.

The API request & response for Get Test case Folders under a given folder is changed.

The API request & response for Get Test suite Folders under a given folder is changed.

Get List of Audit Logs

List Test cases for Bulk Operations

Get Test cases linked to a specific Requirement

Get Test cases linked to a specific TestSuite

Get Test Data Parameters in a Test case version linked to a TestSuite

Get version details of a Test case

List Requirements for Bulk Operations

Get Requirements linked to a specific Issue

Get R equirements linked to a specific Test Suite

Get Requirements linked to a specific Test case

Get version details of a Requirement

Get Issue linked to a TestCaseStep Run

Get Issue linked to a TestCase Run

Issue Trend Over Time

Issue Open Vs. Closed - Cumulative

Issue Velocity compared to Test Cases executed

Issue Velocity compared to Requirements

Issue Leakage Rate

Issue Re-Open Rate

Introduced E-signature based approval workflow for testcase authorization and test execution

Enterprise reporting capabilities allows to generate custom matrices based on organization testing process

Enterprise teams practicing Behavior-Driven Development (BDD) can author, store and sync features files directly to/from Version Control Systems (VCS) like SVN, Git and Bitbucket, using the built-in Gherkin editor in QMetry requirements. The two-way syncing between QMetry & VCS keep developers, testers and product owners up-to-date with the latest source code change commits with automated step definitions. Using QMetry automation agents, test executions could be trigged directly from QMetry. Test cases are smartly created/reused authored based on the feature step definitions and link them to requirements. Test Suite stores the automation execution results ensuring complete feature traceability with requirements.

Enhance reusability and save effort on creating duplicate test assets by sharing test cases/requirements/issues across projects.

Test data parameterization allows testers to execute same test case multiple times with different data inputs; without having to create duplicate test cases. Test Data parametrization allow QA teams to store reusable test data in one centralized location, Import existing parameters and data sets & share data across QMetry projects.

Record sessions using inbuilt exploratory testing capabilities that allow testers to capture screenshots of any content without ever leaving your browser window. Communicate feedback clearly with easy-to-use annotation tools, audio recordings, auto capture details of environment and ensure nothing slips through the cracks while raising bugs. Create test cases directly from sessions without taking efforts to author them manually.

Quick in place editor on detail screens for all test assets.

Save duplicate efforts on managing folder structure by cloning them across modules.

Efficiently manage folders & assets with easy move & copy options.

Ensure coverage completeness & cut time spent on linking testcases manually to test suites by creating Test suite directly from requirement/requirement folder/testcase/testcase folder

Creating testcase directly from requirement helps by copying data for common fields.

Download all attachments of a test asset in a single click.

Easy management of attachments at entity level instead of versions.

Export Test cases details in elegant pdf format.

Reuse custom fields and Platform attribute across projects and modules

Organize requirements synced from Jira to QMetry in folder structure e.g based on sprints, modules, components, features etc

Manage Jira-QMetry fields mapping separately for requirements and issues

Remove Jira integration now allows to retain test assets synced by converting them to QMetry internal assets

150+ open API's to integrate external tools with QMetry. Revised Swagger documentation with ability to track changes between versions.

Easily sequence testcases in a test suite by drag/drop or move options.

Quick search on menu to reach the desired option.

Simplified menu options for quick navigation.