Jazz Library Workarounds and Limitations: Known issues in IBM Engineering Test Management 7.0.3
Author name

Workarounds and Limitations: Known issues in IBM Engineering Test Management 7.0.3

The following known problems are related to this release.

Workarounds

The following problems in this release have workarounds:

Limitations

The following problems in this release do not currently have workarounds:


Workarounds

Identifier property value does not contain the concept URI for the resources anymore


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.

Workaround
You can follow any of these ways to find the concept resource apart from the identifier property:
  • From the UI: Do the following steps:
    • Open the test artifact from where you want to know the concept resource.
    • Click Copy link for this page and select Copy concept resource.
  • From the OSLC API: Perform an OSLC GET for the resource and look for the resource property. For example, the resource property, oslc_qm:TestPlan, contains the concept link as it is the parent resource. Similarly, for the following resources, look for the parent representation:
    • Test plan: oslc_qm:TestPlan
    • Test script: oslc_qm:TestScript
    • Test script step: rqm_qm:TestScriptStep
    • Test case: oslc_qm:TestCase
    • Test case execution record: oslc_qm:TestExecutionRecord
    • Test case result: oslc_qm:TestResult
    • Test case step result: rqm_qm:TestScriptStepResult
    • Test suite: rqm_qm:TestSuite
    • Test suite execution record: rqm_qm:TestSuiteExecutionRecord
    • Test suite result: rqm_qm:TestSuiteResult
    • Build record: rqm_qm:BuildRecord
    • Build definition: rqm_qm:BuildDefinition
    • Keyword: rqm_qm:Keyword
    • Test data: rqm_qm_TestData
    • Test environment: rqm_qm:TestEnvironment
Note: oslc_qm=”http://open-services.net/ns/qm#” and rqm_qm=”http://jazz.net/ns/qm/rqm#“.


Related information
Work item 188060
Work item 188963

Back to top


Warning message for projects that are using the legacy local work item provider


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.

Note: This warning message cannot be dismissed.

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

Related information
Story 186848
Task 135518

Back to top


Warning message for IBM Rational ClearQuest Synchronizer integration for ETM projects that are using the local work item provider


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.

Note: This warning message cannot be dismissed.

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

Related information
Work item 189120

Back to top


Test phases are no longer published as inline resources for test plan, test case execution records, test suite execution records, test case results, and test suite results in the OSLC API


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.

Workaround
Use the new Test Phase OSLC API to create and update test phases. For other test artifacts, it is recommended to review the corresponding document shape to understand the following new structure:
  • For concept resources, the URI format: https://server:9443/qm/oslc_qm/contexts/Project_Area_UUID/resources/com.ibm.rqm.process.TestPhase/itemID
  • For versioned resources, the URI format: https://server:9443/qm/oslc_qm/contexts/Project_Area_UUID/resources/com.ibm.rqm.process.TestPhase/itemID/StateID
  • For resource shape, the URI format: https://server:9443/qm/oslc_qm/contexts/Project_Area_UUID/shape/resource/com.ibm.rqm.process.TestPhase
  • For resource shape create, the URI format: https://server:9443/qm/oslc_qm/contexts/Project_Area_UUID/shape/creation/com.ibm.rqm.process.TestPhase
  • For query shape, the URI format: https://server:9443/qm/oslc_qm/contexts/Project_Area_UUID/shape/query/com.ibm.rqm.process.TestPhase
  • For query shape for resources, the URI format: https://server:9443/qm/oslc_qm/contexts/Project_Area_UUID/shape/query/resource/com.ibm.rqm.process.TestPhase

Related information
For more information, see Explore having Test Phase embedded inside each TCER RDF representation (187386) and Test phases are now published as root-level reference resources (188799).

Back to top


Test Case execution order is not honoured when running a Test Suite Offline


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.

Workaround
1.
Create a PDF report in ETM or a LQE-based report in Report Builder of the test suite and its test cases.
2. Use this report along with the imported .rqms file to see the sequence of test cases in the Test Suite.


Related information

Work item 191650

Back to top


Some asynchronous tasks, such as CSV or PDF export are blocked when a large number of test artifacts are created or updated


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.

Workaround
Reduce the number of test artifacts that are created or updated in the period of time.

If the problem already exists, complete these steps:
1. Stop the ETM server.
2. Reindex the Apache Lucene full text index using the rebuildTextIndices repository tools command. For more information,  see repository tools command to rebuild text indices. Note that this step might take an extended period of time based on the amount of data in the ETM server.
3. Restart the ETM server.

Related information
Work Item 194505

Back to top


Increase the grace period of CopyJobReaper task if you encounter issues while duplicating large set of test artifacts.


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.

Complete the following steps:

1. Go to Administration -> Manage Application -> Configuration -> Advanced Properties.
2. Search for the term: com.ibm.rqm.copy.impl.CopyJobReaper.
3. Increase the ‘Current Value’ for ‘Grace Period’ property in increments of 100 seconds.

Back to top


ETM projects that contain a ‘+’ character in their names cannot be connected to external tools when the ETM server is configured via proxies


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.

The following utilities, tools, and execution adapters are affected because of the connection issue:
  • URL Utility
  • Reportable REST API
  • Copy Utility
  • Copy Project Properties Utility
  • Excel Importer Utility
  • Command-line adapter
  • JUnit Selenium adapter

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.

Related information
Work Item 188119

Back to top


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


First occurrence

7.0.2

 

Problem

There are two variants of this issue:

  • Variant 1: Configuration management disabled project areas with the OSLC Link/Attribute Mapping project property (Manage This Project Area >> Uncategorized >> OSLC Link/Attribute Mapping) updated in ETM 6.0 – ETM 7.0.1 are configuration management enabled after upgrading to ETM 7.0.2.
  • Variant 2: Configuration management disabled project areas created in ETM 7.0.2 are configuration management enabled after updating the OSLC Link/Attribute Mapping project property (Manage This Project Area >> Uncategorized >> OSLC Link/Attribute Mapping).


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.

Related information
Flash note

Defect 189874
Defect 537098

Back to top


Cannot link ETM test case to RMM architecture element using the drag and drop method in Safari browser


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.

 

Workarounds

 

Related information

194413: [Safari] DnD from ETM to RMM is not working.

Back to top


Browser search does not work with the manual test script editor


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.

Back to top


An execution starting from the Test suite execution editor might use the wrong timeline


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.

Related information
Work item 194582

Back to top


A blank page is displayed while logging into an ETM  project area if the user preferences get corrupted


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.

Related information
Work item 194381

Back to top


Invalid XHTML content in the Rich text editor causes PDF Export to fail


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>

Workaround

  • Fix the invalid XHTML content sent in the PUT request to include the missing <table> tag.
  • After performing the PUT request with the missing <table> tag, click the Validate Content button in the rich text editor before the PDF export, save the test artifact, and run the PDF report.

 

Related information

Work item 193156

Back to top


Limitations

The property dcterms:subject is no longer published for Test Data Variable in the OSLC API

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.

Related information

Defect 190702 

Back to top


Property rqm_qm:ApplicationSecurity will not include dcterms:description anymore

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.

Related information

Work item 192538

Back to top


Warning messages are displayed in the “Quality Manager Library on jazz.net” dashboard widget



First occurrence
7.0.1

Problem
By default, the “Quality Manager Library on jazz.net” widget is in the project dashboard for the default ETM process template.  The following warning messages are displayed when there is no access to jazz.net:
  • There was a problem loading the feed.
  • The content was not a recognized feed.
  • The requested resource is not available on the approved list of external resources.
Workaround
Perform one of the following steps:
  • Configure the external resources allowlist to add on jazz.net.  For instructions, refer the documentation link provided under Related Information.
  • If the “Quality Manager Library on jazz.net” widget if not required, remove it from the dashboard.
Related information
Security considerations for the IBM Engineering Lifecycle Management applications – IBM Documentation (topic “Setting up allowlists to prevent SSRF attacks”)
Work item 192093

Back to top


Warning messages are displayed in the “Quality Manager Library on jazz.net” dashboard widget



First occurrence
7.0.1

Problem
By default, the “Quality Manager Library on jazz.net” widget is in the project dashboard for the default ETM process template.  The following warning messages are displayed when there is no access to jazz.net:
  • There was a problem loading the feed.
  • The content was not a recognized feed.
  • The requested resource is not available on the approved list of external resources.
Workaround
Perform one of the following steps:
  • Configure the external resources allowlist to add on jazz.net.  For instructions, refer the documentation link provided under Related Information.
  • If the “Quality Manager Library on jazz.net” widget if not required, remove it from the dashboard.
Related information
Security considerations for the IBM Engineering Lifecycle Management applications – IBM Documentation (topic “Setting up allowlists to prevent SSRF attacks”)
Work item 192093

Back to top


TRS validation returns incorrect results for test case execution result steps



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.

Related information
See defect 193351

Back to top


The Error state is not included in the Weight Distribution section of the execution result

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.
 
Related information

Back to top


Table in RichText editor is truncated when exporting a test artifact in PDF



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.

Related Information
Work item 193015

Back to top


Permission is required to run multiple test case execution records



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.

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

Back to top


IBM Engineering Test Management Mobile Application is not available for versions 7.0.3 and later


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 .

Related information

Work Item 192320

Back to top


Creating report from “Build Health“ resource does not load build definitions

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.

 

Back to top


Thu, 05 Oct 2023