HP Quality Center 10.00 Readme
Software version: HP Quality Center 10.00 / January 2009
Publication date: July 2009
This file provides information about Quality Center 10.00:
For detailed information about Quality Center, refer to the documentation set. To access the Quality Center Documentation Library from the main Quality Center window, choose Help > Documentation Library.
The first page of this readme document contains the following identifying information:
To check for recent updates or to verify that you are using the most recent edition, visit the following URL:
This site requires that you register for an HP Passport and sign-in. To register for an HP Passport ID, go to:
Or click the New users - please register link on the HP Passport login page.
You will also receive updated or new editions if you subscribe to the appropriate product support service. Contact your HP sales representative for details.
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: www.adobe.com.
For a list of new features in Quality Center 10.00, refer to the HP Quality Center What's New, available from Quality Center by clicking the Help button and choosing What's New.
For system specifications and installation instructions, refer to the HP Quality Center Installation Guide. This guide is located on the installation DVD in the Quality Center directory.
Notes and Limitations
- Windows 2003 64 bit: Working with Quality Center on an IIS 6.0 Web server is not supported on Windows 2003 64 bit.
Workaround: Manually configure IIS 6.0 on Windows 2003 64 bit. For more information, see HP Software Self-solve knowledge base article KM524615.
- Solaris/AIX: When you install Quality Center on Solaris or AIX in UI mode, you cannot select a license using the browse drill-down.
Workaround: Type the license file path manually.
- If a Site Administration database already exists, and during installation you choose 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.
- Quality Center does not support an empty Site Administration database schema password (previously Quality Center User Password) when configuring the advanced database server configuration options.
- Microsoft SQL database: Working with Quality Center on an SQL Server with Windows Authentication is not supported on operating systems other than Windows.
- Microsoft SQL database: When you upgrade the existing Site Administration schema or upgrade a copy of the existing schema on an SQL 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'.
- After you install Quality Center, Quality Center and Site Administration shortcuts are not created on the desktop.
Workaround: Use the shortcuts in the program folder (Start > Programs > HP Quality Center), or create a shortcut on the desktop from the <Quality Center installation directory>\shortcuts folder.
- Quality Center Starter Edition: Microsoft SQL Express database server is installed on the system drive, even if you selected to install Quality Center on a different drive.
- Quality Center Starter Edition: If port 8080 is in use by another application, Quality Center will be installed on port 8081. When the installation completes, the installation wizard page displays the Quality Center URL with port 8080 instead of port 8081.
Microsoft SQL Database
If your site uses SQL Server Eastern Collations or SQL Server Windows Authentication, we recommend that you install Quality Center 10.00 Patch 1 before deploying Quality Center in production.
Patch 1 will be available shortly after the release of Quality Center 10.00, and will address the following issues found in the connectivity layer of Quality Center when using an SQL Server database:
Windows Vista 32 Bit
To install and use a Quality Center client on Windows Vista 32 bit, consider the following installation prerequisites, installation process and other guidelines:
- Microsoft Installer version 3 or later
- Microsoft .Net Framework 3.5
- CAPICOM 184.108.40.206
- Microsoft Visual C++ 2005 Redistributable
- For Document Generator: MSXML 3.0
- Quality Center Explorer: To install the Quality Center Explorer Add-in, set the DEP level to either OptIn, AlwaysOff, or OptOut and exempt QCExplorerAddIn.exe. After you install, you can restore the DEP level.
- HP Screen Recorder Add-in: To install the HP Screen Recorder Add-in, set the DEP level to either OptIn, AlwaysOff, or OptOut and exempt the related .exe files.
- Previous installations of Quality Center must be completely removed. Unregister and delete all files.
- Spider Installation: Open the Web browser as administrator.
- MSI: Run the command prompt as administrator, and activate the MSI file.
- Quality Center Explorer: Run the command prompt as administrator, and activate Quality Center Explorer.
Working in Quality Center as standard (non-administrator) Vista user:
Web Server User Authentication
- IIS Web server: After installing Quality Center with the IIS Web server, you cannot connect to Quality Center until the ISAPI filter status is updated within IIS. This may take some time.
Workaround: Either wait until the filter status is updated automatically, or restart IIS.
- Windows 2003 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 Site and select Properties. Click the Services tab, and select Run WWW service in IIS5.0 isolation mode.
- Quality Center fails to upgrade projects where the Quality Center repository uses a mapped drive (non-UNC path) as the base repository path.
Workaround: In the Site Configuration tab of Site Administration, modify the base repository path from an absolute path to a UNC path.
- Quality Center 9.0: When you upgrade a Quality Center 9.0 project that contains workflow procedures, check that the workflow procedures do not have the same names as new workflow events. If they do, change the procedure names to avoid a naming conflict.
- Database schema: When deleting extra user columns from a database schema, verify that they are not defined in the SYSTEM_FIELD table.
- While running the verification, repair, or upgrade process, if you abort the process, the project will be corrupted.
- Project verification checks whether a project used legacy version control based on the Site Administration dbid.xml file alone, and does not verify that the VER_CTRL table is empty.
- When you upgrade a project, Quality Center creates a new requirement type for each distinct value of the Type field and assigns them to the requirements in the original project. If there are many such values, a large number of requirement types are created in the upgraded project.
Workaround: Before upgrading a project, clear the Type field of values that you do not want to be converted to requirement types.
- Microsoft SQL database: When working with a case sensitive SQL database, the upgrade process fails if the exception file contains an extra table in which the name is in lower case.
- Microsoft SQL database: Project verification does not include a check that the Microsoft SQL database administrator user is the owner of the project database.
- Oracle: When you upgrade Quality Center projects on an Oracle database, the size of the Oracle rollback segment (RBS) may increase when running large transactions. When you upgrade large projects (with a database size greater than 2 GB), it is recommended that you increase the RBS size for the duration of the upgrade so that it has at least 3 GB free. After the upgrade, you can change the RBS size to its size before the upgrade.
- The HP Quality Center Tutorial and HP Business Process Testing Tutorial will be available with Quality Center 10.00 Patch 1.
- You can view video demonstrations of main Quality Center features by choosing a movie from Help > Product Feature Movies. Note that video demonstrations for some features that were released prior to Quality Center 10.00 were not updated to reflect the most recent user interface changes. These videos are still relevant as they do demonstrate the concepts of the features.
- 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.
- When applying the REPLACE_TITLE parameter to the Management, Test Resources, and Dashboard modules, only the module name in the Quality Center sidebar is replaced.
- You cannot import Quality Center project export files (.qcp files) to Quality Center 10.00 if they were created in an earlier version of Quality Center.
- When restoring a project, you should select the dbid.xml file located in the project repository. This ensures that the project retains its original ID. If a project does not have its original ID, the following cross project features may not function properly: cross project customization, importing and synchronizing libraries, and cross project graphs.
Cross Project Customization
- When customizing requirement types in a linked project, user-defined fields applied from the template project cannot be set as required fields.
Workaround: In the template project, set the user defined fields as required fields, and then apply the customization to the linked project.
- Project customization applied to linked projects from a template project can be edited by using Open Test Architecture (OTA).
- Cross project customization reports that are saved as HTML files may display on another machine without formatting.
Workaround: Save the reports as the Web Archive, single file (*.mht) type.
- The following new features in Quality Center 10.00 may result in reduced system performance if used extensively: versioning, baselines, sharing entities, and cross project graphs. For more detailed performance information, refer to the Quality Center v10.00 Benchmark document, available in a future Quality Center patch.
- 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.
- The Favorites menu is unavailable in the Test Plan Tree view and Test Sets Tree view.
- The following 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 Quality Center using the File > New Window command in Internet Explorer, or by opening a new browser tab.
Workaround: To open another instance of Quality Center, open a new Internet Explorer window.
- When you open a new session in Quality Center, you might be prompted to install the Quality Center client even though it was installed the first time you ran Quality Center.
Workaround: In Internet Explorer, select Tools > Internet Options > General > Temporary Internet Files (Browsing History in Internet Explorer 7) > Settings > View Objects and delete Loader Class v4.
- When you expand Group by defect data where the group (second or third level group field) is hidden in Project Customization or workflow, an error message is displayed.
- If you use the data-hiding filter to hide data in a particular folder from a particular user group, and subsequently delete the folder, a user that belongs to the group is unable to log in to Quality Center.
Workaround: A project administrator should modify the data-hiding filter in Project Customization.
- After you specify a value in the Target Release, Target Cycle, Detected in Release, Detected in Cycle fields, you cannot then return them to blank fields.
- When copying an item from the Dashboard module or the Test Resources module to another project which already contains an item with the same name, Quality Center may display an inaccurate warning message. The item is copied nevertheless.
- Windows XP SP3: While running a system test remotely on a Windows XP SP3 client machine, an error message is displayed. For more information, see HP Software Self-solve knowledge base article KM187086.
- Windows XP SP3: When you create a report that includes rich text, you can view the rich text field only if ActiveX content is allowed to run 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.
- Test Resources: Checking out an older version of a test resource will not restore its dependencies as they were at the time of check in. The dependencies of the checked out version are the same as the checked in version.
- DATACONST table: Modifying the hist_directory and baselines_directory parameters in the DATACONST table will cause errors.
- Version control is not supported when working with the following test types: Vuser Script and LoadRunner scenario.
- In a version control enabled project, you cannot copy and paste entities that you have checked out. You also cannot copy and paste entities with related entities that you have checked out.
Workaround: Check in the entities before you copy and paste them.
- Manual tests: In a version control enabled project, an empty folder is created in the Tests repository folder for each manual test. This can increase the disk size of the project repository, and cause a strain on the file system.
- Attachments: If a test has attachments, but the corresponding files in the project repository were manually deleted, the test cannot be checked out.
Workaround: Remove the entries in the CROS_REF table that point to the deleted files.
- Rich text: The RichContent field of a checked in requirement is read-only, and cannot be edited until the requirement is checked out. You cannot check out a requirement automatically by editing the RichContent field.
Workaround: Check out the requirement and then edit the RichContent field.
- Requirements: After you create a new requirement in a version control enabled project, if you then select the parent requirement, the Check Out dialog box opens.
Workaround: Click Cancel to close the Check Out dialog box.
- HP Project and Portfolio Management Center: The Quality Center-PPM integration is not supported for Quality Center projects with version control enabled.
Releases Sub Module (Management)
- History is not preserved for release folders, releases, or cycles in the Releases module.
- 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 releases and cycles.
Workaround: Click the Refresh button to update the data in the graph.
Libraries Sub Module (Management)
- You cannot import a library that contains entities with special characters, for example: /\:"?'<>|*%. Entering special characters in Quality Center is not allowed. However, in Quality Center 9.0 or below, it was possible to add special characters by using either OTA or the HP Quality Center Microsoft Excel Add-in.
- Sharing of libraries is not supported between version control enabled projects and non-version control enabled projects.
- When importing a library that includes user-defined fields that are the same in the source project and the target project, they must be of the same length.
- In the Compare Libraries Tool dialog box, if an entity in a library was both modified and moved, it is only marked as Moved. When you then synchronize the library, only the movement is synchronized.
- When creating a baseline, if an attachment or script is missing from the file system, a warning will be written to the Quality Center server log file. The baseline is created nonetheless.
- When synchronizing a library with a baseline that includes an automated test converted from a manual test, the test is not synchronized.
- After synchronizing a source library with an imported library's baseline, you cannot view, in the Imported By tab, from which baseline the imported library was originally imported. In addition, after synchronizing an imported library with a source library's baseline, in the Imported From tab, you cannot view with which baseline the imported library was synchronized.
- In the Comparison Settings dialog box, selecting the Coverage check box in either the Requirements or Tests tab instructs Quality Center to consider coverage. To ignore coverage, the Coverage check box in both the Requirements and Tests tabs must be cleared. Therefore, if you select or clear the Coverage check box in a library that contains only requirements, for example, this setting is saved and also applied when comparing a library that contains only tests.
- 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.
Risk-Based Quality Management
- Upgrading projects: When upgrading projects from Quality Center 9.2, the following data is not preserved, as it is now obsolete:
- The testing time assigned for each Failure Probability at Full Testing Level, both in Project Customization and in overrides for individual requirements.
- The Testing Policy grid, both in Project Customization and in overrides for individual requirements.
To work with Risk-Based Quality Management after the upgrade, it is recommended that you perform assessment for the new Functional Complexity assessment factor on your assessment requirements and then analyze your analysis requirements.
- RBQM fields: The labels of the following requirement fields refer to "Business Impact" instead of "Business Criticality": RBQM Business Impact, RBQM Custom Business Impact, RBQM Effective Business Impact, RBQM Use Custom Business Impact.
Workaround: You can modify the labels of these fields manually in Project Customization.
- Version Control: Checked out requirements are not reflected in the risk analysis graph. However, when you drill down the graph, it does show the checked out requirements correctly.
Test Resources Module
- If you set the data hiding filter for test resources to hide the Resource File name field, the field is still visible in the Resource Viewer tab.
- You cannot upload a file to a resource if the file name contains a comma. You also cannot upload a folder to a resource if the folder name contains a comma.
- When uploading a folder with a file that has the same name as a file in the resource folder, the file is uploaded without deleting the original file.
Test Lab Module
- Pinned test sets: The following test types cannot be added to pinned test sets: Vuser Script, LoadRunner scenario, and WinRunner.
- Pinned test sets: When viewing details of a test instance in a pinned test set, the Baseline field is not available in the Test Instance Properties dialog box.
Workaround: You can display the Baseline field in the Execution Grid.
- Pinned test sets: When pinning a test set to a baseline, if a new baseline is created in the meantime, the new baseline does not appear in the Libraries tree.
Workaround: Log out and log back in to the project.
- Vuser scripts: Baselines that you create with Vuser scripts include only the script action, and not additional data included in the data subfolder, such as snapshots, and results.
- In the Test Set tree, if you select another test set while a tab other than Execution Grid is selected, and then create a report of the selected test set (Analysis > Reports > Report Selected), Quality Center opens an empty report.
Workaround: Select the Execution Grid tab and then run the report.
- 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, Quality Center adds or updates the entity correctly.
- Oracle: When you use the Text Search feature in Quality Center on an Oracle database, note that Oracle has a default stoplist for each supported language containing a list of stopwords. The search will not find words that are in the stoplist for the language in which the search is being performed. For more information, refer to the Oracle Text Supply Stoplist (http://download-uk.oracle.com/docs/cd/B19306_01/text.102/b14218/astopsup.htm#CEGBGCDF).
- Oracle: When you use the Text Search feature in Quality Center on an Oracle database, note that there are some special characters that function as search operators within Oracle. If you use some of them in the search expression, the search may not find the expected results. For example, if you search for the expressions 'a* a' or 'a%a', which contain the operators * or %, an error message may display.
- Graphs: When you generate a Progress Graph in the Dashboard module, the graph may display different information from that displayed in previous versions of Quality Center. This can occur when the field that you group by does not have the History option enabled in Project Customization, or the History option was not enabled at some time during the period shown in the graph.
- Excel reports: Users who belong to groups that have data-hiding filters, are able to access the restricted data through Excel reports.
Workaround: In Site Administration, add values to the SQL_QUERY_VALIDATION_BLACK_LIST configuration parameter, such as operators, and table names.
- Excel reports: In the Entities pane of the Query Builder, the VC_TEST version control table is not listed.
Workaround: Type the table name manually in the SQL query.
- When generating requirements, the sort options (Filter > View Order) are not generated in the document.
- 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.
- The following 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.
- 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.
- 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.
- QuickTest Professional: If the environment variable file associated with your test or component is stored in Quality Center and you modify it from the Quality Center Attachments tab, the changes are not applied until you reopen the test.
- QuickTest Professional: If you connect to Quality Center from QuickTest Professional using an SSL connection, and you click "No" in the Security Alert dialog box, the Quality Center Connection dialog box stops responding.
- QuickTest Professional: When launching a QuickTest Professional script from Quality Center using an SSL connection, the Security Alert dialog box opens. QuickTest Professional might stop responding when you click "Yes" in the Security Alert dialog box.
- QuickTest Professional: When launching a QuickTest Professional script from Quality Center, the user running the script must have read/write permissions for the system cache folder.
- WinRunner: When working in WinRunner 9.2, an error may occur when attempting to connect to a Quality Center project.
Workaround: Install the HP Quality Center Connectivity add-in from the HP Quality Center Add-ins page.
- WinRunner: The WinRunner test type does not support the following features: baselines, library comparison, entity comparison, and library synchronization.
- 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 Quality Center project whose subject paths are longer than 256 characters. When a WinRunner test uses GUI checkpoints, the test name reappears as a folder name under each result folder. This further restricts the length of valid test names.
Workaround: Make sure that the test name does not cause the full path name to exceed the maximum path name allowed by Quality Center.
- 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 Quality Center and the project is under Version Control, unexpected behavior may occur.
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 Quality Center project which does not contain any previously saved GUI maps, an error message may be displayed.
Workaround: Create a new WinRunner test and save it to the Quality Center project. Restart WinRunner and reconnect to the Quality Center project. You should now be able to save the GUI map to the Quality Center project without evoking the error message.
- The integration of Quality Center with other products is not Unicode compliant. Therefore:
- 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).
- Data that is sent to QuickTest from Quality Center (such as values for test, action, or component parameters) is not Unicode compliant.
- QuickTest results containing Unicode characters may appear corrupted in the Quality Center result grid. You can, however, open and view results containing Unicode characters in the QuickTest Test Results window.
- 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.
- 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.
Open Test Architecture/API and Workflow
- 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.
- Quality Center 9.0: If a Quality Center project calls an event using an event name from Quality Center 9.0, and the event has a different name in Quality Center 10.00, the workflow does not call the old event if there is a new corresponding event that returns a value.
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 Quality Center, you must manually update them to begin at 1.
- 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 Quality Center server. It is recommended that you designate automail fields when there is a low demand on the Quality Center server.
- The Run_MoveTo workflow event has been added to Quality Center 9.2 and higher. You should use this event to add code to run when entering the Manual Runner dialog box. If you are upgrading from Quality Center 9.0, you should move existing code from the ManualRun_EnterModule event to the Run_MoveTo event.
- The _FieldCanChange and _FieldChange workflow events are not activated when you select a value from a drop-down list. Instead, they are activated when the editor is no longer in focus.
- The NewValue parameter in the FieldCanChange workflow event does not return a value when changes occur to the Target Cycle or Target Release field values.
Workaround: Run the following script:
For i = 1 To NewValue.Count
where New Value is a list of ISysTreeNode objects.
- Workflow scripts run with the privileges of the logged-in user, not the privileges of the user who created the script. Scripts that use protected objects, like the Command object, may fail, depending on the project security settings and the group to which the user belongs.
- The Attachment_New and Attachment_CanDelete workflow events are not triggered in the Management module.
- Template Projects: After you create a template from a project with workflow scripts, you must convert all the workflow scripts. You do this in a single session using the Convert dialog box, which runs only the first time you open the Workflow Script Editor after creating the template.
Business Process Testing
The issues described below relate to working with business components, flows, 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.
- Working with QuickTest Professional: When working with QuickTest Professional and Business Process Testing, Quality Center 10.00 works only with QuickTest Professional 10.00.
- Importing and sharing libraries:
- You may encounter problems while working with baseline import or synchronization functionality for libraries containing business process tests, flows, or components. Full business process testing support for these options is planned for an upcoming Quality Center 10.00 patch.
- Components located in the root folder in the Component tree, in the Obsolete folder, and in the Component Requests folder are not included in the library import process.
- Working with version-controlled projects:
- In a version-controlled project, you cannot check in a business process test that is checked out by you, if it is currently opened by another user.
- In a version-controlled project, the status of a business process test is updated according to the status of checked-in components only.
- In a version-controlled project, you cannot open the Component Step Editor from the Component dialog box in Test Plan.
Workaround: Open the Component Step Editor from the Business Components module.
- After changing the snapshot of a requested component in a version-controlled project, the original snapshot is still displayed in the test script.
Workaround: Log out and log back in.
- In a version-controlled project, a Check Out confirmation request opens when you switch to the Automation tab of a checked-in component. This message should be displayed only if you try to edit the content in the Automation tab.
- When working with QuickTest keyword-driven components in a version-controlled project, if after adding one or more steps to a component, you view the comparison of component steps when comparing component versions or baselines, all of the steps that existed before updating the component are marked as deleted and all of the steps currently in the component are marked as new.
- In a version-controlled project, if you try to view the content of a scripted component from the baseline or version history, it always displays the current component content.
- Viewing dependency information for tests and flows: The Dependencies tab for business process tests and flows does not display Using and Used by information.
- Parameter task permissions required to add a component to a business process test: To add a component to a business process test or flow, permissions set for the user in Quality Center Project Customization must include all parameter task permissions.
- Canceling a New Component Request: To cancel a New Component Request, permissions set for the user in Quality Center Project Customization must include permissions to delete business components.
- Loading a snapshot: In the Snapshot tab of a component, you cannot load a file exceeding 9 MB using the Load from File button.
- Copying and pasting components:
- When copying and pasting between projects on a server using a Linux operating system, if you copy and paste a component and select to also copy the resources it uses, only the component and the function libraries are copied. Shared object repositories and recovery scenarios are not copied.
- There are a number of issues to consider when copying and pasting components. For more information, refer to the HP Business Process Testing User's Guide.
- Multiple clicks on the Save button: Repeatedly clicking the Save button in the Test Script tab in Test Plan can cause Quality Center to stop responding.
- Running business process tests remotely:
- When running a business process test or flow on a remote machine, an Access Denied error message may appear. This can occur when DCOM permission settings are incorrectly set on the remote host, when the user on the Quality Center client machine is not configured on the remote machine, or when the user does not have permissions to run the relevant remote agent via DCOM. (This is not a product limitation but a standard Windows DCOM security settings procedure.)
Workaround: The user on the Quality Center client machine should be configured on the remote machine, and should have permissions to run the relevant remote agent via DCOM. The user should also have the same password on both machines.
- To run business process tests on a remote host, the Quality Center client must be installed on the remote host.
- To enable Quality Center to run QuickTest Professional or WinRunner tests on a remote host, open the relevant application on the remote host and select the required option.
- In QuickTest, select Allow other HP products to run tests and components in the Options dialog box > Run pane.
- In WinRunner, select Allow other Mercury products to run tests remotely in the General Options dialog box > Run pane.
For more information, refer to the HP QuickTest Professional User Guide or the HP WinRunner User's Guide.
- Running a business process test with an empty flow: A business process test that contains an empty flow will fail when it is run.
Workaround: Add a component to the empty flow or remove the flow from the test.
- Running business process tests manually: 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).
- 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.
- Scrolling in the Value Configuration Options dialog box: Using the mouse to scroll through parameter names in the Value Configuration Options dialog box can cause Quality Center to crash.
- Incorrect display of parameters in an upgraded project: In an upgraded project, the list of parameters for a component is duplicated in the Details pane of the Run Results.
- Upgrading QuickTest Components: Components created in a Quality Center version 8.x project must be upgraded in a version 9.x project before upgrading to Quality Center 10.00. For more information, see the Quality Center 9.x Readme or refer to your Quality Center Site Administrator.
- Working with WinRunner components:
- When run from Test Lab, a business process test containing an iterated group that includes one or more WinRunner components will fail.
- WinRunner tests that are saved as scripted components in Test Plan are displayed as manual components in the Business Components module.
- Version control is not available for WinRunner components.
- WinRunner 8.2 components work the same way as they did in Quality Center 8.2. New Business Process Testing functionality for versions 9.2 or later is not supported for components created with WinRunner 8.2. For example:
- 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 Business Process Testing permissions.
- The InputLanguage to Quality Center must be the same as the ClientOSLocale and ClientOSAdvanceLocale. For example, if a user creates a defect with Japanese characters in the client, both settings above must be set to Japanese. Otherwise, the Japanese characters are not supported.
- Opening and updating a project that contains characters different from those set in the ClientOSLocale or ClientOSAdvanceLocale may cause irreversible damage.
- The InputLanguage inserted from an external component to Quality Center must be the same as the ClientOSLocale and ClientOSAdvanceLocale. For example, you cannot insert a QuickTest Professional script that contains Japanese characters in a client that runs on an OSLanguage with ClientOSLocale or ClientOSAdvanceLocale that is not Japanese.
- When sending mail that contains non English characters from the Quality Center client, it must be sent from the ClientOSLocale and ClientOSAdvanceLocale that are the same as the mail characters locale.
- To send mail that contains non-English characters, the MailServerVersion and MailClientVersion mail server must support non English characters.
- To display non-English characters, the OSLanguage needs to include the proper fonts for the language.
- The SiteAdminDBCollation and ProjectDBCollation must be set to the same language as the data insert. For example, inserting Japanese characters in a Korean collation is not supported.
- The Spell Checker tool is available only in English.
- Due to a problem in the JDBC driver's specific version, using Chinese and Japanese collation in MS-SQL may cause an error while executing some actions.
- You cannot create Quality Center projects with Thai characters in the project name.
- Microsoft SQL database: Applying customization of group permissions to linked projects is not supported on Asian platforms.
- The number of double-byte characters you can enter in a Quality Center edit box may be more limited than the number of characters specified in the relevant error messages. The number of characters that can actually be used depends on the server definitions and the character set that is being used. For example, one character can occupy 3 bytes when using Japanese characters with a server that is defined to work with UTF8.
- If your Quality Center server and Quality Center client do not use the same default encoding, and you send system information as an attachment, question mark characters may replace non-English characters in the attachment.
Workaround: Ensure that the Quality Center server and Quality Center client use the same default encoding.
- 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.
- Quality Center versions 9.2 and later support LDAP authentication using non-English character sets. Previously, login failed when passwords for LDAP-authenticated users contained non-English characters. To use non-English character sets, set the LDAP_CHARSET parameter in Site Administration to Default or add the relevant value listed in the Basic Encoding Set list (http://java.sun.com/j2se/1.4.2/docs/guide/intl/encoding.doc.html).
- To display localized UI, the OSLanguage of the client must use the same language as Quality Center.
- The UI language is defined by the Quality Center server and only one language can be defined per server.
- Vista: Quality Center Language Pack must be installed and operated on Windows where Windows native language (MLU*) is identical to the MUI* language.
- A Quality Center project created in an English edition cannot be upgraded to a localized edition.
You can visit the HP Software Support Web site at:
This web site provides contact information and details about the products, services, and support that HP Software offers.
HP Software online software support provides customer self-solve capabilities. It provides a fast and efficient way to access interactive technical support tools needed to manage your business. 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:
To register for an HP Passport ID, go to:
© Copyright 1993 - 2009 Hewlett-Packard Development Company, L.P.
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.
For information about third-party and/or open source license agreements, see the Licenses directory on the product installation media.
Adobe® and Acrobat® are trademarks of Adobe Systems Incorporated.
Microsoft®, Windows®, and Windows® XP, and Windows Vista® are U.S registered trademarks of Microsoft Corporation.
JavaTM is a US trademark of Sun Microsystems, Inc.
Oracle® is a registered trademark of Oracle Corporation and/or its affiliates.
Unix® is a registered trademark of The Open Group.
|© Copyright 2009 Hewlett-Packard Development Company, L.P.|