Workarounds and Limitations: Known issues in IBM Rational Quality Manager 5.0.1
The following known problems are related to Rational Quality Manager in the 5.0.1 release.
Workarounds
The following problems in this release have workarounds:
- Saved queries of execution records cannot be run when filters contain categories and results are grouped by an attribute
- Connection to the mobile client fails when the server has a self-issued SSL certificate that is signed by an internal certificate authority
- TeamServiceRegistryException occurs when you search QM artifacts after you restore the text index
- Problems opening the Rational Quality Manager importer from Microsoft Excel or Microsoft Word
- The reconciliation with requirement collections fails with a timeout error
- When you use the “OAuth” XDC Authentication Type, the Quality Management ETL fails
- Text in the editor might be displayed in a language that is not installed
- The generation of test cases to PDF reports fails with a java.lang.StackOverflowError exception
- 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:
- Execution variables cannot be created without a predefined value
- Online migration is not supported for upgrading some versions of the Quality Management application
Workaround summary
Problem
This problem occurs on the Test Case Execution Records page and the Test Suite Execution Records page. If a saved query contains filters for categories and the results are grouped by an attribute, you cannot run the query. When you try to run the query, a message states Unable to load the content. Unterminated object at line/column: line 1, column 1.
Workaround
Complete these steps:
- Either clear the category filters or from the Group By list, select Ungrouped.
- Save the query and run it.
- Optional: After you run the saved query, reapply the group by setting or the category filters. However, do not save the query again.
Related information
Workaround summary
Problem
When you use the Rational Quality Manager 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
Workaround summary
Problem
After you back up (repotools -backupJFSIndexes) and restore (repotools -restoreJFSIndexes), the test index, if you search QM artifacts, an error is logged in the Rational Quality Manager log:
com.ibm.team.repository.common.transport.TeamServiceRegistryException: CRJAZ2671E The "com.ibm.rational.test.lm.sequencer.service.internal.ExecutionSequenceInformationIndexingParticipant" service failed to activate because a service that it depends on, "com.ibm.rqm.common.service.IPagedSearchService", is not registered.
com.ibm.team.repository.common.transport.TeamServiceRegistryException: CRJAZ2671E The "com.ibm.rqm.execution.service.internal.query.ExecutionResultIndexingParticipant" service failed to activate because a service that it depends on, "com.ibm.rqm.common.service.IPagedSearchService", is not registered.
If any changes were made to the QM artifacts since the text index was backed up, they are lost.
Note: This issue impacts Execution Schedule and Execution Result artifacts.
When this issue occurs, artifacts are not in the full text index. You use that index when you search for QM artifacts from the search field in the upper-right corner.
Workaround
To retain the changes that were made to the QM artifacts since the text index was backed up, rebuild the text index by running this command: repotools -rebuildTextIndices.
Related information
Workaround summary
Workaround summary
Workaround summary
Workaround summary
Workaround summary
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
Problem
Typically, you can create an execution variable without a predefined value to use in a test script step. In this scenario, the value can be specified during execution. In the 6.0 release, the display of appending the specified value to the variable during execution was incorrect. The resolution was to ensure that a placeholder is set in the test script step for the value, which requires the execution variable to have a default value. This resolution caused the regression that the execution variable cannot be created without a predefined value.
Related information
Limitation summary
Online migration is not supported for upgrading some versions of the Quality Management application
© Copyright IBM Corporation 2014, 2017