Release Notes 8.29.x

Test Case Run UDFs can now be configured as mandatory to ensure all required execution details are captured during execution. All mandatory fields must be filled in before the execution status of a test case or test step run can be changed, either individually or in bulk.

Defects created from the Test Execution screen during a test case or test step run now automatically include Test Case Run UDFs and their values in the defect description. This gives developers the complete execution context needed to review and reproduce the defect, and removes the need for testers to document these details manually.

Layout Management now supports configuring the position of Test Case Run UDFs on the Test Execution screen, allowing fields to be arranged according to workflow requirements.

Test Case Run UDFs are now displayed in the Test Case Execution section in JIRA and Azure DevOps, alongside other execution details. This gives integrated teams complete execution context in their chosen platform, eliminating the need to navigate to QMetry.

To ensure compatibility with QMetry 8.29.0, customers must use the following integration versions:

Execution exports in PDF, Word, Excel, and CSV formats now include Test Case Run UDF details, providing a more comprehensive view of execution data for reporting, review, and audit purposes.

Bulk execution from Test Suite > Test Execution now supports setting Test Case Run UDF values across multiple releases, cycles, and platforms in a single operation. This saves time on large test runs and makes it easy to fill in mandatory UDFs before updating execution statuses in bulk.

Excel and CSV re-imports of Test Run execution data now support Test Case Run UDF values alongside test case and test step execution statuses. This enables bulk updates to execution results and UDF values through a single import, simplifying offline updates and high-volume batch execution workflows.

The Test Case Run UDF icon now uses color coding to instantly show whether all mandatory UDFs are complete or whether any remain unfilled. This visual cue makes it easy to spot missing fields and complete them before changing the execution status.

Test Case Run UDFs must be configured as optional in projects integrated with Reflect to ensure successful automation imports. Mandatory Test Case Run UDFs are not supported with Reflect integration.

When importing automation test results, the Automation API now supports setting Cascading UDF values for newly created test cases, test suites, and imported test case runs. These values are set using the testcase_fields, testsuite_fields, and testrunudf parameters, which already support other UDF types.

PDF and Word export templates for execution details from the Test Execution section and the Test Execution screen are now optimized with improved compression, so exports complete faster and can handle a larger number of records.