New & Noteworthy for IBM Engineering Test Management 7.0.2

From the ETM 7.0.2 release, a new Project Area Metadata viewer is now accessible that displays the metadata of all active project areas. The Project Area Metadata viewer displays the following metadata of all active project areas:

• Name
• Item ID
• Configuration Management
• Alias

For more information, see Project Area Metadata Viewer.

• Copy Link: Ctrl+C (Windows) or Command+C (Mac)
• Paste as link: Ctrl+Shift+V (Windows) or Command+Shift+V (Mac)

Until now, if a test artifact export operation failed due to permission issues when creating categories, the ETM Excel/Word Importer Utility showed an error message in the ETM Export dialog box without category names or category values.

Now, if a test artifact export operation fails due to permission issues when creating categories, the error message in the ETM Export dialog box shows the category names and category values. Also, the error message specifies the type of the category.

In ETM, you can customize the execution states under the Execution States section in the Manage Project Properties > Properties page. The following customization options are available:

• Edit the name of the execution states.
• Enable or disable the execution states.

Until the 7.0.2 release, you were able to customize execution states for test case results and test suite results.

From this release, the support is now extended to include the following enhancements:

• You can now customize execution states for the test script step results along with test case results and test suite results.
• You can now see the scope of the execution states under the Execution States section in the Manage Project Properties > Properties page. An execution state can have one of the following scopes:
  • Results (applicable for test case results and test suite results)
  • Step Results (applicable for test script step result only)
  • Results, Step Results (applicable for test case results, test suite results, and test script step results)
• You can now see the customized names of execution states in the following fields:
  • Execution schedule result
  • The following dashboard widgets:
    • Execution Status by Points
    • Execution Status by Number of Steps
    • Team Execution Status for Test Cases
    • Team Execution Status for Test Suites
    • Test Suite Execution Status
  • LQE-based reporting
• Changes are made in the resource shape of test results, test suite results, and test script step results to show the customized names of the following properties:
  • Points Blocked
  • Points Failed
  • Points Inconclusive
  • Points Passed
  • Points Deferred
  • Points Skipped
  • Points Perm Failed
  • Script Step Count Blocked
  • Script Step Count Deferred
  • Script Step Count Skipped
  • Script Step Count Failed
  • Script Step Count Inconclusive
  • Script Step Count Passed
  • Script Step Count Perm Failed
  • Number of Blocked Test Cases
  • Number of Deferred Test Cases
  • Number of Error Test Cases
  • Number of Failed Test Cases
  • Number of Incomplete Test Cases
  • Number of Inconclusive Test Cases
  • Number of Inprogress Test Cases
  • Number of Partially Blocked Test Cases
  • Number of Passed Test Cases
  • Number of Paused Test Cases
  • Number of Perm Failed Test Cases
• ETM Reportable Rest API now shows the customized labels of the test script step result verdict and execution schedule result.
• Allow steps to be skipped during manual test script execution is removed from the Execution States section in the Manage Project Properties > Properties page. Instead, the Skipped execution state is added. If you enabled the Allow steps to be skipped during manual test script execution property in the earlier ETM versions, the Skipped execution state is enabled after migration to the ETM 7.0.2 version.

While duplicating test case execution records or test suite execution records, the Duplicate Execution Records dialog box now shows an option to include or exclude test environments that are associated with the execution records. If you select the Include test environments option, test environments that are associated with the execution records are copied to the target test plan along with the execution records.

The option to include or exclude test environments has the following characteristics:

• The option is available for duplicating test case execution records and test suite execution records in the same project area.

• The option is enabled only when a test plan is selected in the Duplicate Execution Records dialog box.

• The Test Environments > Platform Coverage section of the target test plan is not updated with lab resources that are part of the copied test environments.

Until now, you could manually change the test scripts of a test suite step in the Run Test Suite dialog box during a test suite execution. You might change the test script of a test suite step in the following scenarios:

• You added a test script to a test case that was already added to the test suite.
• You archived a test script that was the default test script of a test suite step.
• You removed a test script from the associated test case and the test script was the default test script for a test suite step for that test case.
• You created an automated test script for a test case that was already added to the test suite. A manual test script that was associated to the test case was selected as the default test script for the test suite step. Then, you added an automated test script to the test case and wanted to run the automated test script during the test suite execution.

From ETM 7.0.2 Sprint 4, the following project properties are added under the Execution Preferences section in the Manage Project Properties > Properties page to take care of these scenarios:

• The execution preference, During a test suite execution, automatically select a test script that is associated with the test case if the user does not set a default test script enables ETM to automatically determine the default test script for a test suite step during the test suite execution in the following scenarios:
  • The test suite step does not have a default test script.
  • The existing default test script is archived or removed from the associated test case of the test suite step.

• The execution preference, During a test suite execution, automatically select an automated test script that is associated with the test case if the user sets a manual test script enables ETM to automatically select an automated test script as the default test script during the test suite execution if the associated test case contains both automated and manual test scripts, and you set a manual test script as the default test script for the test suite. The automated test script with the highest ID is selected as the default test script.

The IBM Engineering Test Management Adapter for UFT supports Micro Focus UFT One, versions 15.0 and 2021.
For more information on the new adapter, go to https://jazz.net/downloads/test-management/releases/7.0.2?p=allDownloads.

The ETM application now includes the Multi-component Technology Preview that enables test artifact relationships, such as linking and running tests across components in a configuration management enabled project area.

The following capabilities are provided in the Multi-component Technology Preview:

• To enable or disable this feature in ETM or a specific configuration management enabled project area.
• To view test artifacts from multiple components on the same page. For example, test cases from multiple components can be displayed in the Browse > Test Cases view.
• To create new test artifacts with a specific component.
• To create or delete links between test artifacts from multiple components. For example, the Test Cases section of a test plan can be used to add test cases from multiple components to the current test plan and view test cases from multiple components.
• To provide ETM Reportable REST API and OSLC QM API support of a multi-component context.
• To run tests with test artifacts that are linked to artifacts from multiple components.
• To display all the components in the current multi-component context.

Note: This feature is currently a technology preview and is not supported for use in a production environment. You must install the ELM applications on a dedicated server to use this feature.

For more information, see the Multi-component Technology Preview WIKI.

From the ETM 7.0.2 release, execution variables are now supported for test case and test suite offline executions. You can add artifact execution variables and project execution variables to test scripts, test cases, and associated test suites. The values can be modified in the Run Offline and Run Test Suite Offline dialog boxes.

The following changes are made in the ETM web UI:

• You can add execution variables to a test script that is intended for offline execution.
• You can add execution variables to a test case that is intended for offline execution.
• You can add execution variables to a test suite that is intended for offline execution.
• You can modify execution variables in the Run Offline and Run Test Suite Offline dialog boxes. The edited values in the Run Offline dialog box are processed for further execution. The generated execution package (.rqms file) contains information about the execution variables and their values.

In this release, changes are also made in the ETM Excel Importer Utility. After you import the execution package (.rqms file), the generated Microsoft Excel file (.xls) shows the execution variables and their values with the following options:

• For the execution step type, the variables are displayed inline with the step description. These variables cannot be modified.
• For the variable step type, the variables are displayed inline with the step description. The values of these variables can be modified from the editable cells.
• If a test suite has multiple test cases with associated execution variables, each of the sheets in the generated Microsoft Excel file (.xls) shows the associated execution variables.

For more information on different formats of the generated Microsoft Excel file (.xls) and limitations of using execution variables, see ETM Excel/Word Importer Utility.

You can now run a test suite offline with scriptless test cases. Earlier, the offline execution of a test suite was possible only when the test suite had test cases with test scripts.

You can add multiple test cases with or without associated test scripts to a test suite and run the test suite offline. After a successful execution, an RQMS file (.rqms) is downloaded.

To import the RQMS file (.rqms) into Microsoft Excel, select the ETM > Import for offline option from the Add-In menu. A Microsoft Excel file (.xls) is generated with one test suite result sheet and multiple test case result sheets. The result sheets have different attributes and properties for test case results with and without step results. You can update the start time, end time, overall result, step results, and weight distribution values for execution results without step results.

You can export the test results back to the server in a single user operation by selecting the ETM > Export to Repository option from the Add-In menu.

ETM supports customization of execution states for test case results and test suite results. You can customize the execution states under the Execution States section in the Manage Project Properties > Properties page. From the ETM 7.0.2 release, you can see the customized names of execution states in test script step results along with test case results and test suite results.

From this release, support is also extended to include the customized names of execution states in an offline execution package (.rqms file) when you run a test offline by using ETM Excel Importer Utility. You can see the customized names of execution states in the following sections of the generated Microsoft Excel file (.xls):

• Overall Result
• Step Result
• Weight Distribution

Note: The Skipped execution state is not supported for an offline execution.

After you export the result back to the ETM server, these customized values are updated in the result details.

The command-line and Selenium adapters now support a new type of authentication process to connect to IBM Engineering Lifecycle Management (ELM) applications that are configured for OpenID Connect (OIDC) authentication by using the Jazz Authorization Server (JAS).

You can use the new authentication process with the command-line and Selenium adapters to work in an environment that uses third-party identity providers, such as SAML or OIDC for authentication without any direct support for the protocol that is used by these identity providers. Instead, users receive an application password from JAS. The application password is generated by the configured third-party identity provider. For example, a user can select SAML with the two-factor authentication process and use the application password for authentication with the ELM applications.

With this new authentication process, the user must assign the existing command-line argument, -password and enter the application password instead of the user password.

ETM Excel/Word Importer Utility now supports a new type of authentication process to connect to IBM Engineering Lifecycle Management (ELM) applications that are configured for OpenID Connect (OIDC) authentication by using the Jazz Authorization Server (JAS).

You can use the new authentication process with the ETM Excel/Word Importer Utility to work in an environment that uses third-party identity providers, such as SAML or OIDC for authentication without any direct support for the protocol that is used by these identity providers. Instead, users receive an application password from JAS. The application password is generated by the configured third-party identity provider. For example, a user can select SAML with the two-factor authentication process and use the application password for authentication with the ELM applications.

With this new authentication process, the user must select the Username and Password authentication type in the Export to ETM information window and enter the application password in the Password field.

For more information on the available authentication types, see ETM Excel/Word Importer Utility.

From the ETM 7.0.2 release, you can see an improved status of OSLC Migration when you go to https://<host>:<port>/<context>/oslcMigrationManager (for example, https://myserver:9443/qm/oslcMigrationStatus).

You can now see the following new columns:

• Project Area: Name of the project area that is migrated, being migrated, or waiting to be migrated.
• Status: The current status of the project area, such as Complete, In Progress, or Not Started.
• Total Items Migrated: Total number of items that are migrated in the project area.
• Current Item Type: The item type that is being migrated.
• Items Migrated for Current Item Type: Total number of items that are migrated of the item type that is being migrated.
• Progress: The percentage value that is calculated based on the number of item types (for example, test plan, test case, and other types) in a configuration that are pending to be migrated in the project area. Some item types might take longer to migrate than other item types.
• Current Configuration: The configuration that is being migrated.

ETM stores the labels of owned remote links when the links are created. However, these labels become stale when the remote resources are modified. Owned remote link types include all remote link types in an ETM project area where configuration management is not enabled and remote link types that are owned by ETM in configuration management enabled project areas, such as Requirement Management (RM) links.

A new advance property, Resolve the latest labels of owned remote links in PDF, CSV, and REST API, is added in the ETM Integration Component section under the Server Administration > Advanced properties page. This property is disabled by default. When this property is enabled, the latest labels of the owned remote links are resolved from the remote application and used as the labels of the owned remote links in PDF reports, CSV exports, and ETM Reportable REST API responses. Otherwise, the existing labels of the owned remote links are used as the labels of the owned remote links in PDF reports, CSV exports, and ETM Reportable REST API responses.

The existing advance property, Enable resolving remote link labels for PDF, CSV, and REST API, is renamed to Resolve the latest labels of unowned remote links in PDF, CSV, and REST API. Its functionality remains same. This advance property is enabled by default. Unowned remote link types include remote link types that are not owned by ETM in configuration management enabled project areas, such as Change and Configuration Management (CCM) links. When this property is enabled, the latest labels of the unowned remote links are resolved from the remote application and used as the labels of the unowned remote links in PDF reports, CSV exports, and ETM Reportable REST API responses. Otherwise, the URLs of the unowned remote links are used as the labels of the unowned remote links in PDF reports, CSV exports, and ETM Reportable REST API responses.

Notes:

• A functional user association with the remote application is required to resolve the latest remote link labels.
• PDF reports, CSV exports, and ETM Reportable REST API responses take longer to resolve the latest remote link labels.

The Project Feed Service now supports fields filtering to easily resolve a project area based on the title or alias properties.

For more information, see Project Feed Service.

From the ETM 7.0.2 release, a readiness probe is available for ETM. This service can be used to determine if an application is ready to use.

For more information, see the Readiness probe wiki.

From ETM 7.0.2 Sprint 4, you can now archive baselines or streams when child streams or baselines have a dependency on these configurations. For example, if a parent baseline is associated with a child stream, you can now archive the parent baseline.

• DOORS Next
• Engineering Insights
• Engineering Test Management
• Engineering Workflow Management (including Rhapsody Model Manager)
• Global Configuration Management
• Jazz Team Server

• Access control scoping of users: Only the relevant users are shown as defined in the Access Control setting of the current project area. For instance, if read access is set to Members of the project area hierarchy, then you can see only project area and team area members in the search results.
• Recent users: In addition to the current user, you can access the 10 most recently selected users. However, in this release, the Recent list for quick access is limited to the current user.
• Managing multiple users: Existing users are preselected in the dialog box. You can add new users or remove existing users. Previously, the people picker only supported the addition of new users. Now, you can manage an existing selection set in a single step.