Workarounds and Limitations: Known issues in IBM Rational Quality Manager 4.0.6 and 4.0.7
The following known problems are related to the Rational Quality Manager 4.0.6 and 4.0.7 releases.
Workarounds
The following problems in this release have workarounds:
- Planning: Snapshots of test script steps contain incorrect information when dealing with linked requirements
- Execution: In the Run Test Suite window, adapters across all test cases cannot be selected at the same time
- Reporting: The generation of test cases to PDF reports fails with a java.lang.StackOverflowError exception
- Reporting: Cognos reports for quality management are duplicated
- Reporting: Only one defect for each test case execution result is populated in the data warehouse
- Reporting: Custom categories and attributes are not always accurately shown in views that are exported to PDF format
- Test scripts that do not contain keywords show an error message about containing nested keywords
- Subcategory values are missing from imported process templates
- TCERs cannot be generated for a large number of test cases at one time
- Categories cannot be saved if they have the same name as a different category type in the same hierarchy
- Test case results cannot be opened if requirement links were removed from the associated test case and manual test script steps when in a read-only state
Limitations
The following problems do not currently have workarounds:
- 4.0.6 only: The inline editing of manual scripts in a table causes the loss of manual test steps
- Online migration is not supported for upgrading some versions of the Quality Management application
Workaround summary
Problem
If you take a snapshot of a manual test script and then link a requirement to a script step, the requirement link is shown in the script snapshot. If you link a requirement to a manual script step, take a snapshot of the manual script, and then remove the requirement link in the current version, the requirement link is also removed from the script snapshot.
Workaround
If you need a snapshot of a manual script but want to ensure that the requirement link information for a script step stays correct, do not take a snapshot. Instead, make a copy of the script and select Duplicate with references. The duplicated manual script will have the correct requirement link information.
Related information
Workaround summary
Problem
In the Run Test Suite window, you cannot select adapters across all test cases at the same time. When you try to select all of the test cases, only the test cases on the current page are selected.
Workaround
Important: You can select adapters for multiple test cases only if the test cases share the same script type.
To select adapters across all of the test cases, follow these steps:
- In the Run Test Suite window, from the Items per page list, make sure that Show All is selected.
- To select all of the test cases on the page, click the check box that is next to the Test Case column heading.
- To change the adapters for all of the test cases on the page, click the Select a machine to run this test icon. In the window that opens, select one or more adapters, and then close the window.
- If the Run Test Suite window contains more pages, go to each page and repeat steps 2 and 3.
Related information
Workaround summary
Problem
If the rich-text supported sections of a test case, such as the Test Case Design section, contain more than 30000 characters, the test case cannot be generated to a PDF report. When you try to generate a PDF report, a java.lang.StackOverflowError exception occurs in the QM log file.
Workaround
Increase the stack size for threads of the Java virtual machine (JVM) to a larger number than default value. For example, increase the -Xss property of the JVM to 2048K. For more information about the -Xss property, see the -Xss reference topic.
- On Apache Tomcat servers, this workaround varies depending on whether the Rational Quality Manager server is running on a Windows or Linux system.
- For Windows systems, follow these steps:
- In a text editor, open the server.startup.bat file.
- Add or modify the -Xss property as follows:
set JAVA_OPTS=%JAVA_OPTS% -Xss2048K. - Restart the Rational Quality Manager server on Tomcat.
- For Linux systems, follow these steps:
- In a text editor, open the server.startup.sh file.
- Add or modify the -Xss property as follows:
JAVA_OPTS="$JAVA_OPTS -Xss2048". - Restart the Rational Quality Manager server on Tomcat.
- For Windows systems, follow these steps:
- On WebSphere Application Server, follow these steps:
- In the WebSphere Application Server console, open the JVM configuration settings pane. The path to reach that pane differs depending on which platform you are using. For more information, see Java virtual machine settings.
- In the Generic JVM arguments field, add or modify the -Xss property as follows:
-Xss2048K. - Restart the Rational Quality Manager server on WebSphere Application Server.
Related information
Workaround summary
Problem
In the version 4.0.6 products of the Rational solution for Collaborative Lifecycle Management (CLM), six Cognos reports for quality management were renamed. If you use those reports in version 4.0.5 or earlier and then upgrade to version 4.0.6 or later, the reports are duplicated. You must manually delete the reports; you need to delete the reports only once. However, if you upgrade from version 4.0.6 to version 5.0 or later, you do not need to manually delete the reports.
For example, if you upgrade from version 4.0.4 to version 4.0.6, you must delete the reports from version 4.0.6. If you later upgrade from version 4.0.6 to version 4.0.7, you do not need to delete the reports again.
This table shows the reports that were renamed.
| Old name | New name |
| Data Warehouse Reports/Execution/Milestone Status using Weight | Data Warehouse Reports/Execution/Iteration Status using Weight |
| Data Warehouse Reports/Execution/Milestone Status using TCER Count | Data Warehouse Reports/Execution/Iteration Status using TCER Count |
| Data Warehouse Reports/Summary/Milestone Comparison | Data Warehouse Reports/Summary/Iteration Comparison |
| Data Warehouse Reports/Summary/Drill through/Defect List By Test Case and Milestone | Data Warehouse Reports/Summary/Drill through/Defect List By Test Case and Iteration |
| Data Warehouse Reports/Summary/Drill through/TCER List by Test Case and Milestones | Data Warehouse Reports/Summary/Drill through/TCER List by Test Case and Iterations |
| Reference Reports/Mini Report – Milestone Status using TCER Count | Reference Reports/Mini Report – Iteration Status using TCER Count |
Workaround
Complete these steps:
- Verify whether any of the old reports were customized. If any reports were customized, apply the same customizations to the corresponding new report.
- Manually delete the old reports.
Related information
Workaround summary
Problem
In Rational Quality Manager, when more than one defect is linked to a test case execution result, only one defect is populated in the data warehouse after the Quality Management data collection job is run. To populate all of the linked defects in the data warehouse, you must run the Work Items data collection job in Rational Team Concert.
Workaround
Complete these steps:
- Run the Quality Management data collection job.
- Verify whether any linked defects are missing. To do so, run the Execution and Defect by Owner report.
- If linked defects are missing, open Rational Team Concert and run the Delta Work Items data collection job.
- Verify again whether any linked defects are missing.
- If linked defects are missing, either change the missing defects in Rational Team Concert and run a Delta Work Items data collection job again, or run the Full Work Items data collection job in Rational Team Concert.
Related information
Workaround summary
Problem
After you create or delete a custom category or custom attribute, if you export a view to PDF format, the changes that you made might not be reflected in the PDF file. If you created categories or attributes, they are not shown in the PDF file. If you deleted categories or attributes, they are still shown in the PDF file.
This problem does not occur for all users. If you notice this problem, complete the workaround.
Workaround
Complete these steps:
- Go to the view that is not rendering correctly.
- Click the Change Column Display Settings icon.
- Click OK.
Related information
Workaround summary
Problem
This problem occurs when a test script is associated with a keyword that another script uses. If you modify the test script that is associated with the keyword, even though that script does not contain a keyword, a message in the script states that nested keywords are not allowed.
Workaround
Complete these steps:
- Open the problematic test script in a browser.
- Open the keyword that is associated with the script.
- Disassociate the test script from the keyword.
- Refresh the test script, modify it, and save it.
- Reassociate the test script with the keyword.
Related information
Workaround summary
Problem
If you import a QM process template that has nested categories with at least two child categories for a parent category, the subcategory values might be missing after the import process.
Steps to reproduce the problem:
- Create a category hierarchy with a category type that has two or more child category types at the same level.
- Export the process template from the Manage Project Area page.
- Import the process template that you exported in step 2.
- Create a project area by using the imported process template.
- Go to the Manage Project Properties page for the new project area. Only the last child category type has category values associated with it.
Workaround
Complete these steps:
- Create a project by using the imported template.
- Go to the Manage Project Properties page.
- Manually create the subcategory association for each child category type.
Related information
Workaround summary
Workaround summary
Workaround summary
Test case results cannot be opened if requirement links were removed from the associated test case and manual test script steps when in a read-only stateLimitation summary
Limitation summary
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
- Ugrading 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
© Copyright IBM Corporation 2014, 2016