Known issues in Engineering Test Management 7.1

Workarounds

The following issues in this release have workarounds.

Unhiding the root level machine attributes do not reappear in the test environment of TCER generation

First occurrence: 7.0.2

Internal ID: 196204

Problem: If you hide the root level machine attributes that are set as test environment type. Though after unhiding, it doesn't reappear in the test environment list at the time of TCER generation. It includes the following attributes:

• Installed Software
• IP Interface
• L2 Interface
• Operating System
• Remote Connection
• Any Custom-made Root level Attribute that is set to test environment type

Workaround: Go to Manage Project Properties > Lab Resources and channel properties and unhide the root level attribute in the machine (listed in the problem statement). Go to Manage Project Properties > Test Plan Environment Types > Select the root level > Set Type. Click Ok and Save. If you use this method, the root level attribute appears in the test environment list at the time of generating TCER.

Context sensitive help links in the web UI do not work

First occurrence: 7.0.3

Internal ID: 194609

Problem: Contexts sensitive help links that appear throughout the web UI do not work as expected.

Workaround: To search for the help topics in the online help, click Help Contents or Getting Started on the Help menu on the page header.

An execution that starts from the Test suite execution editor might use the wrong timeline

First occurrence: 7.0.1

Internal ID: 194587

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 followup 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 that is different from the project timeline. The generated test suite execution record (TSER) is associated with the timeline that is specified in the parent test plan.

This problem is only applicable to the TSER of the test plan, which does not use 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.

Some asynchronous tasks, such as CSV or PDF export are blocked when many test artifacts are created or updated

First occurrence: 7.0.2

Internal ID: 194581

Problem: Some asynchronous tasks, such as CSV or PDF export, are blocked when many test artifacts are created or updated in a short time, such as a bulk operation. This happens as all asynchronous tasks are used for 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 exists, complete these steps:

1. Stop the Engineering Test Management server.
2. Reindex the Apache Lucene full-text index that uses the rebuildTextIndices repository tools command. For more information, see repository tools command to rebuild text indices.
   Note: This step might take an extended period based on the amount of data in the Engineering Test Management server.
3. Restart the Engineering Test Management server.

Increase the grace period of a CopyJobReaper task if you encounter issues when a large set of test artifacts is duplicated

First occurrence: 7.0.3

Internal ID: 194568

Problem: You might encounter the following error when you duplicate a large set of test artifacts: was unable to complete the duplicate. This error happens when a copy job is not updated with the progress for sometime. It exceeds the grace period time that is defined in the advanced properties for the CopyJobReaper task.

Workaround: Increase the grace period in the Engineering Test Management advanced properties.

Complete the following steps:

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

Unable to link the Engineering Test Management test case to a Rhapsody® Model Manager architecture element that uses the drag method in the Safari browser.

First occurrence: 7.0.3

Internal ID: 194562

Problem: In the Safari browser, when you drag an Engineering Test Management test case and drop it on a Rhapsody Model Manager architecture element, an option to add a link to them is not available. This issue is diagnosed as a defect with Rhapsody Model Manager: 80335: [Simplified linking] DnD from ETM/EWM to RMM is not working..

Workaround:

• Link that uses the drag method in other supported browsers. For more information, see: Linking test artifacts to requirements and development artifacts by using the drag-and-drop method.
• Link the Engineering Test Management test case to a Rhapsody Model Manager architecture element by using the copy-and-paste method. For more information, see: Linking test artifacts to requirements and development artifacts by using the copy-and-paste method.
• Link the Engineering Test Management test case to a Rhapsody Model Manager architecture element that uses the traditional method of selecting the target artifact with an OSLC picker dialog.

A blank page is displayed when you log in to an Engineering Test Management project area if the user preferences get corrupted.

First occurrence: 7.0.1

Internal ID: 194543

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.

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

First occurrence: 7.0.2

Internal ID: 194518

Internal ID: 194518

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 issue 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 that is 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.

Test Case execution order is not accepted when you run a Test Suite Offline

First occurrence: 7.0

Internal ID: 191963

Problem: When you select the Run this suite in a sequence option in the Test Cases section of the test suite editor and run a Test Suite or Test Suite Execution Record by 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 by using the Engineering Test Management Excel Importer Utility.

Workaround:

1. Create a PDF report in Engineering Test Management or an Lifecycle Query Engine-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.

Engineering Test Management projects that contain a plus sign (+) character in their names cannot be connected to external tools when the server is configured through proxies

First occurrence: 7.0

Internal ID: 190752

Problem: Engineering Test Management projects that contain a + character in their names might not be reachable by using the project area alias when the Engineering Test Management 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

Workaround: To connect the utilities and tools to the projects, use the project area item UUID instead of the project area alias or the project area name.

Configuration Management is enabled for a project area in Engineering Test Management 7.0.2 after the OSLC Link or Attribute Mapping section of the project area is updated

First occurrence: 7.0.2

Internal ID: 190122

Problem: This issue has the following variants:

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

Workaround: For more information, see Configuration Management is enabled for a project area in 7.0.2 after updating the OSLC Link/Attribute Mapping section of the project area.

Inconsistent encoding and decoding for Engineering Test Management Reportable REST API URLs with project aliases, external IDs, and query parameter values

First occurrence: 7.0.2

Internal ID: 189848

Problem: In the Engineering Test Management 7.0.2 release to centralize the encoding and decoding schemes to resolve issues due to the existing inconsistent encoding schemes, the x-www-form-urlencoded encoding scheme is applied on the project alias, external ID, and query parameter value that can be placed as a segment on the URL.

The change affects the following cases:

• Project area aliases with URL-reserved characters
• External IDs with URL-reserved characters
• Query parameter values

Workaround: When the project alias, external ID, or query parameter value is part of a URL parameter, the entire parameter value must be encoded as is often used in encoding the parameter value for HTML form submission through GET or POST by using the application or x-www-form-urlencoded W3 Forms content type.

For example, if you were using the following Engineering Test Management Reportable REST API URL to set the fields parameter in the Engineering Test Management 7.0.1 release or earlier:

https://<host>:<port>/<contextroot>/service/com.ibm.rqm.integration.service. IIntegrationService/resources/A+%2B+B/testplan? fields=feed/entry/content/testplan/testcase['https://<host>:<port>/<context root>/service/com.ibm.rqm.integration.service. IIntegrationService/resources/A+%2B+B/testcase/testcase2? oslc_config.context=_2QCggKblEeq_g_5OO_ryVA']

The Engineering Test Management Reportable REST API URL now must be constructed in the following way where the value of fields is x-www-form-urlencoded:

https://<host>:<port>/<contextroot>/service/com.ibm.rqm.integration.service. IIntegrationService/resources/A+%2B+B/testplan?fields=feed%2 Fentry%2Fcontent%2Ftestplan%2Ftestcase%5B%40href%3D%27https%3A%2F%2F <host>%3A<port>%2F<context root>%2Fservice%2Fcom.ibm.rqm.integration.service. IIntegrationService%2Fresources%2FA%2B%252B%2BB%2Ftestcase%2Ftestcase2%3 Foslc_config.context%3D_2QCggKblEeq_g_5OO_ryVA%27%5D

For more information, see Project Alias.

Note: All the Engineering Test Management Reportable REST API consumers, such as integrations and utilities, must validate, check, and possibly refactor the calls to the Engineering Test Management Reportable REST API based on the information that is provided in this workaround to determine the size and upgrade costs.

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

First occurrence: 7.0.3

Internal ID: 189152

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:
  • 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 oslc_qm:TestPlan resource property 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#".

Warning message for IBM® Rational® ClearQuest® Synchronizer integration for Engineering Test Management projects that are using the local work item provider

First occurrence: 7.0.3

Internal ID: 189126

Problem: Engineering Test Management previously supported a local work item provider, which was deprecated in Rational Quality Manager 6.0. For more information, see: Workarounds: Warning message for projects that are using the local work item provider . The IBM Rational ClearQuest Synchronizer integration with Engineering Test Management requires Engineering Test Management 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  Synchronizer integration with  is also deprecated that requires  to act as work item provider. Contact IBM Software Support to learn about other supported work item providers.

Warning: This warning message cannot be dismissed.

Workaround: For more information, see Integrating Engineering Test Management and ClearQuest.

Browser search does not work with the manual test script editor

First occurrence: 6.0.6.1

Internal ID: 189098

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 that is 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 text in the entire test script, scroll down to the last test script step.

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

Internal ID: 188836

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 longer editable directly in the associated resources. For example, until the Engineering Test Management 7.0.3 release, you were able 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 because 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

Engineering Test Management projects that contain a plus sign (+) character in their names cannot be connected to external tools when the Engineering Test Management server is configured via proxies

First occurrence: 7.0

Internal ID: 188234

Problem: Engineering Test Management Projects that contain a + character in their names might not be reachable via the project area alias when the Engineering Test Management 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: The following utilities and tools are connected to these projects via the project area item UUID instead of project area alias or project area name:

• URL Utility
• Reportable REST API
• Copy Utility
• Copy Project Properties Utility

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

First occurrence: 7.0.2

Internal ID: 187807

Problem: IBM Engineering Test Management 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 Engineering Test Management 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,  that is deprecated and will be removed in a future release. The IBM Rational ClearQuest Synchronizer integration with  is also deprecated as that requires  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.

Execution Status by Iteration that uses TCER Count widget reports incorrect test case results count when you select the multi-valued test case categories

First occurrence: 6.0.6.1

Internal ID: 187606

Problem: The Execution Status by Iteration using TCER Count (Live) widget reports execution status based on various parameters, such as Test Plan, Iteration, Test Environment, Test Case, Test Case Category Type, and Test Case Category Name. If you select a multivalued test case category, the Execution Status by Iteration using TCER Count (Live) widget shows a wrong execution status because the Count is calculated incorrectly.

Workaround: When you select a multi-valued test case category, do not use the Execution Status by Iteration using TCER Count (Live) widget. Instead, complete the following steps to build a report in the Jazz® Reporting Service Report Builder component:

1. Open the Choose data tab.
   1. Choose a report type by using the following steps:
      1. Set Data source as Lifecycle Query Engine.
      2. Select the Current Data (table or graph) radio button.
      3. Click Continue.
   2. Limit the scope by using the following steps:
      1. Select the Project name.
      2. Click Continue.
   3. Choose an artifact by using the following steps:
      1. Select the QM Test Plan under the Quality Management section.
      2. Click Continue.
   4. Trace relationships and add artifacts by using the following steps:
      1. Add the following relationship:

         QM Test Plan > Reported By > QM Test Execution Record > Current Test Case Result > QM Test Result.

      2. Select the Enable multiple paths or add other source artifacts checkbox.
      3. Add an artifact of the QM Test Plan: QM Test Plan > Reported By > QM Test Execution Record > Test Schedule > Test Phase.
      4. Click Continue.
   5. Set conditions by using the following steps:
      1. Select attributes of the QM Test Plan.
      2. Choose the ID attribute.
2. Go to the Format Results tab.
   1. Go to the Table section.
      1. Remove all the existing rows.
      2. Add the Iteration attribute from Test Phase.
      3. Add Calculated Value for Test Result's supported status by using the following steps:
         1. Choose a calculation as Count of number of artifacts.
         2. Choose all or Limit.
         3. Choose an attribute such as Status.
         4. Choose limiter values as status is and select the value. For example, to add the Blocked status column, choose com.ibm.rqm.execution.common.state.blocked.
         5. Rename the added column as required. For example, rename com.ibm.rqm.execution.common.state.blocked as Blocked.
   2. Go to the Graph section.
      1. Change the chart title as TCER count.
      2. Change the Y axis as Iteration.
      3. Change the X axis as Count.
      4. Select Add lines or bar segments from numeric measures and select all status.
      5. Click Continue.
3. Go to the Name and Share tab.
   1. Specify your Reportname.
   2. Set Default visualization as Graph.
   3. Click Save.

Export Details and Export Comprehensive options of the Export PDF menu for test plans utilize a large amount of server memory

First occurrence: 6.0

Internal ID: 187121

Problem: Test plans are associated with test cases. The test plans might also be associated with test suites, test case execution records, test suite execution records, test case results, and test suite results. When you select the Export Comprehensive option from the Export PDF menu for a test plan, the PDF export job includes all the associated artifacts for comprehensive exporting. The output files are merged into a large PDF file. This export job consumes a large amount of server memory that can cause out-of-memory exceptions.

A similar problem can also occur when you select the Export Details option from the Export PDF menu for a test plan.

Workaround: To avoid consuming the critical amount of server memory, you can use any of the following methods:

• Disable the PDF export details and PDF Export Comprehensive options of the Export PDF menu in the Artifact Export Preferences section under the Manage project Properties > Properties tab.
• Increase the memory for the Java™ virtual machine (JVM).
• Before you select the Export Details or Export Comprehensive option from the Export PDF menu for a test plan, check the number of test artifacts that are associated with the test plan.
  Note: During internal testing, it was found that IBM Engineering Test Management supports the Export Comprehensive option of the Export PDF menu for test plans that are associated with a maximum of 160,000 test artifacts when 8 GB or more of the JVM memory is available.

Execution Status by Owner that uses Weight (Live) widget reports incorrect weight values when you select the multivalued test case categories

First occurrence: 7.0

Internal ID: 186479

Problem: The Execution Status by Owner using Weight (Live) widget reports execution status based on various parameters, such as Test Plan, Iteration, Test Environment, Test Case, Test Case Category Type, and Test Case Category Name. If you select a multivalued test case category, the Execution Status by Owner using Weight (Live) widget shows a wrong execution status because the Weight is calculated incorrectly.

Workaround: When you select a multivalued test case category, do not use the Execution Status by Owner using Weight (Live) widget. Instead, use the Execution Status by Points widget, which works on saved queries. The Execution Status by Points widget shows the correct execution status, even if you select a multivalued test case category.

To create a query, complete the following steps:

1. Go to Execution > Browse > Test Case Execution Records.
2. Click the Change column display settings icon.
3. Select the query parameters that you want, such as Test Plan, Iteration, Test Environment, Test Case, and the name of a test category that is defined in the Manage Project Properties > Artifacts Categories page.
4. Click the Save icon.
5. Select Query Type as Shared and click OK.

To configure the Execution Status by Points widget for a project, complete the following steps:

1. Go to the project dashboard and add the Execution Status by Points widget.
2. Click Select test artifact query.
3. Select a Project from the available project areas.
4. Select Test Case Execution Record from the Artifact type list.
5. Select a Query from the available shared queries.
6. Select Owner from the Grouping attribute list.
7. Click OK.

Deleting the default component configuration of a project causes major issues in Engineering Test Management

First occurrence: 6.0.3

Internal ID: 183707

Problem: Deleting the default component configuration of a project causes the following major issues in Engineering Test Management:

• IBM Engineering Workflow Management cannot be integrated.
• Execution adapters, such as the Command Line Adapter, cannot be connected.
• Utilities, such as the Engineering Test Management Copy Utility and Engineering Test Management Excel Importer Utility, failed to operate.
• The OSLC API service provider document cannot be resolved (404 Not Found).
• Engineering Test Management resources are not displayed in the Report Builder when you select the configuration-management-enabled Lifecycle Query Engine data source and configuration-management-enabled project to generate a new report.

Workaround: The deleted default component configuration can be restored to resolve these issues. Also, complete the following steps to display Engineering Test Management resources in the Report Builder:

• Update the configuration, for example, change the description, which is required for Rational Quality Manager 6.0.6.1 and earlier versions
• Run Reset Etags in the TRS Console.

Note: This workaround does not work for existing configuration-management-enabled projects where the default component configuration was scrubbed.

A test suite snapshot might fail if the Engineering Test Management process contains obsolete configuration

First occurrence: 7.0

Internal ID: 183289

Problem: When you create snapshot of a test suite, the action might fail if there is an obsolete process configuration. An error message: The participant com.ibm.rqm.execution.service.snapshotTestSuiteExecutionRecords is not valid for the operation com.ibm.rqm.planning.testsuite.snapshot might be displayed.

Workaround:

Complete these steps:

1. Connect to Engineering Test Management project area that uses Eclipse client.
2. Open the project area.
3. Select the Process Configuration Source tab.
4. Search for <operation id="com.ibm.rqm.planning.testplan.snapshot">.
5. Below that search for <followup-action description="Includes Test Suite Execution Record in Test Suite Snapshots" id="com.ibm.rqm.execution.service.snapshotTestSuiteExecutionRecords" name="TSER Snapshot Inclusion"/>
6. Delete the followup-action element.
7. Save the change.

The Engineering Test Management data source in Lifecycle Query Engine might register an invalid update when the Engineering Test Management server has a heavy load

First occurrence: 6.0.6.1

Internal ID: 180311

Problem: When the Engineering Test Management server is experiencing a heavy load, the Quality Management data source in Lifecycle Query Engine might register an invalid update.

Workaround: Complete these steps:

1. Using a JazzAdmin account, go to https://<server>:<port>/qm/trsConsole.
2. Click the resetEtags command.
3. Wait for Lifecycle Query Engine to apply the changes.

In Report Builder, the Is Blocked attribute is no longer available for the Test Execution Record artifact type

First occurrence: 6.0.6.1

Internal ID: 180199

Problem: When you generate reports in Report Builder, the IsBlocked attribute is no longer available for conditions or columns in reports on the Test Execution Record artifact type. The IsBlocked attribute is a Boolean flag that indicates whether the test execution record is blocked.

Workaround: When you create a report in Report Builder, complete these steps:

1. In the scope of the report, include the associated Change and Configuration Management (CCM) projects that contain defects that block test execution records.
2. Add the Blocked By Work Item relationship property to the Defect work item. Then, test execution records in the report with one or more defects are considered blocked.

When you remove a level in a nested numbered list, items are incorrectly reordered

First occurrence: 4.0

Internal ID: 180109

Problem: If you delete a level in a numbered list that has multiple levels, the items under the deleted level are incorrectly reordered

Consider the following example:

1. aaa
2. bbb
   • mmm
   • nnn
     1. xxx
     2. yyy
     3. zzz

If you delete all the entries in the second level, in this example a. mmm and b. nnn, so that the third level becomes the second level, the entries in the new second level are placed in the reverse order.

1. aaa
2. bbb
   1. zzz
   2. yyy
   3. xxx

Workaround: Complete these steps:

1. Delete all but one entry in the level that you want to delete. In this example, delete b. inn.
   1. aaa
   2. bbb
      1. xxx
      2. yyy
      3. zzz
2. Remove the remaining item from the higher level and change the style of the numbered list if needed.
   1. aaa
   2. bbb
      1. xxx
      2. yyy
      3. zzz

Some reports do not open when you click the widget header on the dashboard

First occurrence: 6.0.1

Internal ID: 180008

Problem: If you click widget header to open the report when the Tester Report using Weight or Tester Report using TCER count widgets are added to the dashboard, an error is displayed about a missing report descriptor. Clicking the widget header opens the report page in a detailed view. However, these two reports were deployed with an incorrect report descriptor, which causes the error.

Workaround: Complete these steps to update the report resources with the correct identifier:

1. Go to Reports > Report Resources.
2. Click Tester Report using Weight report, specify %testerWeight.Report ; for the identifier and save the report.
3. Click the Tester Report using TCER count report, specify tester.Report for the identifier, specify Tester Report using TCER Count for the report name, and save the report.

Snapshots of test plans with many test artifacts might cause an error

First occurrence: 6.0.5

Internal ID: 167270

Internal ID: 167270

Problem: When you create a snapshot of a test plan that has many test artifacts, an error message, such as 500: Unable to save snapshot for Test Plan, might be displayed. The snapshot might be created successfully, but the error can occur if the session times out with an HTTP proxy server.

Workaround: Increase the session timeout setting for the HTTP proxy server. In IBM Engineering Test Management, the default session timeout setting is 6 hours. Consider increasing the timeout setting for the HTTP Server to the same value.

TCERs cannot be generated for many test cases at one time

First occurrence: 4.0.5

Internal ID: 163894

Problem: If you have many test cases, such as more than 500, the following method of generating test case execution records does not work reliably:

1. Browse to Planning > Create test plan.
2. In the Test Cases section, add many test cases for example, 1000, and save the test plan.
3. Select all the test cases and generate test case execution records.

Workaround: Complete the steps for the application server that you use.

IBM WebSphere Application Server

1. Stop the CLM/QM server.
2. Set the following system property: maxParamPerRequest="1000000". . For more information about setting the system property, see Set up system property
3. Start the CLM/QM server.

Apache Tomcat

1. Stop the CLM/QM server.
2. Set the following attribute on the Connector tag in the Server.xml file: maxParameterCount="1000000". For more information about setting the attribute, see Set connector attribute.
3. Start the CLM/QM server.

Text in the editor might be displayed in a language that is not installed

First occurrence: 5.0

Internal ID: 163893

Problem: When you edit an artifact, some context menus, toolbar labels, and tooltips in the editor gets converted into the browser-preferred language, even if that language is not selected in IBM Installation Manager during installation. In IBM Engineering Test Management, The issue is encountered in these instances:

• In rich text sections of artifacts, such as the Test Case Design, Business Objectives, and Test Suite Design sections
• In custom rich text editor sections
• In execution steps when you run a test case execution record

This issue occurs because the editor provides its own language pack. If the matching language version is available, the editor is displayed in the user’s language. If not, the editor is displayed in the default language, which is most commonly English.

Workaround: For consistently translated text in the editor, make sure that you select any required languages in IBM Installation Manager when you install the server. For an existing installation, you can modify the language selection in IBM Installation Manager.

The reconciliation with requirement collections fails with a timeout error

First occurrence: 5.0

Internal ID: 163892

Problem: This problem occurs only in environments where IBM HTTP Server is configured as a reverse proxy, typically in a cluster environment. In test plans in IBM Engineering Test Management, the reconciliation with requirement collections fails and responds with a server error. The reconciliation fails after a fixed period. In the details of the reconciliation failure, you might see one of the following error messages:

• Gateway Time-out The proxy server did not receive a timely response from the upstream server.
• Internal Server Error The server encountered an internal error or misconfiguration and was unable to complete your request.

This issue occurs because the editor provides its own language pack. If the matching language version is available, the editor is displayed in the user’s language. If not, the editor is displayed in the default language, which is most commonly English.

Workaround: In the plugin-cfg.xml file, within the <ServerCluster/> tags, set the ServerIOTimeout values to 0 so that the connection will not time out. For more information about the plugin-cfg.xml file, see the Editing the Web server plugin_cfg.xml file for idle standby and the Server cluster sections in Setting up servers for a basic high-availability configuration.

Problems opening the Engineering Test Management importer from Microsoft Excel or Microsoft Word

First occurrence: 5.0

Internal ID: 163891

Problem: In Microsoft Excel or Microsoft Word, when you try to open the IBM Engineering Test Management importer, the expected window might not open. This issue is related to the language setting of the computer. If the language is set to English, the importer works. In other languages, you might notice unexpected behavior, such as the importer window not opening.

This issue occurs because the editor provides its own language pack. If the matching language version is available, the editor is displayed in the user’s language. If not, the editor is displayed in the default language, which is most commonly English.

Workaround: Complete these steps:

Windows 7 operating systems

1. Open the Control Panel and click Clock, Language, and Region > Change location.
2. Change the format to English (United States).
3. Change the location to the United States.

Windows XP operating systems

1. Open the Control Panel and click Regional and Language Options.
2. Change the location to the United States.
3. Change the standards and formats to English (United States).

In the Reconcile Requirements wizard, filtering for requirements returns only results for requirements on the current page

First occurrence: 6.0.1

Internal ID: 163823

Problem: When you reconcile requirement collections in test plans and then filter for requirements, the filter returns results for only the requirements that are displayed on the current page.

Workaround: To filter on all available requirements, select one of the following options:

• For Number of Items Per Page, select Display all.
• Manually go through the pages in the table and perform the filter.

Work item queries that contain test artifact links cannot be created or edited in the Engineering Workflow Management Eclipse client

First occurrence: 6.0.1

Internal ID: 163821

Problem: Work item queries for Task-Review work items that contain test artifact links cannot be created or edited in the Engineering Workflow Management Eclipse client.

Test artifact links:

• Blocking Test Execution Record
• Related Test Case
• Related Test Script
• Related Test Suite
• Test Case
• Test Plan
• Test Suite
• Test Suite Result
• Test Case Result

Workaround: Create and edit the queries in the IBM Engineering Test Management web client https://<host>:<port>/<context root>/console/<project area name>#action=com.ibm.team.workitem.viewWelcome.

JUnit Selenium test scripts cannot be created or saved if the class path is larger than 1000 characters

First occurrence: 6.0.2

Internal ID: 163820

Problem: You cannot create or save a JUnit Selenium test script with a class path that is larger than 1000 characters.

Steps to reproduce the problem:

1. Browse to Construction > Create test script.
2. Change the test script type to JUnit Selenium.
3. Name the test script.
4. In the Test Class field, enter the Selenium test class name.
5. In the Classpath field, provide a value that is larger than 1000 characters.
6. Save the test script.

Workaround:

Complete the steps for the application server that you use.

IBM WebSphere Application Server:

1. Stop the CLM/QM server.
2. Set the following system property: Dcom.ibm.team.repository.service.internal. RdbRepositoryDataMediator.skipValidationOnSaveItemInTxn=true.

   For more information, see Setting generic JVM arguments in the WebSphere Application Server V8.5 Liberty profile.

3. Start the CLM/QM server.

Apache Tomcat:

1. Stop the CLM/QM server.
2. Set the following system property: Dcom.ibm.team.repository.service.internal. RdbRepositoryDataMediator.skipValidationOnSaveItemInTxn=true.

   For more information, see System Properties.

3. Start the CLM/QM server.

Permission is required to run multiple test case execution records

First occurrence: 7.0.1

Internal ID: 194700

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

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

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

First occurrence: 7.0.1

Internal ID: 192773

Problem: By default, the Quality Manager Library on jazz.net widget is in the project dashboard for the default Engineering Test Management 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 to the documentation link that is provided in Related Information.
• If the Quality Manager Library on jazz.net widget is not required, remove it from the dashboard.

Limitations

The following issues in this release that does not have workarounds.

Property rqm_qm:ApplicationSecurity will not include dcterms: description anymore

First occurrence: 7.0.3

Internal ID: 194768

Problem: The dcterms:description property was removed from the Test Policy resource for Test Plan because it was not including any information. Instead, the rqm_qm:testPolicyDescription 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.

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

First occurrence: 6.0

Internal ID: 194564

Problem: You cannot create a report from Build Health resource because the build definitions do not load on the Create report page.

The system is behaving as designed. The Build Health report is an Engineering Workflow Management report that is used to report against Engineering Workflow Management builds. It is not to be used in Engineering Test Management.

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

Table in Rich Text Editor is truncated when exporting a test artifact in PDF

First occurrence: 7.0.2

Internal ID: 194120

Problem: In PDF export of Engineering Test Management, 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 rich text editor, the tables that are 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 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 Print in landscape Format server advanced property 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.

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

First occurrence: 7.0.3

Internal ID: 192601

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.

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

First occurrence: 7.0

Internal ID: 190988

Problem: The dcterms:subject property is removed from the Test Data Variable OSLC V2 resource shape because 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 or supported.

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

First occurrence: 6.0.6.1

Internal ID: 189245

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.

IBM Engineering Test Management Word Importer Utility does not support the self-referential link syntax for configuration files

First occurrence: 6.0.6.1

Internal ID: 188084

Problem: IBM Engineering Test Management Excel Importer Utility supports the configuration syntax for creating self-referential links between test artifacts by assigning these test artifacts to use data that is already being used by the other test artifact. For example, the testcase.dc:title=testscript.dc:title configuration syntax creates a self-referential link between a test case and a test script. However, the Word Importer Utility does not support the configuration syntax for creating self-referential links.

Dropped features in the Engineering Test Management 7.0.2 release

First occurrence: 7.0.2

Internal ID: 187808

Problem: The following features are removed in IBM Engineering Test Management 7.0.2:

• Engineering Test Management HP Quick Test Professional (QTP) or HP Unified Functional Testing (UFT) Adapter

  HP QTP versions 9.0, 9.1, 9.2, 9.5, 10, and 11.0 and UFT versions 11.50, 11.53, 12.02, and 12.51 were marked as End-of-Life (EOL) or End Of Support (EOS) in July 2019. In the 7.0.2 release, Engineering Test Management ended the support for these adapters.

  Note: Both the QTP and UFT adapters are supported in previous versions of Engineering Test Management.
• Engineering Test Management HP LoadRunner adapter

  HP LoadRunner versions 9.1, 9.51, 11.5, and 12.50 were marked as End-of-Life (EOL) or End Of Support (EOS) in August 2019. In the 7.0.2 release, Engineering Test Management ended the support for this adapter.

  Note: The LoadRunner adapter is supported in previous versions of Engineering Test Management.

Any change in the keyword step result cannot be re merged to the test script associated with the keyword by comparing the keyword step results with the test script steps

First occurrence: 7.0.2

Internal ID: 187575

Problem: You can edit a manual step custom attribute during test case execution if the manual step custom attribute enabled in the test case result. If a keyword step contains such an editable custom attribute, you can edit it during test case execution or from the test case result editor. However, you cannot merge the changes back to the test script that is associated with the keyword by comparing it with the test script steps from the test case result editor.

Rich-text content is not imported into the web UI correctly by the Engineering Test Management Reportable REST API and the OSLC Engineering Test Management API

First occurrence: 6.0.6.1

Internal ID: 185986

Problem: Sometimes, rich-text content cannot be imported correctly into the web UI by using the Engineering Test Management Reportable REST API and OSLC Engineering Test Management API. The issue occurs when the windowtext color property is defined for rich-text content. The windowtext color property represents the system color and can be set to any color. By default, the windowtext color property is set to black.

This limitation applies to any utility that uses the Engineering Test Management Reportable REST API or the OSLC Engineering Test Management API. To export rich-text content when you use the Engineering Test Management Excel Importer Utility, the configuration file uses the rich text <Cell/column> keyword. See the following example:

This is a test

Image of rich-text content in a spreadsheet: 99317

Image of rich-text syntax in the configuration file: 99281

In the example, This is in the red color, and is a test. is in the black color, which is the default color of the windowtext color property. When the content is imported into the web UI, the entire content appears in the red color, This is a test.

The issue occurs because the windowtext color property is not correctly recognized by the CKEditor, which is the rich-text editor in the web UI. The CKEditor applies the color of the parent HTML element. Moreover, the CKEdtior cannot map the windowtext color property to a specific color because the default system color can be set to any color.

When duplicating test plan across the project, test environments are not getting mapped for the test plan in the target project

First occurrence: 7.0

Internal ID: 183794

Problem: Currently, cross-project test artifact duplication wizard does not offer test environment mapping for the test plan. While duplicating test plan across the project, test environments are not getting mapped for the test plan in target project.

Email notifications for formal reviews are not customizable

First occurrence: 6.0

Internal ID: 163904

Problem: The notification messages that are emailed to users when a formal review on a test artifact changes, such as when an approval or a comment is added, are not customizable. Specifically, on the Manage Project Area page, in the Mail Templates section, any changes to the default text for the following notifications are not included in the email messages that are sent: Approvals, Messages At Me, Work Item Aggregate Changes Notification, and Work Item Changed Notification.

When artifacts are merged from a baseline, some Accept section and Merge section operations are not supported

First occurrence: 6.0

Internal ID: 163901

Problem: When you merge artifacts from a baseline, some sections do not support the Accept section and Merge section operations. For more information about support for each artifact type, see the related tables.

The Disallow execution of test case execution record with blocking status precondition is only enforced from the UI

First occurrence: 6.0.1

Internal ID: 163898

Problem: The new Disallow Execution of Test Case Execution Record with Blocking Status precondition in the project area properties is enforced only when execution is initiated from the UI. When execution is initiated from a utility that uses the Rational Quality Manager Reportable REST API, the precondition is not enforced.

Rational Quality Manager Reportable REST API does not support team area process-level operations

First occurrence: 6.0.1

Internal ID: 163897

Problem: Process and permissions that are defined at the team level do not affect the Rational Quality Manager Reportable REST API behavior. For Rational Quality Manager Reportable REST API operations, all process and permissions operate at only the project level.

Test Statistics, Test Matrix, and Execution by Weight dashboard widgets do not display multiple-valued categories correctly

First occurrence: 6.0.1

Internal ID: 163896

Problem: If you group the Test Statistics, Test Matrix, or Execution by Weight dashboard widgets by a category that has multiple values that are associated with it, only the results for the first value are displayed. For example, consider a Test Phase category that has three values: Development Test, Integration Test, and User Acceptance Test.

The category values are assigned to seven test cases in the following way:

• Three test cases have both the Development Test and Integration Test values (the Development Test value is listed first)
• Two test cases have only the Development Test value
• Two test cases have only the Integration Test value

In this scenario, the results should show that each value is assigned to five test cases. However, because the widgets tabulate only the first value for categories with multiple values, the widgets show that five test cases contain the Development Test value, and only two test cases contain the Integration Test value.

Test data in a snapshot can change

First occurrence: 6.0.2

Internal ID: 163895

Problem: When you create a snapshot of a test script, the test data references in the snapshot are always the same as the current revision of the test script. So, if the current test script changes the reference to the test data, the change is also reflected in all snapshots. Likewise, if the values in the test data change, the changes are reflected in all snapshots. There is no workaround for this issue because the state of the test data is not captured at the time of the snapshot.

The guest Access feature is not supported

First occurrence: 6.0

Internal ID: 163331

Problem: The Guest Access feature enables guest access to secure resources by using a dedicated guest user. However, enabling the Guest Access feature and configuring a Guest Access user ID in the Advanced Properties causes several issues, for example, with browsing and editing test artifacts. Because of these limitations, Guest Access is not supported in Rational Quality Manager, which is presently known as IBM Engineering Test Management.

Name of SAFe® 6.0 Full & Essential templates are not translated for various locales

First occurrence: 7.1

Internal ID: 196542

Problem: When a new project area is created with any locale selected, the SAFe 6.0 template's name is not converted into the selected language. The name is shown in English, and the content in the SAFe template project is shown in the language of the selected locale. The affected locales are Chinese, French, Korean, Spanish, Russian, Italian, Portuguese, Chinese (Taiwan), and Chinese (Hong Kong S.A.R. of the PRC SAR China).