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

• You can create and use the Lifecycle Query Engine (LQE) based reports since LQE-based reports show the customized names of the execution states.
• Use the following dashboard widgets that show the customized names of the execution states:
  • Execution Status By Points
  • Execution Status By Number Of Steps
  • Test Artifact
  • Test Statistics
  • Test Matrix
  • Team Execution Status for Test Cases
  • Team Execution Status for Test Suites
  • Test Suite Execution Status

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

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

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

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

You cannot open a test case execution record when the associated test plan is restored from the archived state

• A test case execution record is associated with a test plan and iteration.
• The test plan is archived after you created a test case execution record.
• The test plan is restored.

1. Open the Test Schedules section in the test plan.
2. Click Clear to remove all the test schedules from the test plan and save the test plan.
3. Add the test schedule again and save the test plan.

Deprecated features in 7.0.1

• TRS 1.0 API

The TRS 1.0 API is deprecated and replaced by the TRS 2.0 API. For more information, see TRS 1.0 API.

• ETM Reportable REST API

The remotescript (non-manual test script) and testscript (manual test script) resource types are deprecated.
The workitem (work item) resource type is deprecated and replaced by Engineering Workflow Management. For more information, see Rational Team Concert 3.0 SDK.

• OSLC Automation API

The com.ibm.rqm.buildintegration.BuildDefinition (build plan) and com.ibm.rqm.buildintegration.BuildRecord (build result) resource types in the rqm_build context are deprecated.

• IBM RQM Mobile Application

The RQM Mobile Application is deprecated. The Android and Windows versions of the application, versions 5.x and 6.x are supported. IBM Engineering Test Management Mobile Application is not available for versions 7.0.3 and later. For more information, see IBM RQM Mobile Application Deprecation .

Note: The iOS version of the RQM Mobile Application is no longer supported.

• ETM Word/Excel Importer Utility 32-bit version

The 32-bit version of the ETM Word/Excel Importer Utility is deprecated.

Workaround
The following are the workarounds for the deprecated features:

• TRS 1.0 API

Instead of using the TRS 1.0 API, use the TRS 2.0 API. For more information, see TRS 2.0.

• ETM Reportable REST API

Instead of using remotescript and testscript resource types, use the executionscript resource type, which covers both resource types. For more information, see Resource Objects and their Relationships.
Instead of using workitem resource type for linking, use the ETM OSLC QM V2 API.

• OSLC Automation API

Instead of using the com.ibm.rqm.buildintegration.BuildDefinition and com.ibm.rqm.buildintegration.BuildRecord resource types, use the com.ibm.rqm.buildintegration.BuildDefinition and com.ibm.rqm.buildintegration.BuildRecord resource types in the qm_rqm context. For more information, see rqm_qm:BuildRecord and rqm_qm:BuildDefinition.

• IBM RQM Mobile Application

Instead of using the RQM Mobile Application for offline test execution, use the offline test execution capability in the ETM web UI. For more information, see Offline execution.

• ETM Word/Excel Importer Utility 32-bit version

Instead of using the 32-bit version of the ETM Word/Excel Importer Utility, use the 64-bit version of the ETM Word/Excel Importer Utility. For more information, see Installing the Word Excel Importer.

Related information
Work item 184276
Work item 85647
Work item 163725
Work item 181031
Work item 179174

The clmhelp.war file and the updateSite.zip for release 7.0.2 are unavailable for download

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

• 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

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

• 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

Related information
Work Item 188119

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

Related information

Work item 191650

Test suite snapshot may fail if ETM process contains obsolete configuration

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

Related information
Work item 182931

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 QM 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.

Related information

Deprecated features in 7.0

• To capture the screen, use either OS supported screen capture or other external tools.
• In place of Filter By Tree view, use alternative browse views.

Execution Status by Iteration using TCER Count (Live) widget reports incorrect test case results count when you select the multi-valued

1. Go to 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 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 QM Test Plan: QM Test Plan > Reported By > QM Test Execution Record > Test Schedule > Test Phase
      4. Continue Continue.
   5. Set conditions by using the following steps:
      1. Select attributes of 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 QM 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 as status.
         4. Choose limiter values as status is and select the value. For example, to add 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. Continue Continue.
3. Go to the Name and share tab.
   1. Specify Report name.
   2. Set Default visualization as Graph.
   3. Click Save.

Related information
Work Item 187339

• For online background indexing, no action is required except to ensure that the full-text index folder is empty before you start the server
• For offline indexing before you start the server, run the appropriate repotools-<app> -rebuildTextIndices command.

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.

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

Multiple entries are shown for the same resource during a full-text search for some test artifact types

• Build Record
• Build Definition
• Lab Resource
• Test Cell

Workaround
Originally, when you upgrade an installation by using the upgrade scripts, the full-text search indexes from the earlier installation are copied to the new installation. However, the upgrade scripts in versions 6.0.6.1 and later do not copy previous indexes from 6.0.6 or the earlier versions including the interim fixes. Instead, the new server automatically rebuilds the indexes in the background after you start the server. Results of full-text searches might be incomplete until the reindexing operation is finished. The progress of the reindex is periodically written to the server log file.

Alternatively, instead of allowing the server to rebuild full-text search indexes online, you can rebuild them manually by running the repotools-qm -rebuildTextIndices command after the upgrade is complete, but before you start the server. For more information, see Repository tools command to rebuild text indexes.

Note that reindexing might be a lengthy process and might take many hours for a large database. It is preferred to follow the online background indexing procedure.

As a workaround to the problem, complete one of the following steps:

• For online background indexing, no action is required except to ensure that the full-text index folder is empty before you start the server.
• For offline indexing before you start the server, run the repotools-qm -rebuildTextIndices command.

Related information
Work item 183801

1. Open the rich-text section.
2. Click the Edit pencil icon to open the rich-text editor. (If the rich-text editor also shows the same issue, use Chrome or Internet Explorer to open it.)
3. Select all the content in the rich-text editor (press Ctrl+A).
4. Cut the selected content (press Ctrl+X).
5. Open a blank Microsoft Word document and paste the content into it (press Ctrl+V).
6. Select all the content in the Word document (press Ctrl+A).
7. Copy the selected content (press Ctrl+C).
8. In the rich-text editor of the Rational Quality Manager rich-text section, paste the content (press Ctrl+V).
9. Click the Preview icon to verify that the content is rendered correctly.
10. Save the test artifact to save the content.

1. In Rational Quality Manager, go to the Shared Resource Location section of Manage Project Properties.
2. Remove the trailing separator character from all shared location paths.

BIRT report 'Test Cases Impacted by Defects' reports on last result for test case/TCER but not test suite/TSER

1. Follow IBM Knowledge Center instructions for Reporting on artifacts across projects with Report Builder.
2. At step 5, choose the artifact as QM Test Suite and prepare required relationship with defect, that is, QM Test Suite -> Run By -> QM Test Suite Execution Record -> Current Test Suite Result -> QM Test Suite Result -> Reports on Test Plan -> QM Test Plan -> Related Work Item -> Defect.
3. Run the report.

• 6.0.4 interim fix 007 and later
• 6.0.3 interim fix 010 and later
• 6.0.2 interim fix 015 and later
• No version of 5.0.2 contains a compatible Java version. For 5.0.2, complete the steps in the IBM Support flash article.

1. Log in to Jazz Team Server, go to jts/admin > Server > License Key Management and note all the licenses on the server.
2. In IBM Rational License Key Center, under License Management, click Return Keys.
3. Click the product link that you want to return the license keys for, and then click Return.
4. After the license is returned, click Get Keys.
5. Click the product link to generate licenses for.
6. When prompted, provide the required information and click Generate.
7. Download the  file that contains the new licenses.
8. Log in to Jazz Team Server, go to Server > License Key Management and reimport the new license files.
9. To add a license, click Add, accept the license agreement if you agree to its terms, and then complete the steps in the wizard.

1. Log in to Jazz Team Server, go to jts/admin > Server > License Key Management and note all the licenses on the server.
2. In IBM Rational License Key Center, go to View keys by host or View keys by user.
3. Enter the information about the host or the user.
4. Select the product to generate the license for.
5. Click View Licenses for Selected Product Lines.
6. Select the license and click View Details.
7. Click Download Keys.
8. Log in to Jazz Team Server, go to Server > License Key Management and reimport the new license files.
9. To add a license, click Add, accept the license agreement if you agree to its terms, and then complete the steps in the wizard.

1. Update the Java SDK to IBM 1.6 SR12 or later.
2. In the IBMJavaInstall\jre\lib\security directory, locate the java.security file.
3. In the java.security file, change "keystore.type=jks" to "keystore.type=Windows-MY".
4. Locate the following content:

Deleting the default component configuration of a project causes major issues in ETM

• IBM Engineering Workflow Management (EWM) cannot be integrated.
• Execution adapters, such as Command Line Adapter cannot be connected.
• Utilities, such as the ETM Copy Utility and ETM Excel Importer Utility fail to operate.
• The OSLC QM API service provider document cannot be resolved (404 Not Found).
• ETM resources are not displayed in the Report Builder when you select the configuration management enabled LQE 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. In addition, complete the following steps to display ETM resources in the Report Builder:

• Update the configuration, for example, change the description (required for RQM 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 has been scrubbed.

Related information
Work item 182849

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

1. Stop the CLM/QM server.
2. Set the system property as follows: "-Dcom.ibm.team.repository.service.internal.RdbRepositoryDataMediator.skipValidationOnSaveItemInTxn=true". For details about setting the system property, see Setting generic JVM arguments in the WebSphere Application Server V8.5 Liberty profile.
3. Start the CLM/QM server.

1. Stop the CLM/QM server.
2. Set the system property as follows: "-Dcom.ibm.team.repository.service.internal.RdbRepositoryDataMediator.skipValidationOnSaveItemInTxn=true". For details about setting the system property, see System Properties.
3. Start the CLM/QM server.

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

1. Go to Reports > Report Resources.
2. Click the 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 TER Count for the report name, and save the report.

• 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

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

• 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 (ETM) 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.

Related information
Work item 185979

Extra resources are published in the ETM Resources (TRS 2.0) feed when you enable the baseline only mode in a project area

• Selection resource for the initial stream
• Configuration resource for the initial stream
• Component resource

Workaround
Complete the following steps to avoid including these extra resources:

1. Go to https://<server>:<port>/qm/admin > TRS Feed Diagnostics > Validation.
2. Click Validate and select the Resolve problems checkbox.
3. Optional: Select the Reset incremental data checkbox to force a full validation.
4. Click Validate now.

Related information
Work item 188159
Work item 519075

1. Open the test plan in the test plan editor.
2. Click Requirement Collection Links.
3. Select all of the requirements and click the Reconcile Requirements in Collections icon.

• 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 the test script editor when you edit steps
• In execution steps when you run a test case execution record

• 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.

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 United States.

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

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

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

1. Stop the CLM/QM server.
2. Set the attribute on the Connector tag of the Server.xml file as follows: maxParameterCount="1000000". For details about setting the attribute, see Set connector attribute.
3. Start the CLM/QM server.

Dropped features in the ETM 7.0.2 release

• IBM Engineering Test Management HP Quick Test Professional (QTP)/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 are marked as End-of-Life (EOL) or End Of Support (EOS) in July, 2019. In the 7.0.2 release, ETM ended the support for these adapters.

Note: Both the QTP and UFT adapters will be supported in previous versions of IBM Rational Quality Manager (RQM)/ETM.

• IBM Engineering Test Management HP LoadRunner Adapter

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

Note: The LoadRunner adapter will be supported in previous versions of RQM/ETM.

Related information
Work item 186848
Micro Focus Product Support Lifecycle table

Comma-Separated Values (CSV) export jobs cannot be cancelled during the preparation phase

• Preparation phase – Engineering Test Management (ETM) gathers information about all the test artifacts that need to be exported.
• Rendering phase – ETM writes data to the CSV file.

CSV export jobs cannot be cancelled immediately when in the preparation phase. ETM checks if the export job is cancelled before starting and after completing the preparation phase. If you try to cancel the CSV export job during the preparation phase, the CSV export job is cancelled only after the preparation phase completes. However, CSV export jobs can be cancelled immediately when in the rendering phase.

Related information
Work item 183609

• 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.

• 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.

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

Dropped features in the IBM Engineering Test Management (ETM) 7.0 release

Rich-text content is not imported into the web UI correctly by

A warning message is shown when you create a link between a diagram artifact in IBM Engineering Systems Design Rhapsody (Rhapsody) and a test case in IBM Engineering Test Management (ETM)

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

In Report Builder, the Start Time attribute is no longer available for the QM Test Script Step Result artifact type

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

Multiple rows are shown in Report Builder after modifying an iteration that has at least one result

6.0

Problem

Suppose, you modify an iteration that is associated to a Test Plan and that iteration is also associated to at least one Test Case Result or Test Case Execution Record. Now, if you create a report by using Lifecycle Query Engine as the data source and the report includes a Test Phase relationship, then multiple rows get displayed in the Report Builder. The report displays one row for the Test Case Result or Test Case Execution Record and another row for the new modified iteration in the Test Plan.
 

Workaround

Migrate to the ETM version 7.0.3. For more information, see New and Noteworthy.

Related information

Defect 190711

OSLC Quality Management (QM) PUT and POST API can not add or remove work item links from test case result and test case execution record in configuration management mode

Online migration is not supported for upgrading some versions of the Quality Management application

• Upgrading from version 4.0.6 or later to version 4.0.7 or a version 5 release
• Upgrading from a version 5 release to a version 6 release

If you have version 4.0.6 or later of the QM application and perform an online migration before you upgrade to version 4.0.7 or a version 5 release, the operation runs, but no migration occurs. Similarly, if you have a version 5 release and perform an online migration before you upgrade to a version 6 release, the operation runs, but no migration occurs.

Related information
Work Item 361962
Work Item 141120