QuickTest Professional
Web Services Add-in 9.1
ReadMe

This file provides the following information about the QuickTest Professional Web Services Add-in:

Overview
Customer Support
System Requirements
Supported Environments and Programs
Third-Party Licenses
Useful Information
Known Problems and Limitations

Overview

The QuickTest Professional Web Services Add-in enables you to create and run tests on Web services using specially customized functionality.

In addition, the customized WebService test object, methods, and properties make scripts simple to read, maintain, enhance, and parameterize, enabling both advanced and novice users to create sophisticated tests on Web services.

For more information on the QuickTest Professional Web Services Add-in and for details and syntax of the WebService test object and methods, refer to the QuickTest Professional Web Services Add-in Guide and the Web Services section of the Object Model Reference Help.

Customer Support

Technical support for QuickTest Professional and the QuickTest Professional Web Services Add-in is provided via our award-winning Customer Support Web Site. From this Web site, customers are able to review Frequently Asked Questions, submit and check the status of support requests, and access online documentation, patches, and other downloads. Please visit the Customer Support Web Site at:

http://support.mercury.com

Customer Support contact numbers all over the world are available at:

http://support.mercury.com/cgi-bin/portal/CSO/contacts.jsp

System Requirements

To work with the QuickTest Professional Web Services Add-in, your system configuration should meet the requirements for QuickTest Professional 9.1 (as specified in the QuickTest Professional 9.1 Readme), plus the following add-in specific requirements:

Prerequisites:

QuickTest Professional, version 9.1.

Free Hard Disk Space:

110 MB of free disk space on which you want to install the Web Services Add-in (depending on your feature selection), in addition to the space required for the QuickTest Professional installation. In addition, the disk on which Windows is installed (system disk) requires 110 MB of free hard disk space while the Web Services Add-in is being installed. After the installation is complete, 25 MB of this disk space is released (meaning that 85 MB of the system disk remains in use by QuickTest Professional).

Supported Environments and Programs

The QuickTest Professional Web Services Add-in supports the environments and programs listed in the sections below.

Toolkits

Microsoft .NET Framework 1.1 WSE 2.0 Service Pack 3
Microsoft .NET Framework 2.0 WSE 3.0
Apache Axis 1.x (Apache Axis 1.4 installed with the Web Services Add-in)

Other Environments and Applications

WS-I Interoperability Testing Tools 1.1-Required for validating WSDL interoperability

Third-Party Licenses

===========================================================

NOTICE file corresponding to section 4(d) of the Apache License,

Version 2.0, in this case for the Apache Axis distribution.

===========================================================

This product includes software developed by The Apache Software Foundation (http://www.apache.org/).

Useful Information

QuickTest accesses the WSDL to learn WebService test objects and to run operations on Web services. If your WSDL is located on a secure server or if the network connection is secure, it is recommended that you save the WSDL (and any additional resources used by the WSDL) to a local drive before learning Web service test objects and running Web service tests or components. In addition, if you choose a WSDL from a file, you should always use an absolute path or a Quality Center path when specifying the WSDL to use.

Known Problems and Limitations

General

The Web Services Add-in uses the toolkit specified in the Web Services tab of the Options and Test Settings (or Application Area Settings) dialog boxes to learn WebService objects and run Web service operations. If the WSDL file does not work with the toolkit type selected in these dialog boxes, the add-in cannot learn or run Web service steps.
In some cases, when trying to send very large numbers to a Web service during a run session, QuickTest sends incorrect values.

Workaround: Send the number as a string. (You can use the VBScript CStr function to convert numbers to strings.)

Creating and Running Tests and Components

If you create a checkpoint or output value step for an operation that returns a multi-dimensional array (or perform an update run on such a step), the XML tree is generated for only one dimension of the array.
If a WebService test object was learned using the QuickTest Professional 9.0 Web Services Add-in:
In IntelliSense, there will not be a separator between the Web service operations and the WebService test object operations.
QuickTest will not be able to generate XMLWarehouse objects for this test object.

Workaround: Learn the WebService test object again.

When you run several steps on a test object that uses a programmatic description, each step creates a separate instance of the test object. If one of these steps performs an operation that modifies the test object in some way, and the following step performs its operation on a new instance of that object, the second step may fail.

For example, if you run a SetClientConfiguration operation on a WebService test object using a programmatic description, and then you run another step on a WebService test object with the same description, the second step performs its operation on a separate instance of the WebService test object and not on the test object for which the configuration was set.

Workaround: Store the test object with the programmatic description in a variable and create steps using the variable. For example, instead of:

WebService(wsDescription).Configuration.SetClientConfiguration "", "<configurefile>"

echoString=WebService(wsDescription).echoString("salem ")

WebService(wsDescription).Check CheckPoint("echoString")

Use:

Set oWebService = WebService(wsDescription)

oWebService.Configuration.SetClientConfiguration "", "<configurefile>"

echoString=oWebService.echoString("salem ")

oWebService.Check CheckPoint("echoString")

Web Service Testing Wizard

If you create a test or component using the Web Service Testing Wizard in the Keyword View, and you select to include many WSDL operations, it may take some time for QuickTest to create the test or component steps after you click the Finish button.

Workaround: Switch to Expert View before using the Web Service Testing Wizard.

When creating a test or component using the Web Service Testing Wizard, if the Web service operation expects an array of complex types, QuickTest will automatically generate the array but not the structure.

Workaround: Edit the XML structure to reflect the expected type. For example, suppose that the Web service expects an array of Struct objects. In this case, the generated XML would be similar to the following:

<Struct xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://examples.ws.mercury.com">

    <firstName>String</firstName>

    <lastName>String</lastName>

</Struct>

In this case, you would replace the XML with the following:

<ArrayOfStruct xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">

    <Struct>

        <firstName xmlns="http://examples.ws.mercury.com">kuku</firstName>

        <lastName xmlns="http://examples.ws.mercury.com">bubu</lastName>

    </Struct>

</ArrayOfStruct>

Microsoft .NET Framework WSE Toolkit

The .NET toolkit may not support an array of arrays as an input or output argument value for a WebService operation.
SOAP requests with DIME attachments are not displayed in the test results when using the .NET toolkit. (Relevant only for Microsoft .NET Framework 1.1 WSE 2.0)
If your Web service requires security features that are not available using the WebService().Security object, you can use a policy file to define the configuration for the service.

For example:

Take the app.config and wse3policyCache.config files from a working Web service client. Then verify the policy name that was used in the client. (It should also appear in wse3policyCache.config file under <policy name="...">)

Then, run the following steps in QuickTest:

' Set security options for the "SecureInvoiceService" Web service

WebService("SecureInvoiceService").Configuration.SetClientConfiguration "C:\MyPolicies\app.config","C:\MyPolicies\wse3policyCache.config","MyClientPolicy"

tokenID = WebService("SecureInvoiceService").Security.AddUsernameToken ( micRequest, "jsmith", "p@ssword", micPlainText )

' SecureInvoiceService Web service object steps

Set StockQuoteRequest = WebService("SecureInvoiceService").StockQuoteRequest(Array("CONTOSO","FABRIKAM"))

WebService("SecureInvoiceService").Check CheckPoint("StockQuoteRequest")

Apache Axis Toolkit

When a Web service operation returns an object of Entities (org.apache.axis.type.Entities), the returned value is always empty.

Workaround: Retrieve the Entities value by running a LastResponse statement on the WebService object and then parsing the returned XMLData object using XMLData methods and properties.

Tests that were created using the QuickTest Professional 9.0 Web Services Add-in and Apache Axis 1.2.1, and that contain an array of simple types, may not run properly using QuickTest Professional 9.1 Web Services Add-in.

Workaround: Recreate the relevant steps (service calls) in QuickTest.

If your Web service contains a DocEncoded type and was created using Microsoft .NET Framework 1.1 or 2.0, the service may not run properly using the Axis toolkit.
If your Web service includes two operations with the same name, the Axis toolkit may not work with that service. (This is a known Axis toolkit bug.)

This document, and the accompanying software and other documentation, is protected by U.S. and international copyright laws, and may be used only in accordance with the accompanying license agreement. Features of the software, and of other products and services of Mercury Interactive Corporation, may be covered by one or more of the following patents: United States: 5,511,185; 5,657,438; 5,701,139; 5,870,559; 5,958,008; 5,974,572; 6,137,782; 6,138,157; 6,144,962; 6,205,122; 6,237,006; 6,341,310; 6,360,332, 6,449,739; 6,470,383; 6,477,483; 6,549,944; 6,560,564; 6,564,342; 6,587,969; 6,631,408; 6,631,411; 6,633,912; 6,694,288; 6,738,813; 6,738,933; 6,754,701; 6,792,460 and 6,810,494. Australia: 763468 and 762554. Other patents pending. All rights reserved.

U.S. GOVERNMENT RESTRICTED RIGHTS. This Software Documentation is a "commercial item" as defined at 48 C.F.R. 2.101 (October 1995). In accordance with 48 C.F.R. 12.212 (October 1995), 48 C.F.R. 27.401 through 27.404 and 52.227-14 (June 1987, as amended) and 48 C.F.R. 227.7201 through 227.7204 (June 1995), and any similar provisions in the supplements to Title 48 of the C.F.R. (the "Federal Acquisition Regulation") of other entities of the U.S. Government, as applicable, all U.S. Government users acquire and may use this Documentation only in accordance with the restricted rights set forth in the license agreement applicable to the Computer Software to which this Documentation relates.

Mercury, Mercury Interactive, the Mercury logo, the Mercury Interactive logo, LoadRunner, WinRunner, SiteScope and TestDirector are trademarks of Mercury Interactive Corporation and may be registered in certain jurisdictions. The absence of a trademark from this list does not constitute a waiver of Mercury's intellectual property rights concerning that trademark.

All other company, brand and product names may be trademarks or registered trademarks of their respective holders. Mercury disclaims any responsibility for specifying which marks are owned by which companies or which organizations.

Mercury provides links to external third-party Web sites to help you find supplemental information. Site content and availability may change without notice. Mercury makes no representations or warranties whatsoever as to site content or availability.

Mercury Interactive Corporation
379 North Whisman Road
Mountain View, CA 94043
Tel: (650) 603-5200
Toll Free: (800) TEST-911
Customer Support: (877) TEST-HLP
Fax: (650) 603-5300

QTPWSRM9.1/01