Info: QTP 10 Web 2.0 Toolkit erschienen

Info: QTP 10 Web 2.0 Toolkit erschienen

Beitragvon daniel am Di Okt 06, 2009 8:42 am

Folgender Link zu Support: http://h20230.www2.hp.com/selfsolve/document/FID/DOCUMENTUM_QTPWEB_00044

Provides installations for Extensibility Accelerator including all required prerequisites, QuickTest add-in support for Silverlight 2 and 3, and QuickTest add-in support on controls from ASP.NET Ajax, Google Web Toolkit (GWT), Dojo Toolkit, and Yahoo User Interface (YUI) toolkits.

Out of the box” support for the most common Web 2.0 technologies, including:
o Silverlight 3.0
o Ajax :
ASP.NET AJAX (from Microsoft)
GWT (from Google)
YUI (from Yahoo)
Dojo (open source)
daniel
 
Beiträge: 54
Registriert: Do Jun 04, 2009 11:56 am

Re: Info: QTP 10 Web 2.0 Toolkit erschienen

Beitragvon daniel am Di Aug 03, 2010 5:21 pm

QTP Web 2.0 Toolkit verbessert - untenstehend die Funktionalitäten
Ăśber HP Support mit Patchname: QTPWEB_00048 zu beziehen.

Web 2.0 Feature Pack for HP Functional Testing Readme

Publication date: November 2009

This file provides the following information about the Web 2.0 Feature Pack for HP Functional Testing:

* Overview
* System Requirements
* Installation
* Notes and Limitations
* Legal Notices

Overview

The controls in Web 2.0 applications are feature-rich and dynamic, requiring sophisticated and flexible testing capabilities. The Web 2.0 Feature Pack for HP Functional Testing provides a set of new tools, enhancements, and add-ins that improve and facilitate Web 2.0 application testing.

This pack includes:

* Extensibility Accelerator for HP Functional Testing. Provides a Visual Studio-like IDE that accelerates and facilitates the design, development, and deployment of QuickTest Web Add-in Extensibility support sets. These support sets extend the Web Add-in so that you can test Web controls that are not supported out-of-the-box.
* Web 2.0 Toolkit Support for QuickTest Professional 10.00. Provides full QuickTest support on controls from ASP.NET Ajax, Google Web Toolkit, Dojo Toolkit, and Yahoo User Interface toolkits.
* Silverlight Testing Support for QuickTest Professional 10.00. Provides support for Silverlight 2 and 3 when working with the QuickTest .NET Add-in.

System Requirements

The system requirements differ for each component of the Web 2.0 Feature Pack for HP Functional Testing.

This section describes the system requirements for the following:

* Extensibility Accelerator 1.10 for HP Functional Testing System Requirements
* Web 2.0 Toolkit Support for QuickTest Professional 10.00 System Requirements
* Silverlight Testing Support for QuickTest Professional 10.00 System Requirements

Extensibility Accelerator 1.10 for HP Functional Testing System Requirements
Computer/Processor:

PC with a Pentium III or higher (Pentium IV or higher recommended) microprocessor.
Operating System:


* Windows XP Professional 32-Bit Edition—Service Pack 2 or Service Pack 3
* Windows XP Professional 64-Bit Edition—Service Pack 2
* Windows Vista 32-bit Edition or Windows Vista 32-bit Edition—Service Pack 1
* Windows Server 2003 32-Bit Edition—Service Pack 2


Permissions:

You must be logged in to your computer with administrative permissions to install and to use Extensibility Accelerator.
Memory:

Minimum of 512 MB.
Color Settings:

Minimum of High Color (16 bit).
Graphics Card:

Graphics card with 4 MB video memory (8 MB and above recommended)
Free Hard Disk Space:

30 MB of free disk space for the Extensibility Accelerator installation.
Additional space is required if you install one or more of the prerequisite programs.
Browser:

To use Extensibility Accelerator, you must have one of the following Microsoft Internet Explorer versions installed on your computer.

* Microsoft Internet Explorer 6.0 Service Pack 1
* Microsoft Internet Explorer 7.0
* Microsoft Internet Explorer 8.0



Web 2.0 Toolkit Support for QuickTest Professional 10.00 System Requirements

You can install and run the Web 2.0 Toolkit Support for QuickTest Professional 10.00 only on a computer that has QuickTest Professional 10.00 with the Web Add-in installed.

If you want to install the Web 2.0 Toolkit Support for use with Quality Center on a computer where QuickTest Professional is not installed, extract the ZIP file as described in the installation instructions, and then manually copy the files from:
<Web 2.0 pack installation folder>InstallDir\Toolkits\dat\Extensibility\Web to:
<QuickTest Add-in for Quality Center>\dat\Extensibility\Web
Silverlight Testing Support for QuickTest Professional 10.00 System Requirements

To successfully install and run Silverlight Testing Support for QuickTest Professional 10.00, your computer must meet the following minimum system requirements:

* .NET Framework 3.0 or later.
* QuickTest Professional 10.00 with the QuickTest Professional .NET Add-in installed.

If you want to install the Silverlight testing support for use with Quality Center on a computer where QuickTest Professional is not installed, extract the ZIP file as described in the installation instructions, and then install the qfe.msp file located in the <Web 2.0 pack installation folder>\InstallDir\SilverlightQC folder.
Installation
Selecting the Installation File

You can select from the following files:
File

Description
Web2Pack (With PreReq).zip

Select this file if:

* You are installing Extensibility Accelerator and do not have Microsoft Visual Studio 2008 SP1 and .NET Framework 3.5 SP1 installed on your computer.

When installing the Extensibility Accelerator, the installation recognizes if you are missing one or more of the following prerequisites and will prompt you to install them:

o .NET Framework v3.5 SP1
o Microsoft Visual C++ 2008 Run-time Components
o Visual Studio 2008 Shell (isolated mode) with SP1 Redistributable Package
* You are installing Silverlight Testing Support and you do not have .NET Framework 3.0 or later installed on your computer.

You can manually install .NET Framework v3.5 SP1 from: <Extracted Install Folder>\InstallDir\EA\Common\dotnet35_sp1\dotnetfx35_sp1.exe
Web2Pack.zip

Select this file if one or more of the following is applicable:

* You are installing Extensibility Accelerator and have Microsoft Visual Studio 2008 SP1 and .NET Framework 3.5 SP1 installed on your computer.

Note: If you have Visual Studio 2008 installed on your computer, verify that you also have Service Pack 1 installed.

* You are installing Silverlight Testing Support and you already have .NET Framework 3.0 or later installed on your computer.
* You are installing Web 2.0 Toolkit Support.



Installing the Web 2.0 Feature Pack for HP Functional Testing

1. Make sure that your computer meets all system requirements as described in System Requirements and that you selected the correct .zip file as per the prerequisites described in Selecting the Installation File.
2. Log on with Administrator privileges.
3. Close any instances of QuickTest Professional. It is also recommended to close all other open applications, as you may be prompted to restart your computer.
4. Save the .zip file to your file system or a network drive, and extract the content to folder in your file system. (Make sure that the Use folder names option is selected in your zip extraction application.)

Note: To ensure that the Add or Remove Programs > Repair/Remove functionality will be available after you install, you must keep the complete extracted content in the location from which you initially install.

The extracted folder contains the following:
* Setup.exe file
* InstallDir folder
* QTPWeb2SupportReadme.htm file
5. Double-click Setup.exe. The Setup window opens.
6. Select one or more of the options and click Install.
7. Follow the on-screen instructions for each installation.

The following elements are installed:
Option

Installed Elements
Extensibility Accelerator 1.10 for HP Functional Testing

* Prerequisites (if relevant), as specified in Selecting the Installation File
* Extensibility Accelerator 1.10 full installation
Web 2.0 Toolkit Support for QuickTest Professional 10.00

* Add-in support for controls in ASP.NET Ajax, Google Web Toolkit, Dojo Toolkit, and Yahoo User Interface toolkits.

For each supported toolkit the following is installed:
o .js test object files
o .xml test object class files
o Object Model Reference documentation
o Test object class icons
o Readme file
* Web Add-in and Web Add-in Extensibility updates including:
o Updated .dll and .xsd files
o Web and Web Add-in Extensibility documentation
Silverlight Testing Support for QuickTest Professional 10.00

* Updated .dll and .map files
* Add-in Guide and Object Model Reference documentation
* Patch readme file


Notes and Limitations

This section contains information and limitations for each installed component.

* Extensibility Accelerator 1.10 for HP Functional Testing Notes and Limitations
* Web 2.0 Toolkit Support for QuickTest Professional 10.00 Notes and Limitations
* Silverlight Testing Support for QuickTest Professional 10.00 Notes and Limitations

Extensibility Accelerator 1.10 for HP Functional Testing Notes and Limitations
General

* If you install the QuickTest .NET Add-in Extensibility SDK after installing Extensibility Accelerator on a computer where Visual Studio 2008 is not installed, the .NET Add-in Extensibility SDK installation fails.

Workaround: Install the SDK before installing Extensibility Accelerator.
* If you install the Microsoft Script Debugger after Extensibility Accelerator is installed, you cannot use the Debug Test Object Operation command to debug your JavaScript functions.

Workaround: Uninstall the Microsoft Visual Studio 2008 shell (isolated mode) and reinstall it.
1. The program appears in the list of programs in the Add or Remove Programs dialog box.
2. The program is available for installation in the Web2Pack (With PreReq).zip file: \InstallDir\EA\Common\vs2008_shell_sp1_isolated_redist\vs_shell_isolated.enu.exe
* Extensibility Accelerator does not support multiple open projects. However, if you open a project using the Recent Projects menu command when a project is already open, Enterprise Extension does not close the first project.

Workaround: Close any open projects before selecting a project using the Recent Projects menu command.
* Project names cannot include spaces or any of the following characters: ~!@$^()
* Creating a test object class with a name ending in an underscore and a number (for example, TButton_1) may result in unexpected behavior.
* When defining names for the elements listed below, use only English (Roman) letters, numbers, and underscores (A-Z, a-z, 0-9, _), and do not begin the name with a number:
o Test object classes
o Operations
o Operation arguments
o Properties
o Enumerations (names and values)
* If a JavaScript implementation file that you import into the Extensibility Accelerator project has the same name as another JavaScript file in the project, the file you import overwrites the existing one.

Workaround: Make sure to use a unique name for each implementation file.
* The Debug Test Object Operation option does not support debugging JavaScript functions in files other than the default implementation file and the common implementation file.

Workaround: Write your functions in the default implementation file or the common implementation file, at least during the debugging stages.
* Description elements inside Argument elements are not supported in the test object configuration XML file. If you import a support set with an XML file that contains these, or you add such elements manually to an existing XML file in an Extensibility Accelerator project, those elements are deleted from the XML file.
* Extensibility Accelerator supports comments in XML files only in the following situations:
o The test object class designer for the test object class whose XML section you are modifying is open. (Relevant when adding comments manually. For example, if you want to add comments related to the GWTPushButton test object in the XML editor, you must also open the GWTPushButton test object class designer.)
o The comments appear directly before the opening tag of an element. However, comments before the following element types are not supported:
+ In the test object configuration file: Description, AdditionalInfo, IdentificationProperties, Documentation.
+ In the toolkit configuration file: Controls, Methods, HTMLTags, Settings, Variable (within a Controls\Settings element).

If you import a support set with XML files containing comments that are not supported, the comments are not included in the Extensibility Accelerator project's XML files. If you add such comments manually to an existing XML file in the XML editor, the comments are discarded.

Documentation

* Context-sensitive Help (opened by pressing F1) is not supported for generic Visual Studio IDE when you are not connected to the Internet.
* F1 is not supported for the Project Explorer window and the Control Selection dialog box.

Selecting Controls (Map to Controls) and Editing Files

* The Extensibility Accelerator rule editor (on the Map to Controls tab of the Test Object Class Designer) currently supports only one type of Identification element in the toolkit configuration XML file: Conditions elements of type IdentifyIfPropMatch.

Workaround: If you need to use other types of identification, you must edit the Identification elements manually in the XML file.
* The Extensibility Accelerator rule editor (on the Map to Controls tab of the test object class designer) does not support selection of controls in a dialog box.
* To select controls in a Web page, make sure that in Tools > Internet Options the options specified below are enabled. (Note that in some operating systems these options may be disabled by default.)
o Security (Internet Zone) > Custom Level > ActiveX controls and plug-in -> Binary and script behaviors
o Security (Internet Zone) > Custom Level > Scripting-> Active scripting
* When selecting controls in an application with a 800X600 screen resolution, the pointer behaves unexpectedly.

Workaround: Increase screen resolution.
* While selecting controls, opening a new web page may cause the Web page to behave unexpectedly.

Workaround: Stop the selection process, open the Web page, then resume the selection process.
* In some specific cases, when you click a control to select it, the application responds to the click (for example, by closing a drop-down menu) instead of, or in addition to, Extensibility Accelerator recognizing the selection. This sometimes makes it difficult to select a control to create rules.

Workaround: In some cases, you can click a higher HTML element in the hierarchy and then select this control from within the displayed hierarchy. In other cases you might have to manually create a rule for the control.

Toolkit Support

* When the Identification element in the toolkit configuration XML file includes HTMLTags elements, they are not displayed in the rule editor on the Map to Controls tab of the test object class designer.

Note: This is relevant for some of the controls in the Extensibility Accelerator sample Web 2.0 support samples.
* When the Identification element in the toolkit configuration XML file includes Conditions elements with a type other than IdentifyIfPropMatch, the rules are not displayed in the rule editor on the Map to Controls page, and you cannot use the debugging process to debug the test object class's operations. The rules function as expected on QuickTest.

Note: This is relevant for some of the controls in the Extensibility Accelerator sample Web 2.0 support samples.

Web 2.0 Toolkit Support for QuickTest Professional 10.00 Notes and Limitations

This section contains general information and limitations for this component, as well as toolkit-specific limitations. This section also includes limitations regarding Web Add-in Extensibility.

* ASP.NET Ajax Support Notes and Limitations
* GWT Toolkit Support Notes and Limitations
* Yahoo User Interface Toolkit Support Notes and Limitations
* Web Add-in Extensibility Notes and Limitations

ASP.NET Ajax Support Notes and Limitations

* You cannot perform the following on ASPAjaxSlider and ASPAjaxMultiHandleSlider test objects:
o Use the Highlight in Application command in the object repository.
o Create a bitmap checkpoint.
o Run a CaptureBitmap operation.
* You cannot perform the following for ASPAjax CollapsiblePanel objects when the panel is collapsed in the application:
o Use the Highlight in Application command in the object repository.
o Create a bitmap checkpoint.
o Run a CaptureBitmap operation.

Workaround: Expand the collapsible panel before performing any of the above.
* QuickTest does not support AutoComplete controls whose EnableCaching property is set to False.
* Due to synchronization issues, if you navigate to a new Web page while recording, then QuickTest may not record certain operations on certain ASPAjax objects in the page. Similarly, when running steps that navigate to a new page, QuickTest may fail to perform certain steps on certain ASPAjax objects.

Workaround: If the problem occurs while recording, refresh the Web page and record the step again. If the problem occurs while running, insert a Wait() statement before the problematic step.
* When you perform a Move operation on an ASPAjax drag panel, QuickTest records a WebElement.Drag step and a WebElement.Drop step in addition to the ASPAjaxDragPanel.Move step.

Workaround: Delete the extra Drag and Drop steps before running the step.

GWT Toolkit Support Notes and Limitations

* When you perform a Select operation on a GWT menu bar, QuickTest records a GWTMenuBar.Select step followed by an unnecessary WebElement.Click step. When running, the WebElement.Click step fails.

Workaround: Manually remove the WebElement.Click step.
* When you perform a Move operation on a GWT dialog box, QuickTest records a WebElement.Drag step and a WebElement.Drop step in addition to the GWTDialogBox.Move step. Running these three steps will move the dialog box to an unpredictable location.

Workaround: Delete the extra Drag and Drop steps before running the step.

Yahoo User Interface Toolkit Support Notes and Limitations

* When you perform a Move operation on a Yahoo UI dialog box, QuickTest records a WebElement.Drag step and a WebElement.Drop step in addition to the YUIDialogBox.Move step. Running these three steps will move the dialog box to an unpredictable location.

Workaround: Delete the extra Drag and Drop steps before running the step.

Web Add-in Extensibility Notes and Limitations

* QuickTest does not support recovery scenarios for Web Add-in Extensibility test objects.
* You cannot use Web Add-in Extensibility to create support for Web controls that extend over more than one Web frame. For example, a Web control that exists in two parallel frames that change visibility in order to hide backstage loading.
* When debugging a Web Add-in Extensibility JavaScript file (in the Microsoft Script Debugger or the Microsoft Visual Studio debugger), you cannot step into a function that resides in the Microsoft Internet Explorer engine. (The step into (F11) command steps over the function.)

Workaround: Open the relevant JavaScript file in the debugger and put a breakpoint in the JavaScript function.
* When debugging Web Add-in Extensibility JavaScript code using Microsoft Visual Studio, if you try to add a Watch expression that does not yield an object (for example, the expression if (a = b), Visual Studio may behave unexpectedly.

Workaround: Do one of the following:
o Watch only variables or expressions that yield objects (for example, the expression new Color() returns a Color object).
o Use Microsoft Script Debugger.
* When running a test or component using an external debugger to debug Web Add-in Extensibility JavaScript code, run-time errors may occur in the test or component.

Workaround: If necessary, do one of the following:
o Minimize the number of breakpoints you use to debug the code.
o Analyze the behavior of your JavaScript code by using calls to the _util.LogLine method in the JavaScript functions, instead of using the debugger.
* If Internet Explorer 8.0 is installed on your computer, you can debug Web Add-in Extensibility code only in Visual Studio 2008 SP 1.
* When you enable Just-In-Time debugging in Visual Studio, and you enable debugging in Internet Explorer 8.0, QuickTest does not record operations on custom Web controls supported by Web Add-in Extensibility. In addition, QuickTest does not display identification property values of Web Add-in Extensibility test objects in the Object Spy.

Silverlight Testing Support for QuickTest Professional 10.00 Notes and Limitations

* Silverlight applications hosted in a Mozilla Firefox browser are not supported.
* The Silverlight plug-in must be initialized with the EnableHtmlAccess property value set to True to enable QuickTest to recognize it as Silverlight application. See http://msdn.microsoft.com/en-us/library/cc838264(VS.95).aspx for an explanation of how the value of this property is determined.

If, according to the rules, your application will be initialized with an EnableHtmlAccess value of False, set the ForceHtmlAccess registry key to 1 in HKEY_CURRENT_USER\Software\Mercury Interactive\QuickTest Professional\MicTest\Packages\WpfPackage\Settings to configure QuickTest to force the application to be initialized with an EnableHtmlAccess property value of True.

Note: Having an application initialized with an EnableHtmlAccess value of True can be a security risk. For details, see the Caution note in http://msdn.microsoft.com/en-us/library/cc838264(VS.95).aspx.
* You can enable an additional, more detailed display of the Silverlight test object hierarchy when using the Object Spy and Add Objects features. To do this, set the value of the SlvHighResolutionView registry key to 1 in: HKEY_CURRENT_USER\Software\Mercury Interactive\QuickTest Professional\MicTest\Packages\WpfPackage\Settings. With this registry value set to 1, these features will show the test object hierarchy in a higher resolution, including test objects that are not normally shown in the default mode.
* When learning all objects under a Browser or Page object, Silverlight objects are not added.

Workaround: Learn the objects within a page using the Add Objects option. While learning the objects, select the SlvWindow object in the Object Selection dialog box. (Do not use Navigate and Learn.)
* Operations on check boxes located in table cells are sometimes recorded as check box operations instead of SlvTable.SetCellData operations.

Workaround: Before you perform an operation on a check box in a table cell, perform at least one operation on another cell in that table.
* QuickTest retrieves incorrect values for the all items and selection properties for ListBox and ComboBox controls that are bound to data via a template.
* In some versions of Internet Explorer, the Silverlight application becomes active only after a Click operation is performed. In these cases, QuickTest may fail to run steps unless an initial Click operation is performed.

Workaround: Insert a step containing a Click operation on the Silverlight application before performing other operations on the application.
* Applications containing numerous controls might have performance problems while recording.

Workaround: Change the Active Screen capture level to Partial or Minimum to capture less information. To do this, select the Tools > Options > Active Screen node and modify the setting.
* If a recovery scenario uses the Object State trigger, it may detect redundant test objects when checking the state of a SlvWindow.
* You cannot create a virtual object for an area in a WPF or Silverlight application.
* You cannot use a text checkpoint or output value step to retrieve text from Silverlight link objects.

Workaround: Use a SlvLink.GetROProperty step to retrieve the text value.
* If you insert a text area checkpoint or a text area output value using the Windows API text recognition mechanism (as opposed to the OCR mechanism), all of the text on the Silverlight control is captured (instead of only the text from the selected area).
* For some test objects, if you try to insert a text checkpoint from the Active Screen, the text checkpoint cannot be inserted and an error message is displayed.
* Sometimes, running a Set operation on an SlvRadioButton does not perform the expected operation, even though the radio button state changes successfully. For example, suppose you have an application in which setting the state of a Silverlight radio button to ON causes a list box to open. If you insert a SlvRadioButton.Set step to change the state of the radio button to ON, the state of the radio button changes but the list box might not open.

Workaround: Use a Click operation instead of a Set operation.
daniel
 
Beiträge: 54
Registriert: Do Jun 04, 2009 11:56 am


ZurĂĽck zu QuickTest Pro 10.x

Wer ist online?

Mitglieder in diesem Forum: 0 Mitglieder und 1 Gast

cron