New & Noteworthy for IBM Engineering Test Management 7.0.2 M4


Description
Administration New Project Area Metadata viewer for IBM Engineering Test Management (ETM)

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.

Execution New project properties to enable ETM to automatically determine the test script to be executed for a test suite step during a test suite execution

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 automated test script with the highest ID (when the associated test case contains both automated and manual test scripts) or the manual test script with the highest ID is selected as the default test script.
  • 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.
Integrations/ Excel & Word Import ETM Excel/Word Importer Utility shows error messages with category names and category values if the export operation fails due to permission issues when creating categories

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.

REST API Project Feed Service supports fields filtering

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.

Server Start Up New readiness probe for ETM

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.

Test Environment New option to copy associated test environments to the target test plan while duplicating execution records

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.

Usability Enhancements Archive streams and baselines with dependent configurations

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.

Web UI Smart people picker component

A new people picker component is now introduced as part of the ongoing user experience transformation and alignment with IBM's open source Carbon Design System. The people picker is a dialog box for selecting users and can be used for assigning an owner or a set of subscribers to an artifact.

The new people picker is common across the following applications:
  • DOORS Next
  • Engineering Insights
  • Engineering Test Management
  • Engineering Workflow Management (including Rhapsody Model Manager)
  • Global Configuration Management
  • Jazz Team Server
The following improvements are included over the classic people picker component:
  • 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 the current milestone, 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 addition of new users. Now, you can manage an existing selection set in a single step.
Note: The classic people picker component is not entirely replaced. You can still use it in the Administration UI, and for selecting users when querying and filtering because these use cases require access to all historical users.

Image of the classic people picker component:


Image of the new people picker component (single-user mode):


Image of the new people picker component (multiple-user mode):

© Copyright IBM Corporation 2020  |   Contact  |   Privacy Policy  |   Terms of Use