New & Noteworthy for IBM Engineering Test Management 7.0

	Description
Clustering	Quality Management clustered environment You can now set up a clustered environment to host a Jazz™ Team Server and multiple Quality Management (QM) WebSphere Liberty nodes. The QM applications must be installed on multiple WebSphere Liberty servers and connected by using an MQTT broker, which enables synchronization across the nodes. A load balancer is used as a front-end URL, which accepts connections and distributes the requests to one of the back-end QM nodes. The host name of the load balancer is used as a public URL for the QM applications during setup. To install the Quality Management applications in a clustered environment, see the Interactive Installation Guide .
Custom attributes	Custom attributes: New custom attribute of type Text (Large) New custom attribute of type Text (Large) A new custom attribute of type Text (Large) has been added to all of the artifacts that support custom attributes. The custom attribute of type Text (Large) allows users to enter up to 32 KB of data in the custom attribute field. The custom attribute of type Text (Large) does not support the sorting and filtering capability in table views.
	New custom attribute of type Link A new custom attribute of type Link has been added to all the artifacts that support custom attributes. You can now enter an URL and display text for any resource in the custom attribute field. You can add a single resource link for each custom attribute of type Link. You can also sort and filter the display text of the links in table view.
	New manual step attribute of type rich text A new custom attribute with the rich text type is now available for manual step attributes. With this custom attribute you can add a rich text column in the Manual Steps section of the test script editor. By using the new custom attribute, you can enter XHTML data in the attribute field. However, in the Manual Steps table view, you can’t filter rich text attributes.
Execution	Add test case categories and test case attributes as sections during test case execution You can now include the test case categories and test case attributes as sections during the execution of a test case without a test script. By default, the sections are not available on the result page. To add the corresponding sections above the Result Details section, under the Execution Preferences section, select the following system properties: Display the test case categories in an online test case execution without a test script Display the test case attributes in an online test case execution without a test script Click the section titles to collapse the required sections on the result page.
	Improved performance when running test suites The product now supports 500 command-line adapters. You can run a test suite of 2000 test cases by using 500 adapters in parallel mode. For details, go to the Engineering Test Management (ETM) Adapter Deployment Guide.
	Optimized scheduling and distribution of automated tests among the available adapters Until now, Engineering Test Manager distributes test cases in a parallel test suite to the available adapters in advance, before the execution of the first test case starts. The scheduling is based on a round-robin algorithm and doesn’t consider the length of each test case. Because of this approach, test resources might not always be efficiently used; some adapters might end up processing only short running test cases, while others process only long running test cases. This imbalance leads to unnecessarily long test case execution. Three new project properties in the Automated Test Preference section help you optimize adapter utilization. Image of the new automated test preferences: Select the adapter for an automated test case execution based on the estimate of the associated automated test case execution record and work allocated to the adapter: This option enables you to assign adapters based on the load. Instead of calculating the number of tasks (TCERs) to be assigned to an adapter, the load is now calculated based on the estimated time required to execute all assigned tasks. After an automated test case execution has passed, set the estimate of the associated automated test case execution record with the total run time of the test case result: This new project property sets the estimate for the test case execution record. For the new solution, it is important to have estimates for the test case execution records. After an automated test case execution record is created, set the estimate of a new automated test case execution record to the total run time of the last passed test case result for the test case and the test script combination: If this property is enabled, the product searches the latest passed result for the test case and test script combination. It uses the run time of that result as the estimate for the new test case execution record.
	Show test case and TCER categories in Test Case Results table view Show test case and TCER categories in Test Case Results table view You can now add test case and test case execution record (TCER) categories as columns in the Test Case Results table view. The columns display category values of a parent test case and TCER that is linked to the test case result. You can filter, sort, and group the test case results by using test case and TCER category columns. You can also filter the test case results by test case and TCER category values by using the Filter By view. These actions allow you to organize the test case results with their parent artifacts.
	Show test suite and TSER categories in Test Suite Results table view Show test suite and TSER categories in Test Suite Results table view You can now add test suite and test suite execution record (TSER) categories as columns in the Test Suite Results table view. The columns display category values of a parent test suite and TSER that is linked to the test suite result. You can filter, sort, and group the test suite results by using test suite and TSER category columns. You can also filter the test suite results by test suite and TSER category values by using the Filter By view. These actions allow you to organize the test suite results with their parent artifacts.
	When duplicating test plans or test cases, include related test case execution records with or without test case results When you duplicate test cases or test plans within or across projects, you can now include test case execution records with or without the related test case results: For test cases: In the duplication dialog box, select Include links to duplicates of the test artifacts that the original artifacts link to and specify which execution records to include. For test plans: In the duplication dialog box, select Include test case execution records and specify which ones to include. When you duplicate test case results, only the latest one is copied. If a test case execution record is linked to a test plan, this record and the test case results are not copied when you duplicate the associated test case. When you duplicate test case results across the project, if the test environments for test case execution record and latest test case result are different in the source project, the test environment for test case in the target project is overwritten by the mapped test environment for test case execution record.
Installation	ELM launchpad reorganized The ELM launchpad has been reorganized as follows: The server Evaluation installation and Custom installation sections contain updated guidance on planning installations for multiple server topologies. A section has been added for the Document Builder application. A section has been added to help users find additional download content (.zip files and other non-Installation Manager artifacts) for several ELM products. The version of Installation Manager bundled with the launchpad in the ELM web installer has been updated from 1.8.x to 1.9. Image of launchpad:
Licensing	API read-only access requires a Contributor license Users now require a Contributor license for read-only access to the ETM Reportable REST API and OSLC QM V2 API.
Mail notifications	Receive email notifications when test artifacts changed Artifact creators, owners, or subscribers can now receive email notifications for changes in test cases, test plans, test suites, or test scripts. To configure the notification, go to User Profile > My Preferences for Quality Management > Change notifications.
Offline execution	Add test cases to a test suite and run the test suite offline You can now add multiple test cases to a test suite and run the test suite offline. For offline execution, the test cases must have manual test scripts. You can select the test plan, test phase, iteration, test environment, and build information. After a successful execution, an RQMS file is generated. Download and save the file. To import the RQMS file to Microsoft Excel (XLS), use the Add-ins > Import for offline option. One test suite result and multiple execution results open in separate XLS sheets. Provide the result details and export the file back into the repository where you downloaded the RQMS file from.
	Execute test case offline from the Test Cases section of a test plan or test suite You can now select a test case from the Test Cases section of a test plan or test suite and execute it offline. The test case should have manual test scripts assigned to it. Only single test case offline execution is supported from the section. If you select multiple test cases, the Run Offline button is disabled.
	Export multiple TCERs to a server in a single user operation You can now run multiple manual test case execution records (TCERs) offline. After the TCERs are executed, an RQMS file is generated. You can import the RQMS file into a Microsoft Excel spreadsheet, where all of the test case results are added to different sheets. You can also export the results to a server in a single operation.
	Include preconditions and post-conditions in offline execution of test case or TCER The rqms file that is generated from a test case or test case execution record now includes preconditions and post-conditions. The preconditions state the conditions that must be met before the test is executed. The post-conditions state the conditions that must be met after the test is executed and before the result is saved or exported to a server. After an rqms file is imported into an Excel spreadsheet, two new non-modifiable fields are added to the spreadsheet to display the preconditions and post-conditions.
	Offline execution support for test cases without test scripts You can now execute a test case offline without linking it to a test script using the new scriptless execution capability. Earlier, the offline test case execution was available only when a test script was linked to the test case. The user interface for generating the RQMS package and importing the package to Microsoft Excel is identical to the earlier offline execution sequence. The generated .xls file for scriptless test case execution is different. The Test Description, Pre-Condition, Expected Results and Post-Condition sections are read-only but you can edit the Result Details section. You can also update weight distribution, start time, end time and the overall result before exporting the .xls file to the server. Offline execution does not work for a test suite that includes test cases with no associated script. The option is disabled in the user interface.
	Select build information for offline execution of test case or TCER You can select build information for offline execution of a test case or test case execution record (TCER). For test case offline execution, you can select build information from the test case editor view and table view. For TCER offline execution, you can select build information from the TCER editor view, table view, table view of a test case, table view of a test plan, and table view of a test suite execution record.
OSLC integrations	Create, modify, and delete test script step results by using OSLC QM V2 API Create, modify, and delete test script step results by using OSLC QM V2 API You can now use the OSLC QM V2 API to create, modify, and delete test script step results. You can modify the following attributes when you create or modify a test script step result: Actual Result Affected By Defect Attachment Comment Compare Custom Attribute Description End time Expected Result Related Change Request Step type Step verdict Tested by
Process templates	New SAFe 4.6 process templates You can now use the following new Scaled Agile Framework (SAFe) process templates for creating a project area: Quality Management for Essential SAFe 4.6 Quality Management for Full SAFe 4.6 The Quality Management for SAFe 4.0 process template is deprecated and not available for creating a new project area. You can still use the template for existing project areas.
Product name change	Rational Quality Manager was renamed In this release, IBM Rational Quality Manager was renamed to IBM Engineering Test Management (ETM). For details, see Renaming the IBM Continuous Engineering Portfolio .
Reporting	ETM artifacts from deleted components, streams, and baselines are no longer in LQE and LDX When you delete a component, stream, or baseline, the delete events are published to the IBM Engineering Test Management (ETM) Resources (TRS 2.0) feed. LQE and LDX removes these artifacts to their repository. When you restore a previously deleted component, stream, or baseline, the create events are published to the ETM Resources (TRS 2.0) feed. LQE and LDX adds these artifacts to their repository. The deleted or restored events that are published are applicable for all artifacts that belong to the restored component, stream, or baseline. The event processing after a component, stream, or baseline is deleted or restored supports a server restart. For example, after the server restarts the internal processing of a deleted component, stream, or baseline resumes from where it left off. Note: The same behavior is currently supported while archiving and restoring project areas.
	Create reports on non-Quality Management artifacts with trace relationships to Quality Management artifacts You can now create reports in Report Builder using a LQE data source on non-Quality Management artifacts with trace relationships to Quality Management. For example, you can create reports on Architecture Management artifacts such as, architecture element with trace relationships to Quality Management artifacts such as, test case.
	Enable permissions to export to PDF and CSV format The ability to export to PDF and CSV format is now controlled by permissions in the Project Area editor > Permissions area. Users with these permissions can export the content in test artifact editors and table views to PDF and CSV format: Export to CSV: Enable this permission to allow users to export the content in test artifact table views to CSV format. Export to PDF: Editors: Enable this permission to allow users to export the content in test artifact editors to PDF format. Table views: Enable this permission to allow users to export the content in test artifact table views to PDF format.
	ETM TRS feed validation - simplified and consistent with other ELM applications The procedure for validating the Engineering Test Management (ETM) TRS feed is now consistent with other Engineering Lifecycle Management (ELM) applications. Administrators complete these easy steps: Go to the administration page at https://<server>:<port>/qm/admin, and click TRS Feed Validation in the top menu. Click Run full validation to compare all the artifacts in the ETM TRS feed against the artifacts in the repository. To validate only the artifacts that changed since last validation, click Validate. Note: To use the old TRS Validator that was available in the previous release, go to https://<server>:<port>/qm/TRSValidator. The instructions for using the TRS Validator are available in this topic.
	Manage skipped resources You can now see a list of Engineering Test Management (ETM) resources (TRS 2.0 data source) in the Lifecycle Query Engine (LQE) or Link Index Provider (LDX). The ETM application evaluates the resource list and determines possible skipped resources to track them in its own repository. You can use the page actions, sort, group, or filter options in the resource list. This process helps you manage skipped resources and provides you with actions to potentially solve the most common incidences or ignore resources completely. You can use the following actions for TRS 2.0 ETM feed to manage skipped resources: Retry resource: Publishes creation and deletion events for the feed. LQE and LDX are forced to do a retry for resources executing this action. This option is helpful for temporarily failing requests Ignore resource: Publishes a deletion event. LQE and LDX remove the failing resource from their repository until the resource is requested again by LQE or LDX. Remove skipped resource: Deletes the skipped resource from the ETM repository. The item is simply removed and is not displayed in the resource list (unless LQE or LDX unsuccessfully request the resource again). No events are published for this action. To access the Manage Skipped Resources page, click the Administration icon. Click Manage This Project Area and then select the Skipped Resources tab. The following image shows the skipped resources in the ETM application:
Usability enhancements	Customize the related information panels in test artifacts You can now customize what related information to include in your test artifacts. To select which related information panels to display in the artifact editor, go to User Profile > My Preferences for Quality Management > Related Information. You can choose not to display empty panels where links to the related artifacts can't be added. In the artifact editor, the title bar of the related information panels now provides the link count. If you have multiple pages of links, the navigation bar shows link indexes instead of page numbers. The Copied To section under the Copies panel also supports multiple pages of links. By default, there are several new panels of related information in the test artifact editor: Test Plan Editor: Related Blocking Defects* Test Case: Related Test Case Execution Record, Last Test Case Result, Related Blocking Defects Test Suite Editor: Related Test Suite Execution Record, Last Test Suite Result, Related Blocking Defects Test Script: Related Test Plans, Related Test Suites, Related Blocking Defects* Test Case Execution Record: Parent Test Plan, Parent Test Case, Related Test Suites, Related Test Scripts, Last Test Case Result Test Suite Execution Record: Parent Test Plan, Parent Test Suite, Last Test Suite Result, Related Blocking Defects, Related Defects Test Case Result: Parent Test Plan, Parent Test Case, Parent Test Case Execution Record, Related Test Suites, Related Test Scripts Test Suite Result: Parent Test Plan, Parent Test Suite, Parent Test Suite Execution Record, Related Defects Note: Panels that are marked with an asterisk (*) are by default not selected. Panels that duplicate the information in test artifact are by default not displayed.
	Customize your test artifacts to show linked defects You can now configure the related information section of your test artifacts to show linked defects. Go to User Profile > My Preferences for Quality Management > Related information, and select what to include in the related information for each test artifact. Now, you can display the related blocking defects for the following test artifact types: test plans, test cases, test case execution records, test suites, test scripts, and test suite execution records. Previously, only test case execution records could show related blocking defects. Similarly, you can now display the related defects in test case execution records, test case results, test suite execution records, and test suite results. Previously, only test case execution records and test case results could show related defects.
	New look for product and component banners The product banners for IBM Engineering Lifecycle Management (ELM) products and components are updated to align with IBM's open-source Carbon design theme. This modern theme provides a consistent look across IBM products. The login window is also updated, but still works the same way. If you extend the UI in ELM applications, you can learn more about the Carbon guidelines at https://www.carbondesignsystem.com/. Image of the product banner for IBM Engineering Test Management: Image of the login window:
	Quickly insert a keyword step in a manual script When you write a manual script, you can quickly insert a new keyword step by pressing Ctrl+Space in the description field of an existing step. In the search keyword field that opens, you can type text to find matching keywords. Keywords are matched by name and by tag. Use the arrow keys or the mouse to select which keyword to add for the new step. Image of the keyword search field:
	Undo the deletion of a category value When you edit an artifact's category, you can undo the action for a category value that is marked for deletion. In the category editor's Hierarchy view, you can view the category's values in the right panel. If you delete a value in that panel, a Restore action is available to undo the deletion. Image of the Restore action:
	Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.