IBM Rational Quality Manager
Quality management · Manual testing · Continuous improvement
Rational Quality Manager 184.108.40.206
Rational Quality Manager Version 220.127.116.11 Release Notes
This release is a service release of Rational Quality Manager, Version 3.0.1. It contains new features and fixes for defects. See the Getting Started page for information on documentation and support resources, software and hardware requirements, and installation or upgrade steps.
The following notes detail important fixes and issues in the release of Rational Quality Manager. Please ensure that you also read the Jazz Foundation, Version 18.104.22.168 Release Notes, the Rational Requirements Composer, Version 22.214.171.124 Release Notes, and the Rational Team Concert, Version 126.96.36.199 Release Notes.
Fixes included in this release
The Version 188.8.131.52 release of Rational Quality Manager delivers APAR and non-APAR fixes. To review and explore completed work, see the Rational Quality Manager development dashboard and the Collaborative Lifecycle Management development dashboard.
View this query for a detailed list of fixes for this release.
View the Rational Quality Manager development dashboard APARs page for a summary list of APARs fixed for this release.
View this query for a detailed list of APARs fixed for this release.
|BIRT Reporting: Fixes problem with the "The Execution Status by TER Count" report's handling of customised state names
|Build Integration: Fixed a problem that prevented the display of Rational Team Concert builds
|ClearQuest Integration: Enabled Clearquest OSLC integration where there is a customer ClearQuest Schema
|CQTM Migration: Fixes a problem where the testcase order in a suite is not preserved in the CQTM migration
|CQTM Migration: Enables CQTM migration to a non-SSL RQM server
|DOORS Integration: Fixes a problem where requirements can only be exported to one test plan even if a second DOORS view is created
|Integrations API: Fixes a problem where the API would be unable to access resources whose external ID contained a special character
|Integrations OSLC: Improves performance when associating a defect to multiple TCERs
|Integrations OSLC: Fixes an error that occurs when reconciling a requirement collection where a requirement had changed
|Lab Management: Fixes a problem where selecting a lab resource to reserve based on a test environment causes a radio button to clear, making the reservation impossible to complete
|Offline Execution: Fixes a problem with Japanese characters getting garbled when exported for offline execution
|Offline Execution: Fixes a problem with the generated results from offline execution where a keyword would cause the results to contain an extra step
|PDF Reporting: Added a section for custom attributes to the PDFs
|PDF Reporting: Fixes a problem with the PDF for the Summary of View Test Case Execution Records where column values were overlapping
|Reporting RDDI ETL: Fixes a problem where changing testplan-testsuite relationship were becoming out of sync
|RequisitePro Integration: Fixes a problem with the history generated by adding a reference to a RequisitePro requirement
|RequisitePro Integration: Fixes a problem that occurs when RequisitePro requirements with long names are imported
|RQM Upgrade: Fixes a problem with the upgrade from 2.x where references to missing TERs or Configurations causes the migration to fail
|Test Execution: Fixes a problem where using "Apply All" during a manual test execution would not cause correct timestamps to be set in all step results
|Test Execution: Fixes a problem where selecting multiple TCERs does not enable the Run button
|Test Execution: Fixes a timing issue where a testcase Run button could become enabled before the adapter had loaded
|Test Execution: Fixes a problem where a deleted test script is still visible when running a test case
|Test Execution: Fixes a problem viewing a test case result; choosing "Show all Sections" causes the Defect and Previous Results sections to become empty
|Test Planning: Fixes a problem where duplication of a test script will fail if that script uses the same keyword more than once
|Test Planning: Fixes a problem with selecting a category from the left navagation bar when the number of values for the category is greater than ten
|Test Planning: Fixes a problem where deleted catagory values were still selectable
|Test Planning: Fixes a problem where a view could not be sorted by a custom category if the category name contained a colon
|Test Planning: Fixes a problem which could cause the bottom bar in the list views to become detached, potenitially blocking the view of one of the rows
|Test Planning: Addresses an occasional issue when a test case is duplicated, the new test case is not opened for editing
|Word/Excel Importer: Fixes a problem importing resources using categories with the Excel Import Tool
|Word/Excel Importer: Fixes a problem with the creation of images with the Excel Import Tool
|Word/Excel Importer: Fixes a problem with Japanese characters getting garbled when imported with the Excel Import Tool
|Word/Excel Importer: Enables the setting of categories form the Word Import Tool
|Word/Excel Importer: Enables Word and Excel import tool usage with basic authentication
|Word/Excel Importer: Fixes a problem with the setting of the step type by the Word Import Tool
Known problems and workaroundsThe Rational Quality Manager Version 184.108.40.206 Release Notes query lists the known issues and workarounds in this version.
When using CLM reports, test plan to test suite relationships become inconsistent (PMR 80949 180 000)
In RQM V220.127.116.11 and earlier versions, test suites are associated with a test plan, but the current trigger works based on changes to the test suite. The trigger should work the other way around, based on test plan changes. See work item 60692.
There is a fix available for Rational Insight and RRDI users. If you do not use these products, the fix is not required because BIRT reports are not impacted.
The solution includes:
(1) A hotfix for the schema in which the new trigger keeps the old name to ensure it will not break a migration to V4.0.
(2) A repair job to load the broken relationships.
SET CURRENT SCHEMA RIODS;
DROP TRIGGER TRG_TSTPLTLK;
CREATE TRIGGER TRG_TSTPLTLK AFTER UPDATE OF REC_DATETIME ON TESTPLAN REFERENCING NEW AS NEWROW OLD AS OLDROW FOR EACH ROW MODE DB2SQL BEGIN ATOMIC DELETE FROM TESTSUITE_TESTPLAN_LOOKUP WHERE TESTPLAN_ID=NEWROW.TESTPLAN_ID; END;
ALTER SESSION SET CURRENT_SCHEMA=RIODS;
DROP TRIGGER TRG_TSTPLTLK;
CREATE TRIGGER TRG_TSTPLTLK AFTER UPDATE OF REC_DATETIME ON TESTPLAN FOR EACH ROW BEGIN DELETE FROM TESTSUITE_TESTPLAN_LOOKUP WHERE TESTPLAN_ID=:NEW.TESTPLAN_ID; END;
DROP TRIGGER RIODS.TRG_TSTPLTLK
CREATE TRIGGER RIODS.TRG_TSTPLTLK ON RIODS.TESTPLAN FOR UPDATE AS BEGIN DELETE FROM RIODS.TESTSUITE_TESTPLAN_LOOKUP WHERE TESTPLAN_ID IN (SELECT TESTPLAN_ID FROM INSERTED) END
This hotfix comprises two parts: a schema patch for your data warehouse and a repair job that reloads the relationships between all your test plans and their assigned test suites into the warehouse. The instructions cover how to run it with IBM Insight V18.104.22.168 or V1.1 as well as the RRDI that ships with CLM V22.214.171.124. The hotfix has been tested against CLM V126.96.36.199 and CLM V4.0 M7.
- Apply the schema fix.
- Open a command tool for your database, such as Command Center for DB2.
- In "Schema changes" above, select the correct script for your respective database vendor. Copy, paste, and run the script. The script drops an existing trigger in the RIODS schema and recreates it with the correct definition.
- If you have never run any ETLs, then you can stop here; the solution is complete. If you ran ETLs in the past, then you need to run a repair job to correct the data in your warehouse by completing steps in one of the following two alternatives:
- Alternative 1: Run the warehouse repair job using Rational Insight.
These instructions assume that you setup Rational Insight for CLM and already ran your ETLs successfully using Data Manager in the past. If you run your ETLs on a non-Windows machine using data movement tasks then the instructions for running the job with RRDI will also work for you instead.
- Download the file attached to this work item called "RQM_RepairPlanSuiteLookup.pkg".
- Start Data Manager.
- Click File > Import Package.
- When prompted to backup your catalog, do so.
- In the Package File dialog box, select the file you downloaded earlier; then click Open.
- In the Import Package Wizard dialog, only select the following entry: RQM_RepairPlanSuiteLookup. Then in the Dependent Components dialog box, clear the selection of everything except the mandatory selection RQM3_PlanSuiteLookup.
- Confirm that only the two component entries listed above are selected and no other components. Click Next; then click Finish.
- After the import, go to the Connections list and confirm that your settings for Rational Data Warehouse are still correct.
- Verify that your xdc files are configured correctly (your previous ETL jobs all succeeded and covered all your projects).
- Run the job in "Build and JobStreams > Jobs > RQMJobs > RQM3_MigrationJobs > RQM_RepairPlanSuiteLookup".
- Review the logs files and make sure all jobs completed successfully.
- Alternative 2: Run the warehouse repair job using Rational Reporting for Development Intelligence (RRDI).
- Download the rqm3011.xdc or rqm4.0.xdc file and
configure the ODBC data connection called "Rational Quality Manager." For detailed instructions, see Integrating the Collaborative Lifecycle Management XML data configuration files with Rational Insight
in the CLM information center.
Note: You only need to download and configure the rqm3011.xdc or rqm4.0.xdc file; you can ignore the other file described in the help page.
- Download the file, "RQM_RepairPlanSuiteLookup.zip," attached to jazz.net work item 60692.
- Place the file in the following folder:
- To import this one file into the report server, see Importing the data models and reports on Rational Reporting for Development Intelligence.
- To create a new connection called "RIDW (ETL)", complete steps 1 through 2 (only) of these instructions.
Note: it is important to use the DB admin user (or the user that you have created for the Java ETL jobs) here for the Signon user. Although these are instruction from RQM 2.x, this page describes the steps you need to do to get the "RIDW (ETL)" connection right.
- In Cognos Connection, go to the folder dataMovementTasks and execute the job called "RQM_RepairPlanSuiteLookup" that you imported earlier.
- Check the log files in
/cognos/datamanager/log to make sure all jobs completed successfully.
- Download the rqm3011.xdc or rqm4.0.xdc file and configure the ODBC data connection called "Rational Quality Manager." For detailed instructions, see Integrating the Collaborative Lifecycle Management XML data configuration files with Rational Insight in the CLM information center.
- Alternative 1: Run the warehouse repair job using Rational Insight.
Rational RequisitePro and Rational Quality Manager integration issue
You might see the following message in the Rational RequisitePro Server Administration page:
"The imported username and password for the following RequisitePro projects are invalid:
Workaround: The message is misleading and can be ignored. See work item 63006.
Money that Matters sample can cause ETL to hang
Occasionally, the the Rational Quality Manager ETL hangs after the creation of
the Money that Matters sample. This problem might be occurring due to an interaction
with testing automation.
Workaround: The problem can be fixed by restarting the server. See work item 59531.