Known issues

First occurrence: 7.0.3

Problem: The identifier property value of a resource is changed from the concept URI to UUID. UUID is the unique identifier representation of a resource.

First occurrence: 7.0.2

Problem: IBM Engineering Test Management (ETM) previously supported a legacy local work item provider, which was deprecated in the Rational Quality Manager 6.0 release and will be removed in a future release. In the ETM version 7.0.2, if a project area is using the legacy local work item provider, the following warning message is displayed on the header of the screen:

This project area is using a legacy local work item provider, Engineering Test Management (ETM) that is deprecated and will be removed in a future release. The IBM Rational ClearQuest Synchronizer integration with ETM is also deprecated as that requires ETM to act as a legacy local work item provider. For more information about supported work item providers, contact IBM Support.

Workaround: Contact IBM Support to learn about other supported work item providers.

First occurrence: 7.0.3

Problem: ETM previously supported a local work item provider, which was deprecated in the Rational Quality Manager 6.0. For more information, see Workarounds: Warning message for projects that are using the local work item provider (187807). The IBM Rational ClearQuest Synchronizer integration with ETM requires ETM to act as a work item provider, this integration process is also now deprecated. In this release, if a project area is still using the local work item provider, the following warning message is displayed on the header of the screen:

This project area is using a deprecated work item provider, which will be removed in a future release. The IBM Rational ClearQuest Synchronizer integration with ETM is also deprecated that requires ETM to act as work item provider. Contact IBM Software Support to learn about other supported work item providers.

Workaround: Contact IBM Software Support to learn more about the IBM Rational ClearQuest Synchronizer integration with ETM.

First occurrence: 7.0.3

Problem: Test phases are now published as root-level reference resources unlike earlier releases, where test phases were presented as inline resource for test plans, test case execution records, test suite execution records, test case results, and test suite results. Because of publishing test phases as separately referenced listed resources, test phases are no more editable directly in the associated resources. For example, until the ETM 7.0.3 release, it was allowed to send an update to a test plan, test case execution record, or test suite execution record to modify or create a new test phase since the test phase was part of the same resource.

First occurrence: 7.0

Problem: When you select the Run this suite in a sequence option in the Test Cases section of the test suite editor, and execute a Test Suite or Test Suite Execution Record using the Run Offline option, the test case result tabs in the spreadsheet might not be displayed in the same order as in the web UI when the related .rqms file is imported into Microsoft Excel using the ETM Excel Importer Utility.

First occurrence: 7.0.2

Problem: Some asynchronous tasks, such as CSV or PDF export are blocked when a large number of test artifacts are created or updated in a short period of time, such as bulk operation. This happens as all asynchronous tasks are consumed updating the Apache Lucene full text index.

Problem: You might encounter the following error while duplicating a large set of test artifacts:

ETM was unable to complete the duplicate.

This happens when copy job is not updated with the progress for a period of time, which exceeds the grace period time defined in the advanced properties for CopyJobReaper task.

Workaround: Increase the grace period in the ETM advanced properties.

First occurrence: 7.0

Problem: ETM Projects that contain a ‘+’ character in their names might not be reachable by using the project area alias when the ETM server is configured via proxies. Some external utilities, tools, and execution adapters that use project area alias might not work for these projects.

Workaround: You can connect the utilities and tools to the projects by using the project area item UUID instead of the project area alias or the project area name.

First occurrence: 7.0.2

Workaround: Refer to Configuration Management is enabled for a project area in ETM 7.0.2 after updating the OSLC Link/Attribute Mapping section of the project area for more information and work around.

First occurrence: 7.0.3

Problem: In Safari browser, when you drag an ETM test case and drop it on a RMM architecture element, there is no option to link them. This is diagnosed as a defect with RMM: 80335: [Simplified linking] DnD from ETM/EWM to RMM is not working.

First occurrence: 6.0.6.1

Problem: When you use the browser search feature in a manual test script editor, the search feature works only for the text in the test script steps that are displayed. It cannot find a text in the test script steps that are not displayed on the page.

Workaround: The scope of the browser search feature is to find all the text displayed on a page. To search for a text in the test script steps that are not displayed, scroll down to load the test script steps in the display before you use the browser search feature. To search for a text in the entire test script, scroll down to the last test script step.

First occurrence: 7.0.1

Problem: You can configure the project area to use team areas and a different timeline from the default project timeline. You can associate team areas with a specific timeline, and can scope the preconditions and follow-up actions by the iterations of that timeline. If you enable the project property of team areas and timelines, a test plan can be in a team area and timeline different from the project timeline. The generated test suite execution record (TSER) is associated with the timeline specified in the parent test plan. This problem is only applicable to the TSER of the test plan, which does not uses the project timeline.

You can start the execution of a TSER in the TSER list view, TSER section of the test plan editor, or the TSER editor. When you start the execution from the TSER editor, it uses the timeline of the project, instead of the timeline specified in the test plan. It also enforces the preconditions of the project timeline, instead of the preconditions of the timeline specified in the test plan.

Workaround: Start the execution of the TSER from the TSER list view or the TSER section of the test plan editor.

First occurrence: 7.0.1

Problem: The user preferences are loaded on startup. If the user preferences are corrupted and failed to load, the application is unable to proceed and a blank page is displayed.

Workaround: Contact IBM support to reset the user preferences to the default settings.

First occurrence: 7.0.2

Problem: If you perform a PUT request for any test artifact, with the following content in any rich text section, and then try to export the PDF of the test artifact, it fails. This happens because of the missing <table> tag in the XHTML content.

<div xmlns:”http://www.w3.org/1999/xhtml”>
              <div>
                  <tbody>
                         <tr>
                              <td>Test</td>
                         </tr>
                  </tbody>
               </div>
         </div>

First occurrence: 7.0

Problem: The property dcterms:subject is removed from Test Data Variable OSLC V2 resource shape as it was not representing the subject as stated in http://purl.org/dc/terms/subject, rather it was outlining a property which is not implemented nor supported.

First occurrence: 7.0.3

Problem: The property dcterms:description was removed from Test Policy resource for Test Plan because it was not including any information, instead, rqm_qm:testPolicyDescription which includes the description for the Test Policy within a Test Plan remained as-is. There is no direct impact for end users except the removal of an unused property from the shape and the resource.

First occurrence: 7.0.1

First occurrence: 7.0.3

Problem: The TRS validation returns “Missing artifacts in the feed” for test case execution result steps and they keep appearing even if you check the “Resolve problems” check box before the validation.

First occurrence: 6.0.6.1

Problem: Error is one of the supported states that is included in the Execution States project properties by default. The Error state can be set for the verdict of the step result. However, in the Weight Distribution section of the test case result or test suite result page, no slider controls are provided to adjust the weight for the Error state. A step result in the Error state remains unaccounted.

For example, a test script has five steps for a test case of weight 100. If one of the step results is in the Error state, the weight slider shows only 80 points as Attempted and distributed among passed, failed, and other execution states. In this case, 20 points remain unaccounted for the Error state.

First occurrence: 7.0.2

Problem: In PDF export of ETM, large tables with many columns might be unreadable. It does not support scrolling in large tables so the width of the table columns is shrunk to show all columns in the PDF document.

In the RichText editor, the tables created from the editor tool are formatted so that they can be resized for PDF export. For the tables that are copied from other sources, such as Excel, the format of the tables are preserved and the column width of the tables is not resizable. The tables with a fixed width and beyond the width of the PDF document is truncated. The server advanced property “Print in landscape Format” allows printing the PDF document in the landscape mode, which provides more width to the PDFs. Use the reporting tools, such as JRS, PUB, and Report Builder to print the PDF documents.

First occurrence: 7.0.1

Problem: The user is unable to run multiple test case execution records, when Quality Management > Perform Discovery > Run permission is not provided.

WorkaroundProvide the permission Quality Management > Perform Discovery > Run. This permission is required to run multiple test case execution records.

First occurrence: 7.0.3

Problem: IBM Engineering Test Management Mobile Application is deprecated for versions 7.0.1 and later. There were no new features or updates to the application in versions 7.0.1 and 7.0.2. The application is not available for versions 7.0.3 and later on jazz.net, Google Play Store, and Microsoft Store. For more information, see IBM Engineering Test Management Mobile Application WIKI.

First occurrence: 6.0

Problem: You cannot create a report from “Build Health” resource as the build definitions does not load on the ‘Create report’ page.

System is behaving as designed, Build Health report is an Engineering Workflow Management(EWM) report that is used to report against EWM builds. It is not intended to be used in Engineering Test Management (ETM).

Build Health report appears in ETM as it previously supported a legacy local work item provider, which was deprecated in the Rational Quality Manager 6.0 release. It will be removed in a future release. Build Health report will also be removed from ETM in a future release.