Library > Articles >

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

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

Test case execution records are getting duplicated to target plan though it already has those selected test case execution records


First occurrence
7.0

Problem
When a user tries to duplicate a test case execution record with Include test case execution results option, the execution record gets duplicated even though the target test plan already includes the same execution record. This creates duplicate entries in the Test Case Execution Record section in the target test plan.

Workaround
To duplicate a test case execution record with Include test case execution results option, select one of the following options:

  • Make sure that the target test plan does not have the same execution record, and if it has, delete the execution record from the test plan before duplication.
  • Duplicate the test plan and select an option to duplicate test case execution records wtih test case results. This option makes sure that no execution records are duplicated in the newly created test plan.

Related information
Work item 184244

Back to top

TRS validation stop link is not working


First occurrence
7.0

Problem
You cannot  stop TRS validation once the validation is scheduled to run and the following message is being displayed in the status page: TRS validation scheduled to run, please refresh in a few moments to see the current status. The stop signal is ignored and the validation starts as normal.

Workaround
Reissue the stop command once the validation starts and you see any of the following statuses: Retrieving items from repository, Parsing the TRS items feed, or Calculating discrepancies.

Related information
Link to the TRS Validator:
https://<domain>:<9443>/<qm>/TRSValidator

Back to top

TRS Full Validation fails after a manual rebase


First occurrence
7.0

Problem
Manual rebase, which is executed from the TRS console, is intended to be used by IBM support only. If a manual rebase is executed, the validator will not work until a schedule rebase is executed.

Workaround
In order to perform a validation after a manual rebase was executed, use the Reset incremental data option in TRS validation:

  • Click Validate. Do not click Run Full Validation.
  • In Validate dialog box, select Reset incremental data checkbox.
  • Click Validate now.
Related information
Work item 183661

Back to top

Deprecated features in 7.0


First occurrence
7.0

Problem
The screen capture tool and Filter By Tree view are not available in release 7.0.

Workaround

  • 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.
Related information
Work item 181053
Work item 182938
Work item 182940

Back to top

Test suite snapshot may fail if ETM process contains obsolete configuration


First occurrence
7.0

Problem
When you create snapshot of a test suite, the action might fail if there is an obsolate 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

  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

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

The Quality Management data source in LQE might register an invalid update when the QM server has a heavy load


First occurrence
6.0.6.1

Problem
When the Quality Management (QM) server is experiencing a heavy load, the Quality Management data source in Lifecycle Query Engine (LQE) 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 LQE to apply the changes.
Related information
Work Item 180212
Work Item 180302

Back to top

Full-text search indexes must be rebuilt when you upgrade to 6.0.6.1 or later


First occurrence
6.0.6.1

Problem
In the 6.0.6.1 release, the Apache Lucene full-text search engine was upgraded to a more recent version. This upgrade requires all existing full-text search indexes that were created in 6.0.6 or earlier to be rebuilt. Full-text search indexes must be rebuilt for both the CLM servers and the Rational Team Concert Client for Eclipse IDE.

Workaround
Typically, 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 6.0.6.1 and later do not copy previous indexes from version 6.0.6 or earlier (including interim fixes). Instead, the new server automatically rebuilds the indexes in the background after you start it. 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-<app> -rebuildTextIndices command after the upgrade is complete, but before you start the server, where <app> is one of am, ccm, or qm. Note that reindexing might be a lengthy process and can take many hours for a large database. In the web client, a system alert in the banner states that reindexing is in progress.

If you follow a manual upgrade procedure instead of running the upgrade scripts, you must ensure that the full-text indexes are not copied from the old installation to the new installation. If the new installation is configured to use the same full-text index location as the old installation (the value of the com.ibm.team.fulltext.indexLocation property in the old and new teamserver.properties file is the same absolute path name), you must either run the repotools-<app> -rebuildTextIndices command before you start the server, or delete the contents of the folder at that location before you start the server. You might want to preserve the old contents if you decide to abandon the upgrade and roll back to the previous release.

If an application is clustered, the offline reindexing procedure (using repotools) or the online procedure (ensuring that the full-text index folder is empty before starting the server) must be performed on each node in the cluster.

The Rational Team Concert Client for Eclipse maintains a local full-text search index for the Team Artifact History view. When you upgrade the Rational Team Concert Client for Eclipse to version 6.0.6.1 or later, the full-text search index is automatically deleted, which means the artifact history is cleared and will accumulate artifacts again after the upgrade.

For CLM servers, complete one of these 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 appropriate repotools-<app> -rebuildTextIndices command.
Related information
Work Item 467449

Back to top

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


First occurrence
6.0.6.1

Problem
When you generate reports in Report Builder, the Is Blocked attribute is no longer available for conditions or columns in reports on the QM Test Execution Record artifact type. The Is Blocked 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.
Related information
Work Item 179565

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

Rich-text data is not rendered correctly in Mozilla Firefox


First occurrence
6.0.6

Problem
Sometimes, rich-text data in rich-text sections of Rational Quality Manager (presently known as IBM Engineering Test Management), such as the Test Case Design section, is not rendered correctly in Mozilla Firefox. This issue occurs because, if rich-text data has a depth of more than 200 nodes, Mozilla Firefox prunes the DOM elements which can cause missing data.

Workaround
Use either Google Chrome or Microsoft Internet Explorer, or complete the following steps to make the text render correctly in Mozilla Firefox:
  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.
Related information
Work Item 170960
Mozilla bug: DOM pruned at depth 200   

Back to top

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


First occurrence
6.0.6

Problem
BIRT report Test Cases Impacted by Defects produces accurate data when you execute the test from a test case or test case execution record but when the the test is executed from a test suite or test suite execution record, Test Cases Impacted by Defects does not produce accurate data. In such a case, the report section that is related to defects against the test suite and test suite result, are not accurate.

Workaround
Do not use BIRT reporting. Instead, use LQE-based reporting in Report Builder. BIRT reporting might be removed in a future release.
Complete these steps:

  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.
Related information
Work item 172363

Back to top

Rational Functional Tester scripts that point to a shared location don't run if the path has a trailing separator


First occurrence
6.0.6

Problem
If a Rational Functional Tester script is in a shared path, that path is added with a trailing separator to the Shared Resource Location section of the Rational Quality Manager (presently known as IBM Engineering Test Management) project properties, and the test script is included in the Resource section of a test plan, the test script doesn't run. When you run the script, the execution result is created with an error and this message is displayed in the result details: Could not run the script.

Workaround
  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.
Related information
Work Item 172115

Back to top

Licensing errors might occur if you upgrade the Java environment or upgrade applications to version 6.0.5 or later


First occurrence
6.0.5

Problem
If you upgrade your version of Java to a fix pack that was built after April 2017, or you upgrade an application to version 6.0.5 or later and are using WebSphere Liberty, licensing errors might occur. The errors occur because earlier licenses were signed with the MD5 algorithm, which is now blocked by newer versions of Java.

For example, the License Key Management page for Jazz Team Server might display the following error in the Description field: CRJAZ1236I A development time license is being used. Similarly, the jts.log file might display the following error: CRJAZ0965I The file was not a valid server or client access license activation key.

The latest license files no longer contain the MD5 algorithm because IBM and Oracle Java introduced restrictions on JAR files that are signed with weak algorithms and keys.

Workaround
The licenses in the IBM Rational License Key Center  (presently known as IBM License Key Center) were updated to use a different signature algorithm.

After you upgrade your server to version 6.0.5 or later, obtain the updated licenses from the IBM Rational License Key Center to replace your current licenses. If you previously used floating, token, or authorized user single install licenses, install their updated versions. Your existing user license assignments are kept during the installation of the updated licenses.

Important: If you are not upgrading all applications at the same time, you must apply an interim fix to the applications at earlier versions before you upgrade Jazz Team Server. The following interim fixes contain the compatible version of Java:
  • 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.
If you cannot apply the interim fix before the upgrade, upgrade Jazz Team Server and then complete the steps in the IBM Support flash article. If you do not apply the interim fix or complete the steps in the article, the internal licenses do not load on Jazz Team Server and the applications might experience issues.

To update your current license files, follow the instructions in the Interactive Upgrade Guide or complete the following steps based on the type of license:

For term (floating or authorized user) or token licenses:

Note: For token licenses, you are only required to download the jazztokens.zip file. You do not have to download the license.dat file because it does not contain changes.
  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.
For non-term floating and authorized user licenses:
  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.
Note: If you imported trial licenses before the newer versions of Java were adopted, you might still receive errors in the jts.log file even after you import the updated licenses. For example, you might receive this error: CRJAZ0965I The file was not a valid server or client access license activation key. You can ignore these errors.

Related information
IBM Rational License Key Center
Interactive Upgrade Guide
Oracle release note: Restrict JARs signed with weak algorithms and keys

Back to top

Snapshots of test plans with a large number of test artifacts might cause an error


First occurrence
6.0.5

Problem
When you create a snapshot of a test plan that has a large number of test artifacts, an error message such as 500: Unable to save snapshot for TestPlan 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 Rational Quality Manager (presently known as 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.

Related information
Work Item 166727
Rational Quality Manager Default Session Timeout

Back to top

Command-line adapter cannot connect to the QM server by using smart card authentication


First occurrence
6.0.4

Problem
If you use the command-line adapter to connect to the Quality Management (QM) server, smart card authentication does not work.

Workaround
Complete these steps:
  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:
security.provider.1=com.ibm.jsse2.IBMJSSEProvider2
security.provider.2=com.ibm.crypto.provider.IBMJCE
security.provider.3=com.ibm.security.jgss.IBMJGSSProvider
security.provider.4=com.ibm.security.cert.IBMCertPath
security.provider.5=com.ibm.security.sasl.IBMSASL
security.provider.6=com.ibm.xml.crypto.IBMXMLCryptoProvider
security.provider.7=com.ibm.xml.enc.IBMXMLEncProvider
security.provider.8=org.apache.harmony.security.provider.PolicyProvider
security.provider.9=com.ibm.security.jgss.mech.spnego.IBMSPNEGO

  5. Replace that content with the following content:
 
security.provider.1=com.ibm.security.capi.IBMCAC
security.provider.2=com.ibm.jsse2.IBMJSSEProvider2
security.provider.3=com.ibm.crypto.provider.IBMJCE
security.provider.4=com.ibm.security.jgss.IBMJGSSProvider
security.provider.5=com.ibm.security.cert.IBMCertPath
security.provider.6=com.ibm.security.sasl.IBMSASL
security.provider.7=com.ibm.xml.crypto.IBMXMLCryptoProvider
security.provider.8=com.ibm.xml.enc.IBMXMLEncProvider
security.provider.9=org.apache.harmony.security.provider.PolicyProvider
security.provider.10=com.ibm.security.jgss.mech.spnego.IBMSPNEGO

Related information
Work Item 156232

Back to top

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


First occurrence
6.0.3

Problem
Deleting the default component configuration of a project causes the following 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

Back to top

Requirement links do not appear in a cloned test case that has multiple components and link validity enabled


First occurrence
6.0.3

Problem
Problem occurs when a Global Configuration contains two components from IBM Engineering Test Management (ETM), Component A and Component B. Components are listed in the Global Configuration in the following order:

  • Component A
  • Component B

A test case in Component A, which has requirement link is cloned in Component B and the original test case is deleted from Component A. In such a scenario, the requirement link disappears in the test case when the user opens Component B and link validity is enabled.

Workaround
To display the requirement links, select one of the following options:

  • Reorder the components in the Global Configuration.
  • Restore the test case in Component A.

Related information
Work item 184214

Back to top

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


First occurrence
6.0.2

Problem
You cannot create or save a JUnit Selenium test script with a classpath 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 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.
Workaround

Complete the steps for the application server that you use.

IBM WebSphere Application 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 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 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.
Related information
Work Item 154265

Back to top

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


First occurrence
6.0.1

Problem
If the Tester Report using Weight or Tester Report using TCER count widgets are added to the dashboard, and you click either widget header to open the report, an error is displayed about a missing report descriptor. Clicking the widget header should open the report page to 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 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.
Related information
Work Item 171987

Back to top

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


First occurrence
6.0.1

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.
Related information
Work Item 140715

Back to top

Work item queries that contain test artifact links cannot be created or edited in the Rational Team Concert Eclipse client


First occurrence
6.0.1

Problem
Work item queries for Task-Review work items that contain test artifact links cannot be created or edited in the Rational Team Concert 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 Rational Quality Manager (presently known as IBM Engineering Test Management) web client (https://<host>:<port>/<context root>/console/<project area name>#action=com.ibm.team.workitem.viewWelcome).

Related information
Work Item 141552

Back to top

Requirement links do not appear in a test case when it has link from two different requirement link providers and user has access permission for only one requirement provider


First occurrence
6.0.1

Problem
Problem occurs when all the following conditions hold true:

  • Engineering Test Management is integrated with both Engineering Requirement Manager DOORS Next and Design Manager as requirement provider.
  • Engineering Test Management is in the context of global configuration.
  • Link validity is enabled in Engineering Test Management.
  • The logged in user is member of Engineering Test Management, Engineering Requirement Manager DOORS Next and Global Configuration management but not a member of Design Manager project area.
  • Test case is associated requirement for both Engineering Requirement Manager DOORS Next and Design Manager.

In such a scenario, DNG links are not visible in the test case.

Workaround
Make sure that the user is member of both Engineering Requirement Manager DOORS Next and Design Manager project areas.

Related information
Work item 184172

Back to top

Rational Integration Tester test scripts are not fully executed from test suites


First occurrence
6.0

Problem
If you use a test suite to execute a Rational Integration Tester test script, the execution never finishes and the progress bar stalls at 10% completion. However, you can use a test case to correctly execute the same Rational Integration Tester test script.

Workaround
This issue is a known limitation in Rational Integration Tester 8.7.x that was corrected. Upgrade to Rational Integration Tester 9.0 or later.

Related information
Work Item 147345

Back to top

ETM / EWM build integration requires a EWM license for functional user


First occurrence
6.0

Problem
To import a build definition or a build record from EWM to ETM, you must associate a functional user in EWM for its consumer inbound relationship with ETM. If the functional user does not have a license to get read access, you cannot import the build information to ETM.

Workaround
Assign a EWM license to the functional user. License that can be used are: IBM Engineering Workflow Management – Developer, IBM Engineering Workflow Management – Contributor, Rational Team Concert – Build System, or TRS Consumer-Internal.

Related information
Work item 143096

Back to top

When requirement collection names are updated, the old name is still shown


First occurrence
5.0.2

Problem
This problem occurs when a test plan is associated with a requirement collection and the collection’s name is changed. If you open the test plan, go to the Requirement Collection Links section, and group by Requirement Collection, the old collection name is shown instead of the updated name.

Workaround
Complete these steps:
  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.
Related information
Work Item 122853

Back to top

When you export a BIRT report to Microsoft Excel, you cannot open the new file in Excel


First occurrence
5.0.2

Problem
If you export a BIRT report to Microsoft Excel and try to open the new file in Excel, an error message about Problems During Load is shown. The resulting log file mentions XML ERROR in Table. This issue has been observed when reports include both a chart and a table.

Workaround
Open the new file by using Apache OpenOffice Calc.

Related information
Work Item 124705

Back to top

Connection to the mobile client fails when the server has a self-issued SSL certificate that is signed by an internal certificate authority


First occurrence
5.0.1

Problem
When you use the Rational Quality Manager (presently known as IBM Engineering Test Management) mobile application, you might have difficulties connecting to the Quality Management server if the certificate that is used in your deployment is internally signed and not from a trusted certificate authority.

Workaround
Follow the detailed guidance on the Jazz.net wiki.

Related information
Work Item 118526

Back to top

The reconciliation with requirement collections fails with a timeout error


First occurrence
5.0

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 Rational Quality Manager (presently known as IBM Engineering Test Management), the reconciliation with requirement collections fails and responds with a server error. The reconciliation fails after a fixed period of time. In the details of the reconciliation failure, you might see one of two 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.
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.

Related information
Work Item 105153
Reference topic: plugin-cfg.xml file (See the ServerIOTimeout section)
Setting up servers for a basic high-availability configuration

Back to top

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


First occurrence
5.0

Problem
When you edit an artifact, some context menus, toolbar labels, and tooltips in the editor might be translated into the browser-preferred language even if that language is not selected in IBM Installation Manager during installation. In Rational Quality Manager (presently known as IBM Engineering Test Management), you might encounter this issue 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 the test script editor when you edit steps
  • 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, ensure 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.

Related information
Work Item 145943

Back to top

Problems opening the Rational Quality Manager importer from Microsoft Excel or Microsoft Word


First occurrence
5.0

Problem
In Microsoft Excel or Microsoft Word, when you try to open the Rational Quality Manager (presently known as 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.

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 United States.
Windows XP operating systems
  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).
Related information
Work Item 101602

Back to top

TCERs cannot be generated for a large number of test cases at one time


First occurrence
4.0.5

Problem
If you have a large number of test cases, such as over 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 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.
Workaround
Complete the steps for the application server that you use.

IBM WebSphere Application Server
  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.
Apache Tomcat
  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.
Related information
Work Item 139529

Back to top

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


First occurrence
4.0

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
        a. mmm
        b. nnn
                i. xxx
                ii. yyy
                iii. 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
        a. zzz
        b. yyy
        c. xxx

Workaround

Complete these steps:

1. Delete all but one entry in the level that you want to delete. In this example, delete b. nnn.
 
1. aaa
2. bbb
        a. mmm
                i. xxx
                ii. yyy
                iii. zzz

2. Select all the entries in the lower level and decrease their indent by one level. The item and the numbering style will remain from higher level.
 
1. aaa
2. bbb
        a. mmm
        b. xxx
        c. yyy
        d. zzz

3. Remove the remaining item from the higher level, and change the style of the numbered list if needed.
 
1. aaa
2. bbb
        a. xxx
        b. yyy
        c. zzz

Related information
Work item 179443

Back to top

Limitations

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


First occurrence
7.0

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.

Related information
Work item 183782

Back to top

When duplicating test case results across the project, test environments for target test case results are always same as test case execution records


First occurrence
7.0

Problem
While duplicating test case results across the project, if test environments in the source project are different for test case execution record and the latest test case result, then test case result's test environment in target project is overwritten by mapped test environment of test case execution record.

Currently, cross project test artifact duplication wizard does not offer test environment mapping for the test case results. Hence, the mapped test environments from test execution record wizard page are being used.

Related information
Work item 183679

Back to top

Few attributes are wrongly copied to the test case result during duplicating test case execution along with test case result from a test plan


First occurrence
7.0

Problem
When an user duplicates one or multiple test case execution record(s) from a source test plan to a destination test plan, user might optionally choose to copy associated test case result to destination test plan. In the copied test case result, the following attributes are not copied properly:

  • Test case is set to null in the copied test case result when multiple test case execution records are copied.
  • Iteration is set to null in the copied test case result when one or multiple test case execution record(s) are copied.
  • Test plan is set to source test plan instead of destination test plan in the copied test case result when one or multiple test case execution record(s) are copied.


Related information
Work item 184160

Back to top

Known issue in translated versions of ELM 7.0 documentation


First occurrence
7.0

Problem
  1. The table of contents for ELM 7.0 documentation on IBM Knowledge Center (KC) might display long navigation titles in place of short titles for content in languages other than English.
  2. The pre-release header is visible on the translated pages of ELM documentation on IBM KC.
Related information
Task 496011

Back to top

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


First occurrence
7.0

Problem
IBM Rational RequisitePro integration is not supported for the IBM Rational Quality Manager (now known as IBM Engineering Test Management) 6.0 and later releases. To ensure that you could continue to browse and access the Rational RequisitePro requirements, IBM Engineering Requirements DOORS Next (DOORS Next) and IBM Engineering Test Management (ETM) supported migration of the ETM and Rational RequisitePro integration data to DOORS Next.

In the 7.0 release, both ETM and Doors Next removed the migration support. You must migrate the ETM and Rational RequisitePro integration data to DOORS Next before you upgrade to a 7.0 or later release.

Related information
New & Noteworthy for IBM Engineering Requirements Management DOORS Next 7.0
Work item 186848

Back to top

Execution schedule steps fail if they don't meet the execution preconditions for the execution record


First occurrence
6.0.6.1

Problem
Version 6.0.6.1 corrected an issue where the preconditions for an execution record were not enforced for execution steps. As a result, an execution schedule that previously completed without errors because of the non-enforcement of the execution record preconditions might fail in 6.0.6.1. If you deploy execution preconditions for execution records, ensure that the execution record's preconditions are met when you use them in execution schedules. You might also choose to configure execution schedules to ignore the preconditions for execution records.

Related information
Running execution records in execution schedules without precondition checks

Back to top

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


First occurrence
6.0.6.1

Problem
When you generate reports in Report Builder, the Start Time attribute is no longer available for conditions or columns in reports on the QM Test Script Step Result artifact type. The Start Time attribute showed the date and time when execution of the test script step result started. However, the value was always incorrect and showed the same value as the End Time attribute.

Related information
Work Item 178805
Work item 180026

Back to top

Java 8 SR5 Fix Pack 5 through Fix Pack 10 is not supported as the runtime for CE/CLM applications on a Windows platform


First occurrence
6.0.5

Problem
Continuous Engineering (CE) and Collaborative Lifecycle Management (CLM) applications on a Windows platform that run on Java 8 SR5 Fix Pack 5 through Fix Pack 10 encounter null pointer exceptions and might not be usable. Use Java 8 SR5 Fix Pack 11 (8.0.5.11) or later as the runtime.

Related information
Work Item 455371
Work Item 452307
APAR IJ04429

Back to top

Test data in a snapshot can change


First occurrence
6.0.2

Problem
When you create a snapshot of a test script, the test data reference in the snapshot is always the same as the current revision of the test script. Therefore, 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.

Related information
Work Item 148923

Back to top

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


First occurrence
6.0.1

Problem
If you group the Test Statistics, Test Matrix, or Execution by Weight dashboard widgets by a category that has multiple values 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 7 test cases in the following way:
  • 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
In this scenario, the results should show that each value is assigned to 5 test cases. However, because the widgets tabulate only the first value for categories with multiple values, the widgets show that 5 test cases contain the Development Test value, and only 2 test cases contain the Integration Test value.

Related information
Work Item 142093

Back to top

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


First occurrence
6.0.1

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

Related information
Work Item 135925
Work Item 142409

Back to top

RQM Reportable REST API does not support team area process-level operations


First occurrence
6.0.1

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

Related information
Work Item 140279
Work Item 142815

Back to top

Rational Performance Tester cannot connect to the server when Rational Quality Manager (presently known as IBM Engineering Test Management)

 is configured with single sign-on (SSO)
First occurrence
6.0

Problem
Rational Performance Tester cannot communicate with the Rational Quality Manager (presently known as IBM Engineering Test Management) server when Rational Quality Manager is configured with single sign-on (SSO) authentication. When you configure the adapter from Rational Performance Tester and click Connect to RQM, an attempt is made to connect to the Rational Quality Manager server, but the connection is never established. Because the connection does not succeed, the Rational Performance Tester adapter is not listed on the Adapter Console page. A resolution to this issue is available in the Rational Performance Tester 8.7.1 adapter.

Related information
Work Item 137285

Back to top

Guest Access feature is not supported


First occurrence
6.0

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 (presently known as IBM Engineering Test Management).

Related information
Work Item 161061
Work Item 161056
Work Item 161064
Work Item 413189
Work Item 413950

Back to top

The Rational Quality Manager (presently known as IBM Engineering Test Management)

 mobile application does not work in a single sign-on (SSO) environment
First occurrence
6.0

Problem
The Rational Quality Manager (presently known as IBM Engineering Test Management) mobile application cannot connect to the Rational Quality Manager server when the server is configured for a single sign-on (SSO) environment. In this scenario, you cannot use the mobile application to run tests in offline mode.

Related information
Work Item 137845

Back to top

Validated By test links from some RM applications to a version 6.0 or later Rational Quality Manager (presently known as IBM Engineering Test Management)

 project area that is enabled for configuration management might link to the incorrect test artifact
First occurrence
6.0

Problem
When a version 6.0 or later Rational Quality Manager (presently known as IBM Engineering Test Management) project area is enabled for configuration management, you cannot create new requirements links to Rational DOORS, Rational DOORS Web Access, or version 5 releases of Rational DOORS Next Generation (presently known as IBM Engineering Requirements Management DOORS Next) because these products and versions do not support configuration management. However, you can create a Validated By test link in the opposite direction: from these Requirements Management (RM) applications to a version 6.0 or later Rational Quality Manager project area that is enabled for configuration management. If you create a baseline or stream in the version 6.0 or later Rational Quality Manager project area, the test artifact links that are shown in the RM application might not point to the correct test artifact in the correct configuration. For this reason, you should not create Validated By test links from these RM applications to a version 6.0 or later Rational Quality Manager project area that is enabled for configuration management.

Related information
Work Item 135427

Back to top

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


First occurrence
6.0

Problem
When you merge artifacts from a baseline, some sections do not support the “Accept section” and “Merge section” operations. To view the support for each artifact type, see the related tables.

Related information
Work Item 138430

Back to top

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


First occurrence

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

 

Back to top

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


First occurrence
6.0

Problem
When a version 6.0 or later ETM project area is enabled for configuration management, you cannot add or remove work item links from a test case result or a test case execution record using PUT and POST OSLC Quality Management (QM) API. This symptom applies to any test artifact type that supports CMM links, for example, test case's development items. Note that CCM links are the only links that ETM does not own.
However, you can add or remove work item links from test case result and test case execution record in configuration management mode using web UI.

Related information
Work item 183251

Back to top

Email notifications for formal reviews are not customizable


First occurrence
6.0

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.

Related information
Work Item 141712

Back to top

Data Collection Component only loads requirement data from Rational DOORS Next Generation (presently known as IBM Engineering Requirements Management DOORS Next)


First occurrence
6.0

Problem
Starting in Rational Quality Manager (presently known as IBM Engineering Test Management) 6.0, the Data Collection Component only loads requirement data from Rational DOORS Next Generation (presently known as IBM Engineering Requirements Management DOORS Next). The Data Collection Component no longer integrates with applications that are not part of the Rational solution for Collaborative Lifecycle Management (CLM) (presently known as IBM Engineering Lifecycle Management), such as Rational RequisitePro. The Data Collection Component does not load requirement data from such applications or expose it through the Rational Quality Manager Reportable REST API. This limitation also applies to mixed environments that deploy both Rational Quality Manager 5.x and 6.0. This limitation should be considered before upgrading to the Rational solution for CLM version 6.0 or later.

Related information
Work Item 356530 

Back to top

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


First occurrence
4.0.6

Problem
Online migration for the Quality Management (QM) application is not supported in these upgrade scenarios:

  • 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

Back to top

© Copyright IBM Corporation 2022

Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.
Feedback
Was this information helpful? Yes No 0 people rated this as helpful.