HP Business Process Testing for SAP Applications 2.00 Readme
Software version: 2.00
Publish date: January 2008
This file provides the following information about the HP Business Process Testing Enterprise Extension 2.00 version:
For detailed information about Business Process Testing for SAP Applications, please refer to the documentation set. In Quality Center, choose Help > BPT for SAP Applications Help or click a Help button in a Business Process Testing for SAP Applications dialog box.
Documentation
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: http://ovweb.external.hp.com/lpe/doc_serv/.
- In the Product list, click the product name.
- In the Version list, click the version number.
- In the OS list, click the OS type.
- In the document list, click the document title.
- 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: www.adobe.com.
System Requirements
To work with Business Process Testing for SAP Applications, the following products must be installed:
- HP Quality Center 9.2
- HP Quality Center 9.2 patch 7
- Business Process Testing Enterprise Extension (part of Business Process Testing for SAP Applications) installed and enabled
- HP QuickTest Professional 9.5 with the following QuickTest add-ins installed: SAP Solutions and Web
Note: Business Process Testing for SAP Applications supports testing on SAP Gui client only.
Your Quality Center and QuickTest computers must meet the system requirements of those products as defined in the documentation for each product.
The information in this section is correct at the time of this release. For the most updated QuickTest Professional and Quality Center system configurations, see:
QuickTest Professional Requirements: www.hp.com/go/QTP_SysReq
Quality Center Requirements: www.hp.com/go/TDQC_SysReq
Important Information
Licenses
To work with HP Business Process Testing Enterprise Extension, the following licenses are required:
- HP QuickTest Professional 9.50 license (per user)
- HP Quality Center 9.2 license (per user)
- Business Process Testing license (per user)
- Business Process Testing Enterprise Extension license (per server)
Note: The Business Process Testing Enterprise Extension option must be enabled for each relevant project using Quality Center Site Administration.
For information on receiving, installing, and enabling an HP Business Process Testing Enterprise Extension license, you can visit the HP Software Support Web site at: www.hp.com/go/hpsoftwaresupport.
Uninstalling Business Process Testing Enterprise Extension
After uninstalling HP Quality Process for SAP Applications on the Quality Center server, Business Process Testing Enterprise Extension functionality will no longer be available in the projects on that server. Any Quality Center projects with Business Process Testing Enterprise Extension enabled will become unstable.
Notes and Limitations
This section includes notes and limitations for the Business Process Testing for SAP Applications 2.00 release.
This section includes notes and limitations on the following topics:
General
- It may take 30-45 minutes to enable Business Process Testing Enterprise Extension when using an Oracle database.
- In order to ensure that proper permissions are set, when creating a new users group, base it on the "TDAdmin" group, and then remove any unnecessary permissions. Do not base a new group on the "Viewer" group.
- Business Process Testing for SAP Applications does not support output values on SAP table parameters or SAP table cells.
- Checkpoint property values are parameterized as component and flow parameters. The maximum length for component parameter values is 255 characters. The maximum length for flow parameter values is 70 characters. This causes long text of checkpoints property values to be truncated.
Workaround: If a long property value is needed for a checkpoint property, the component can be modified in QuickTest to use a static value in place of a parameterized value.
- Copying components, tests, test sets, and run entities from a project with Business Process Testing Enterprise Extension enabled to a project without Business Process Testing Enterprise Extension enabled and vice versa is not supported.
- During the Learn Flow process, resources are created which are stored in the BPT Resources folder. For the business process test to perform properly, this folder and any of its sub folders should not be renamed or deleted.
Learn Flows
- When the Record only the selected value when using a Possible Entries (F4) list check box is selected (Tools > Options, SAP tab, SAP GUI for Windows > Record settings), and pressing F4 populates more then one field during a learn session, only the field from which the F4 key was pressed will be populated during the run.
Workaround: Clear the Record only the selected value when using a Possible Entries (F4) list check box for these learn sessions.
- The start of the Learn Flow process may take some time due to internal data processing on pages that contain a large number of controls.
- To create or modify flow output parameters, you must have permission to create or modify component parameters.
Workaround: Set permissions in the Business Components tab of the Permission Settings For Group dialog box. For information on accessing and using this dialog box and tab, see the "Setting User Group Permissions" section in the HP Quality Center Administrator's Guide.
- SAP tab names sometimes contain extra space characters at the beginning of the tab name. These spaces at the beginning of tab names are trimmed when parameterized during the Learn Flow process. This causes a failure in the running of SAPGuiTab.Select operations.
Workaround: Modify the component for the SAPGuiTab.Select operation parameter to use a fixed value instead of the parameterized one.
Or
Use the 'BptAutoParamsFilter.xml' file to prevent the tab.select operation from being parameterized.
- After learning a flow and moving directly to one of the generated components of the flow (in the Business Components module), the component's Automation tab displays faulty object icons.
Workaround: Go back to the Test Plan module and refresh the Test Plan tree.
- During the Learn Flow process, component output parameters are not automatically promoted to flow output parameters.
Workaround: Promote component output parameter to flow output parameters manually, after the flow is learned.
- If a flow is created in a folder whose name contains the "(" or ")" characters with no space in front of them (or if one of the folder's names in the path contains these characters), the flow will fail to save during the Learn Flow process.
Workaround: Do not use "(" and ")" characters with no space in front of them, for test folder names.
Or
When the Learn Flow is complete, you can choose an alternate location for the saved components in the Learn Summary dialog - choose a location without "(" or ")" in its path.
Change Detection
- When learning a flow, if the number of objects in the screen changes dynamically, the dynamically created objects may not be learned and the change detection report may not be accurate.
- When a control with a step is removed from your application and the step is not removed through the Change Detection Report, in the next run the test will fail without changes.
Workaround: The step should be removed manually from the component.
- When a new control is detected in the Change Detection Report and you don't choose to add a step for it, it will not be detected again in the next Detect Changes run.
Workaround: A step can be added manually to the component for the new control.
- If a field becomes mandatory, it is not detected by running the component in Change Detection mode.
Change Detection Report
- You cannot copy and paste data to and from edit fields of the Change Detection Report using Ctrl+C and Ctrl+V.
Workaround: Right-click and use the context-sensitive menu to cut and paste in these fields.
- When the suggested resolution in the Change Detection Report is to add a step for a control, the Change Detection Report allows the user to insert any value for the new step. No validation is done on the value. The user is responsible to ensure that a valid value is used.
- If you rerun a component after running the component in change detection mode and after resolving changes using the Change Detection Report, all of the checkpoints and output values for that component may fail.
Multilingual Support
Support
You can visit the HP Software Support Web site at:
http://www.hp.com/go/hpsoftwaresupport
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:
http://h20230.www2.hp.com/new_access_levels.jspTo register for an HP Passport ID, go to:
http://h20229.www2.hp.com/passport-registration.htmlLegal Notices
© Copyright 2002 - 2008 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.
Adobe® is a trademark of Adobe Systems Incorporated.
Java™ is a US trademark of Sun Microsystems, Inc.
Microsoft® and Windows® are U.S registered trademarks of Microsoft Corporation.
If you have any comments or suggestions regarding this document, please send them by e-mail to SW-Doc@hp.com.
| © Copyright 2008 Hewlett-Packard Development Company, L.P. |