Readme
Software version: 9.2 /
1 May 2007
This document provides the following information about Quality Center 9.2:
Known Problems, Limitations, and Workarounds
For a
list of the new features and other changes in Quality Center 9.2, refer to the HP Quality
Center What’s New, available from Quality Center by clicking the Help
button and choosing What’s New.
Note in
particular the following changes:
Database Schema Changes
Important changes were made to the database schema
structure in Quality Center 9.0. Consider carefully before upgrading from
versions of
The main changes are:
·
History data is no longer stored in the HISTORY table. It is now
stored in two new tables: AUDIT_LOG and AUDIT_PROPERTIES.
·
There have been some changes to the USERS table to specify
to which group a user belongs.
·
There has been a change in the implementation of defect linkage. Links are
now stored in the new
For more information about the structure of the database tables, refer to the HP Quality Center Database Reference. For a more detailed explanation of the changes to the database schema structure, refer to the TestDirector for Quality Center Knowledge Base (http://support.mercury.com) and search for Problem ID 44509.
New Workflow Event Naming Conventions
Changes have
been made to the naming of workflow events. The prefix indicating the module
has been removed from event names. For example, the event Defects_Bug_AfterPost
has been renamed Bug_AfterPost. In addition, two new workflow properties
have been added, providing information about the active module and dialog box.
For backwards compatibility, the previous naming convention is still supported.
If you upgrade a project containing workflow procedures with the same name as
new events, you must change the names of the procedures to avoid a naming
conflict. Note that in future versions of
Documentation Updates
The first page of this readme document contains the following identifying information:
· Version number, which indicates the software version.
·
Publish date, which changes each
time the document is updated.
To check for recent updates or to verify that you are using the most recent edition, visit the following URL:
http://ovweb.external.hp.com/lpe/doc_serv/
1
In the Product list, click the product name.
2
In the Version list, click the version number.
3
In the OS list, click the OS type.
4
In the document list, click the document title.
5
To retrieve the document, click Open
or Download.
NOTE: To view files in PDF format (*.pdf), Adobe
Acrobat Reader must be installed on your system. To download Adobe Acrobat Reader,
go to the following URL:
Installation requirements, as well as instructions for installing
Install.pdf in the \QualityCenter directory of the DVD
After installation the document can be found at:
[drive]:\<
doc_library\pdfs\Install.pdf
Installation and Migration Problems and Limitations
·
When you open Site Administration
immediately after installation, the icon next to the
·
When you upgrade projects from
·
If you try to upgrade a project
from Site Administration or using the Migration Tool and the project fails to
upgrade, it is not recommended to try to upgrade the project again.
Workaround: Restore a back up of the
·
Workaround: In the Site Configuration tab of Site Administration,
modify the base repository path from an absolute path to a UNC path.
·
If a Site Administration database
already exists, and you choose during installation to upgrade a copy of the
existing schema, the password for the default site administrator is not updated
with the new password you entered during installation.
Workaround: Use the password for the default site administrator in the
old schema to log in to Site Administration. You can then change the password
from the Site Users tab.
·
·
MSSQL Server: Working with
·
MSSQL Server: When you upgrade
the existing Site Administration schema or upgrade a copy of the existing
schema on an MSSQL server with SQL Server Authentication, the td user
must exist in the database and be the owner of all user tables.
Workaround:
Use the following SQL command to update the table owner in the database: sp_changeobjectowner
'<table_name>', 'td'.
·
Windows 2000 Professional:
The maximum number of connections to a shared folder in Windows 2000
Professional is ten. When the physical directory of a
·
Quality Center Checker: If you install Quality Center on an application
server other than JBoss, you are not able to run the Quality Center Checker.
Workaround: In the params.properties file, change the port value
of the SERVER_BASE_URL parameter to the port used by your application
server.
·
Oracle: When you upgrade
·
Solaris/AIX: When you install
Workaround: Type the license file path manually.
·
After you install
Workaround: Use the shortcuts in the program folder (Start
> Programs > HP Quality Center), or create a shortcut on the
desktop from the <
·
When you upgrade a project,
Workaround: Before upgrading a project, clear the Type field for values that
you do not want to be converted to requirement types.
·
WebSphere 5.1.1: Quality
Center 9.2 does not support WebSphere 5.1.1. It supports WebSphere 5.1.1.3 and
later.
·
WebSphere 5.1.1.3: When
installing Quality Center on a WebSphere 5.1.1.3 server, the “The maximum
length of 262144000 bytes has been exceeded” error message is displayed. This
is a WebSphere restriction that limits applications installed on a WebSphere
server to no larger than 250 MB.
Workaround: Configure the WebSphere server to
allow an installation of larger than 250 MB.
For more information, refer to the WebSphere Application Server 5.1.x Troubleshooting topic (http://publib.boulder.ibm.com/infocenter/wasinfo/v5r1//index.jsp?topic=/com.ibm.websphere.exp.doc/info/exp/ae/rtrb_installappprob.html), and
search for Application installation fails with MaxLengthExceededException
error if application is more than 250 MB.
·
If you try to log in to
· If you customization one of the client files which is digitally signed (for example Client.cab), the file need to be signed again with a digital signature. The digital signature needs to be a signature of a trusted provider. If you use a private signature, the file is not certified and therefore not valid.
Site Administration
·
Users cannot log in to a project after its connection string to the
database server is modified in Site Administration.
Workaround:
·
When a project is copied,
non-default values in the DATACONST table are not copied. For example,
the REPLACE_TITLE parameter.
Workaround: Manually insert the values into the DATACONST table
of the target project after the project has been copied.
·
The value of the Site
Configuration parameter REPLACE_TITLE cannot contain a percent (%) character.
Users will
not be able to perform add or delete operations for entities in the Defects
module if this character is included.
·
The REPLACE_TITLE parameter
is not supported in the Releases module and in the menu bar for any
·
The option to store the project
repository in the database, and the options to export and import
Web Server User Authentication
·
IIS Web Server: After
installing
Workaround: Either wait until the filter status is updated
automatically, or restart IIS.
·
IIS 6.0 Web Server: When
using an IIS 6.0 Web server on a Windows 2003 Server machine, Quality Center
may not respond when you type a URL with an IIS port (port 80). This can occur
if the IIS ISAPI filter is not loaded.
Workaround:
Configure IIS 6.0 to work in IIS 5.0 mode. Open the IIS manager (Start >
Run, and type inetmgr), right-click Web Sites and select Properties.
Click the Service tab, and select Run WWW service in IIS 5.0
isolation mode.
Requirements Module
·
The history of the Target Release and Target Cycle fields for
a requirement is not recorded.
· Microsoft Word 2000: When working with Microsoft Word 2000, a user can edit the rich text for a requirement, even if the user does not have permission to modify rich text. However, these changes will not be saved.
Releases Module
·
The Spelling and Grammar
options are not available in the Releases module.
· There are no workflow events for the Releases module.
· History is not preserved for release folders, releases, or cycles in the Releases module.
·
You cannot select users from the
users list for user list type fields in the Releases module.
Workaround: Type the user name in the field box manually.
·
When working in right-to-left mode
in a non-memo type field in the Releases module, the text is left-aligned while
the field is in focus.
·
If a user does not have permission
to modify a release folder, release, or cycle, the user is also unable to add
new release folders, releases or cycles.
Workaround: Make sure that users with permissions to add release
folders, releases, and cycles also have permissions to modify them.
·
The Progress and Quality graphs
may not automatically reflect changes made to entities assigned to release and
cycles.
Workaround: Click the Refresh button to update the data in the graph.
Analysis
· Document Generator: Due to a limit of nine header levels in Microsoft Word, only the first nine hierarchical levels are listed in the document Table of Contents.
· Document Generator: This limitation occurs if an attachment included in a project document is a Microsoft Word file, and you select the As expanded text option under Attachment Embedding Options in the Document Generator Options tab. In this case, the Document Generator might format the text and tables differently in the project document from how they are formatted in the original Word document.
·
Document Generator: This
limitation occurs if an attachment included in a project document is a
generated project document or a document with indexes, and you select the As
expanded text option under Attachment Embedding Options in the
Document Generator Options tab. In this case, the resulting project document
might be incomplete.
Workaround: Select the As icons option under Attachment
Embedding Options in the Document Generator Options tab.
·
Document Generator: If you select a Test Lab module graph to include
in a project document from the Test Sets, Tests, or Runs pages, the graph is
not included in the document.
Workaround: To include a Test Lab module graph in a project document,
select the graph from the Test Lab page in the Document Generator.
·
Reports: If you migrate a
project containing a custom report template from TestDirector 7.6 or earlier to
Quality Center 8.0 or higher, and subsequently change the data in a memo field
in an entity, a report generated containing this entity and using the custom
template may contain unwanted characters.
Workaround: In the URL box in the Report Configuration page, change
the URL for the report template to a URL for a report template created in
TestDirector 8.0 or
·
Graphs: When viewing the Defects-Summary
Graph, the Pie Chart tab is not available if the Data type is Sum
of.
·
Graphs: When you generate a Progress Graph in the
Analysis module, the graph may display different information from that
displayed in previous versions of
Text Search
· When you use the Text Search feature to search for a string that is also part of an HTML tag, such as body or html, all records containing formatted text that uses the tag will be found, as well as records containing the search string as text within a searchable field.
·
When you add or update an entity at the same time as the text search is
being enabled, you may receive an error message. However, after you close the
error message,
·
When you use the Text Search feature in
·
When you use the Text Search
feature in
Documentation
·
You may not be able to open the
API Reference help files directly from the Documentation Library Home Page.
This problem occurs when working with Microsoft Windows with Security Update
896358 installed. CHM files located on a remote server are not viewable on a
client machine with this configuration.
Workaround: Download the CHM files to your client
machine. For more information on this issue, refer to the Microsoft Knowledge
Base (www.support.microsoft.com) and search for article ID 896054.
General
· The Favorites menu is unavailable in the Test Plan Tree view and Test Sets Tree view.
· This limitation occurs when you create execution conditions in the Execution Flow such that two manual tests run only after another test has finished running. If you run the test set in the Automatic Runner, only one of the two manual tests runs. The status of the other test is listed as Running but the test does not run.
·
You cannot open multiple instances of
·
When you open a new session in
Workaround: In your Web browser, select Tools > Internet Options
> General > Temporary Internet Files (Browsing History in Internet
Explorer 7) > Settings > View Objects and delete Loader Class
v4.
·
Microsoft SQL Server: You can not add an attachment larger than 100 MB to a
· Windows XP SP2: The following error appears while running a system test remotely on a Windows XP SP2 client machine: “The RPC server is unavailable". For more information, refer to the TestDirector for Quality Center Knowledge Base (http://support.mercury.com) and search for Problem ID 33501.
·
If you are working with the Text
Search feature or Advanced Filters, and there is a high
load on the system, you may experience an impact on performance. In this
case, further iterative tuning and optimization of your environment and
specifically your database server will be required. If necessary, patches will
be provided in the future to address these issues.
·
You cannot import
· You cannot work in Hebrew in the HP Quality Center Login page and the Releases module.
· When you expand Group by defect data where the group (second or third level group field) is hidden in Project Customization or workflow, the following error is displayed: "List Index out of bounds".
·
Windows
XP SP2: When you create a requirement report that includes rich
text, you can view the rich text field only if ActiveX is running on your
machine.
Workaround: Open
Internet Explorer, select Tools > Internet Options > Advanced, and
under Security settings, enable the option to Allow active
content to run in files on My Computer. Restart Internet Explorer.
·
When you print a requirement
report that includes rich text, the rich text is truncated in the printed
document. You can still see all the rich text content in the html requirement
report.
·
If you use the data-hiding filter to enable a particular user group to view
data in a specific folder, and subsequently delete the folder, a user that belongs
to the group only is unable to log in to
Workaround: A project administrator should modify the data-hiding filter
in Project Customization.
·
To edit user-defined fields in the Design Steps tab in the Test Plan
module, you must have Test Lab Modify Run permission settings in Project
Customization.
Languages
·
The number of double-byte
characters you can enter in a
·
If your Quality Center server and
Quality Center client do not use the same default encoding, and you mail system
information as an attachment, question mark characters may replace non-English
characters in the attachment.
Workaround: Ensure that the
·
When you generate a document in
the Document Generator that includes test scripts with non-English characters,
these characters may appear as random ASCII text.
Workaround: Select As Icons for the Document Generator Attachment Embedding Options (and not As expanded text).
·
In the HP Quality Center Login
window, if the Domain or Project lists contain both Japanese and
English characters, empty items are displayed in these lists.
Workaround: Use either only English character or only Japanese
characters in your domain and project names.
·
If you create a password for a
user that includes Japanese characters from the Site Users tab of Site
Administration, authentication fails when the user tries to log in to Quality
Center.
Workaround: Set the password (that includes Japanese characters) from the
Project Customization window.
·
Quality Center 9.2 supports LDAP
authentication using non-English characters. To use non-English characters, set
the value of the LDAP_CHARSET parameter in the Site Configuration
tab of Site Administration either to “Default” to use the Quality Center server
default character set, or to the relevant value listed in the Supported
Encodings list (http://java.sun.com/j2se/1.4.2/docs/guide/intl/encoding.doc.html).
Integrations
·
When connecting to Quality Center
9.2 from previous version of testing tools (WinRunner 8.2, QuickTest
Professional 8.2.1, LoadRunner 8.0 Athena, or earlier), the “Failed create list
of projects” error message displays. This is due to the new login method
introduced in Quality Center 9.0.
Workaround: In the Site Configuration tab in Site Administration,
add the parameter BACKWARD_SUPPORT_ALL_DOMAINS_PROJECTS and set its
value to “Y”.
·
A user who has permission to add a defect, but not to modify it, will be
able to change the defect using the Find Similar Defects option in the Add
Defect dialog box invoked from the testing tool's Test Results window.
·
When you install a
Workaround: Run MSI
installer in non-interactive mode using the command msiexec /i QCClient.msi
/qb
· It is possible to fill list fields with invalid data in the Add Defect dialog box invoked from the testing tool's Test Results window.
·
If a test run from a testing tool has been converted to another type (such
as from WinRunner to LoadRunner) the user can still open it via the recent
files list in the original testing tool and work with it. No error is reported.
·
QuickTest Professional: If the environment variable file associated with
your test or component is stored in
·
QuickTest Professional: If you connect to
·
QuickTest Professional: When launching a QuickTest Professional
script from
·
QuickTest Professional: When launching a QuickTest Professional
script from
· WinRunner: When using the function qcdb_get_test_value, it fails to retrieve a TS_DESCRIPTION with a length greater than 983 characters.
·
WinRunner: WinRunner cannot work with tests in a
Workaround: Make sure that the test name does not cause the full path
name to exceed the maximum path name allowed by
· WinRunner: The locking mechanism does not work for GUI map files. If two users work concurrently on the same GUI map files, the changes of one user overwrite the changes of the other user.
·
WinRunner: If
WinRunner is working in Direct File Access mode with
Workaround: Verify that Direct File Access mode on your Quality Center
Server and Quality Center Client is disabled.
·
WinRunner: If you
save a GUI map created by the GUI Map Editor, to a
Workaround: Create a new WinRunner test and save it to the
· LoadRunner: The management of LoadRunner parameter files that include files from the Test Instance Properties dialog box in Quality Center is not supported. These files must instead be managed directly from LoadRunner.
·
LoadRunner: If you use
LoadRunner Analysis while you are connected to
·
¾ When working with tests or components stored in Quality Center, you should not use Unicode values (such as the name of the test or component, the name of an application area, the default value of a test, action, or component parameter, method argument values, and so forth).
¾
Data that is sent to QuickTest
from
¾
QuickTest results containing
Unicode characters may appear corrupted in the
Version Control
·
SourceSafe: The following
characters cannot be used in the user name or password for a
· SourceSafe: If you choose to store your project’s repository in the database, note that the Visual SourceSafe Version Control Add-in still stores version control history data in the file system. This data is stored in the vcs directory, which is located in the project’s directory under the repository directory. You must not delete or move the vcs directory.
·
SourceSafe: After you
upgrade or migrate a
· SourceSafe: After you upgrade a project, if you try to check in any test that was left checked out before the project was upgraded, a “Failed to check in” error message is displayed. You must check in all tests before you upgrade a project.
·
ClearCase: Version Control integration with Rational ClearCase
is not supported on AIX platforms.
·
ClearCase: During
installation of the HP Quality Center Rational ClearCase Version Control
Add-in, you are asked to type the VOB name. If you type the VOB name with a
slash (/), you cannot enable version control for
Workaround: During installation of the add-in, type the VOB name without
the slash. If you have already installed the add-in, in Site Administration,
remove the slash in the VC_VOB_NAME parameter or type the full path in
the VC_CC_PROJECT_ROOT parameter.
· In the Test Plan module, the Comments field value is not saved in Version Control history.
·
You cannot install version control
add-ins on
Workaround: Disable SSL on the
·
The
Open Test Architecture/API and Workflow
·
A new login module and new
login/logout methods have been introduced in the Open Test Architecture and
Site Administration API. For backwards compatibility, using the old methods is
supported in both
BACKWARD_SUP
·
In previous versions of
· The Defect Linkage (previously Defect Association) feature has been expanded, and it introduces new Open Test Architecture API objects. For backwards compatibly, adding links between defects and other entities through the BUG object from BG_REFERENCE fields is still supported. However, you should use the new LinkFactory and Link objects to get links from an entity.
·
In Project Customization in the
Workflow Script Editor, the TestSetTests_CanPost
workflow event is not listed in the Scripts Tree.
Workaround: To use this workflow event, type it into your
script.
·
When you upgrade a
·
If a
Workaround: To use an old event, remove the new event from the script.
·
When you use an Open Test Architecture (OTA) list, note that list
numbering begins at 1. For example, mylist.Item(1) refers
to the first item in the list myList. If you have used OTA
lists with numbering beginning at 0 in previous versions of
·
When you make changes to the
designated automail fields in the Automail page of Project Customization or in Open Test Architecture (OTA), this causes high CPU
consumption on the
·
The Run_MoveTo workflow
event has been added to Quality Center 9.2. You should use this event to add
code to run when entering the Manual Runner dialog box. If you are upgrading
from an earlier version of
Business Process Testing
The
issues described below relate to working with business components and business
process tests in Quality Center. For information on issues related to working
with business components in QuickTest Professional or WinRunner,
refer to the relevant product's readme file.
· Copying and pasting components: There are a number of issues to consider when copying and pasting components. For more information, refer to the Business Process Testing User's Guide.
·
Renaming scripted components: If you rename a scripted component
from Quality Center to the identical component name but with different
capitalization, the object is not recognized when opening the component in
QuickTest, and it is shown as Unknown
in the Keyword View.
Workaround: Rename the component to
a different name and then return it to the component name you want with the
desired capitalization. For example, if the component name was login, and you renamed it
to Login,
it is not recognized in the Keyword View in QuickTest. Rename the component to oldlogin, and then back to
Login.
The Keyword View then displays it correctly.
·
Running business process tests remotely: To run business process
tests on a remote host, the
·
Running business process tests manually: Consider the following
issues when running business process tests manually:
¾
If you set default values for
run-time parameters, and then run a business process test from the Test Lab
manually, the default run-time values are not used.
Workaround: Open the Test Iterations dialog box from the Test Lab and then click OK to
confirm the default values.
¾ When you select to continue a manual
run and then you make changes in the Manual Runner dialog box, the changes in
the run are always saved (you are not asked whether to save the changes when
you exit the Manual Runner).
·
Upgrading QuickTest Components: When upgrading a project from
¾
To work with QuickTest components
(keyword-driven or scripted) in Business Process Testing 9.2, you must use
Quality Center 9.0 or later and QuickTest Professional 9.0 or later. You cannot
store QuickTest 9.0 or
later components in a
¾
After upgrading a project from
¾ If you created a business component
in QuickTest 8.2.x without an associated application area, then when you open
it in QuickTest 9.0 or later to convert it to the 9.0 or later format, any
customized business component settings are cleared, and therefore
the business component run will fail.
Workaround: After converting the business component, you must
associate it with an application area that contains the required resources and
settings.
¾
If you created a keyword-driven
component in QuickTest 8.2.1 and then try to run it manually in Quality Center
9.2, the information in the steps will be identical to the information from the
Documentation column. For example, the steps will not display actual values for
parameters.
Workaround: Open and save the component in QuickTest 9.0 or later. Then run the business process
test manually. All steps will be converted to the 9.2 format.
¾
When you copy a component created
using Business Process Testing 9.2 to another project, its application area is
automatically copied, as described in the HP
Business Process Testing User's Guide. However, the shared object
repositories that are saved in
¾ For components created in version 8.2.1 or earlier, when you copy a component created in an older version to another project, you must copy the application area and all of its associated resources manually. Otherwise you will be unable to open the component for editing in QuickTest, and business process tests containing these components will fail.
¾ If you created a non-automated component with steps and then converted
it to a keyword-driven component in
·
Working with WinRunner components: WinRunner 8.2 components work
the same way as they did in
¾ When converting a manual component to a WinRunner scripted component, only the step descriptions are converted to comment text. The new step name and expected value items are not included in the comment text.
¾ To enable a user to work with a WinRunner 8.2 component, the user must have WinRunner test permissions in addition to the new Business Process Testing permissions.
Mercury Product Support
You can obtain support information for products formerly produced by
Mercury as follows:
If you work with an HP
Software Services Integrator (SVI) partner (www.hp.com/managementsoftware/svi_partner_list), contact your SVI agent.
If you have an active HP
Software support contract, visit the HP Software Support site and use the
Self-Solve Knowledge Search to find answers to technical questions.
For the latest information about support processes
and tools available for products formerly produced by Mercury, we encourage you
to visit the Mercury Customer Support Web site at: http://support.mercury.com.
Contact your HP Sales
Representative if you have additional questions.
HP Software Support
You can visit the HP Software
Support Web site at:
www.hp.com/managementsoftware/services
HP Software online support
provides an efficient way to access interactive technical support tools. As a
valued support customer, you can benefit by using the support site to:
·
Search for knowledge documents of interest
·
Submit and track support cases and enhancement requests
·
Download software patches
·
Manage support contracts
·
Look up HP support contacts
·
Review information about available services
·
Enter into discussions with other software customers
·
Research and register for software training
Most of the support areas
require that you register as an HP Passport user and sign in. Many also require
a support contract. To find more information about access levels, go to:
www.hp.com/managementsoftware/access_level
To register for an HP Passport
ID, go to:
www.managementsoftware.hp.com/passport-registration.html
© Copyright 1993 - 2007 Mercury Interactive Corporation, All rights reserved.
Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license.
The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein.
The information contained herein is subject to change without notice.
Adobe® and Acrobat® are trademarks of Adobe Systems Incorporated.
Microsoft®, Windows®, and Windows XP® are U.S registered trademarks of Microsoft Corporation.
Oracle® is a registered U.S trademark of Oracle Corporation,
Document Number
QCRM9.2/01