QuickTest Professional .NET Add-in 8.2 Readme
This file provides the following information about the QuickTest Professional .NET Add-in:
Overview
The QuickTest Professional .NET Add-in recognizes and records on objects based on Windows Forms or Web Forms controls, and enables you to access the properties and methods supported by those controls.
For more information on the .NET Add-in, refer to the QuickTest Professional .NET Add-in Guide.
Customer Support
Technical support for QuickTest Professional and the QuickTest Professional .NET 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:
Customer Support contact numbers all over the world are available on the Customer Support Web Site.
System Requirements
To successfully run the QuickTest Professional .NET Add-in, your system configuration should meet the requirements as specified for QuickTest Professional 8.2 (in the QuickTest Professional 8.2 Readme file), plus the following add-in specific requirements:
Supported Environments
The QuickTest Professional .NET Add-in supports:
- .NET Framework 1.0 or 1.1 or 2.0 Beta
- testing standard .NET Windows Forms controls from the System.Windows.Forms library
- testing third-party .NET Windows Forms controls that are inherited from System.Windows.Forms.Control class
- testing most common .NET Web Forms controls. See details in the section below.
Supported Controls and Corresponding Test Objects
The QuickTest Professional .NET Add-in supports all control types listed below as well as controls derived from these types.
.NET Windows Forms
Following is a list of the control types supported for .NET Windows Forms applications.
In addition to the controls listed above, custom-built QuickTest Professional support for a variety of Infragistics .NET Windows Forms controls is provided out-of-the-box by Infragistics TestAdvantage. For more information, refer to http://www.infragistics.com/products/TestAdvantage_portal.asp.
Tips: To view the full type name of an object in your application, view the SwfTypeName test object property in the Object Spy.
You can also view a list of the base types of a selected object by running a statement using the following syntax:
MsgBox SwfTestObj(descr).GetROProperty("SwfTypeNames")
where SwfTestObj(desc) is the test object you want to check.
Running this statement causes a message box to open displaying the actual class at the top of the list and the base classes below it..NET Web Forms
Following is a list of the control types supported for .NET Web Forms applications.
Useful Information
- You can use the .Object property to access all properties and methods of .NET Windows Forms and Web Forms objects.
- For the most common UI controls, context sensitive support is also available.
- The SwfTable.SetCellData method is recorded only after you move the focus from the edited cell to another cell.
Changing the Microsoft .NET Framework 1.0 Configuration
An application may use components that are built on different versions of the Microsoft .NET Framework. The default behavior of CLR version 1.1 and above is to unify usage of framework assemblies. The runtime version that is associated with an application determines which version of the Microsoft .NET Framework assemblies are used by the application and all of its components. For example, if an application is associated with version 1.1 of the Microsoft .NET Framework and uses the System.Data assembly, then version 1.1 of the System.Data assembly is loaded and shared across all components used by the application. If an application component refers to version 1.0 of the System.Data assembly, the reference is promoted at runtime to reference version 1.1.
The Microsoft .NET Framework 1.0 does not perform unification by default. As the result, an application that uses components built with different Microsoft .NET frameworks may load different versions of the same assembly at runtime. The reason for updating the framework configuration is to provide unification for the Microsoft .NET Framework 1.0. In order to achieve this, the QuickTest Professional .NET Add-in setup applies binding redirection of framework assemblies (for version 1.0 only) at the machine level. Changes are made in the machine.config file under the Microsoft .NET Framework 1.0 installation. The original file is saved as machine.config.bak.
QuickTest can automatically change the Microsoft .NET Framework 1.0 configuration during the .NET Add-in installation, or you can choose to change it manually later on. Note that until the required configuration changes are performed, testing applications based on the .NET Framework 1.0 may cause unexpected results.
To manually update the Microsoft .NET Framework 1.0 configuration after installing the .NET add-in:
- Log-in to your computer with administrator permissions.
- Open a Command Prompt (Start > Programs > Accessories > Command Prompt).
- Type cd /d <QuickTest Professional installation path>\bin and press Enter to change the path to the QuickTest Professional bin folder.
- Type NetUpdateConfig /config and press Enter.
This command performs the required changes in the machine.config file under the Microsoft .NET Framework 1.0 installation. The original file is saved as machine.config.bak.
For additional information, refer to http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpguide/html/cpconnetframeworkassemblyunificationoverview.asp.
Known Problems and Limitations
Installation
- If you uninstall the Microsoft .NET Framework 1.1 from your machine and then you install the .NET Add-in 8.2, the installation of the add-in may fail when trying to install the .NET Framework on your computer.
Workaround: Restart your machine after uninstalling the Microsoft .NET Framework 1.1, even if the uninstall process did not require you to restart.
- If you upgrade to a new version of the Microsoft .NET Framework after installing the .NET Add-in, you must also reinstall the QuickTest Professional .NET Add-in.
.NET Windows Forms
- 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, choose the Tools > Options > Active Screen tab and modify the setting.
- Navigating in the grids controls using keyboard keys (e.g.: to select cells, rows, etc.) may not be recorded correctly.
Workaround: Use the mouse to navigate in the grid control.
- If you call the Back method for a Microsoft DataGrid control on table that does not have a parent row, no operation is performed when the statement runs and no error message is displayed.
- Grid controls in the Card View mode are not supported.
- Changing the format of a DateTimePicker control during a test run or between record and run sessions (e.g.: from "Long Date" to "Time") will cause the test run to fail.
- Combo box objects of style Simple Combobox are not supported.
- If a form window in the tested application has an opacity property value not equal to 100% (i.e. the form is completely or partially transparent), the Active Screen captures the image displayed below the form, and not the transparent window.
- Tests recorded with .NET Framework 1.0 or 1.1 on Microsoft PropertyGrid control (and perhaps other compound controls that use Toolbar as an internal element) may stop working when executed with .NET Framework 2.0. This occurs because in .NET Framework 2.0, the Toolbar control on top of the PropertyGrid control was replaced by ToolStrip and MenuStrip controls.
Workaround: Update the description of the appropriate SwfToolBar test object with the correct SwfTypeName property value.
- If you edit your test or component in the Keyword View or Expert View while recording, some test object methods are unavailable for selection in the Keyword View and are not displayed in the Expert View IntelliSense. In addition, the F1 (Help) key may work incorrectly for some methods while recording.
Workaround: Stop recording before editing your test or component or using the F1 key.
- When working with Infragistics UltraWinGrid, recording and/or run of the SwfTable.Sort operation may work incorrectly if the table is grouped by a particular column.
- If you enter data in a .NET Grid control, the SwfTable.SetCellData operation is recorded only when you leave the cell (select another cell).
- Operation on a grid cell that was selected before you start recording on the grid control may be recorded incorrectly. For example, a child cell element operation may be recorded instead of the parent grid operation (for example, SetCellData).
Workaround: Before performing operation on a cell which is already selected move focus to another cell, then select the required cell while recording and perform the required operation.
.NET Web Forms
- .NET Web Forms support does not work correctly when the SAP or Siebel add-ins are loaded.
Workaround: Make sure that check boxes for the SAP and Siebel add-ins are cleared in the Add-in Manager dialog prior to using the .Net Add-in with Web Forms.
- Tests on WbfTreeView test objects that contain special characters may not run as expected.
Workaround: To run a test on a WbfTreeView item that contains special characters, use the #index format. Refer to the .NET Web Forms Object Model Reference section of the .NET Add-in Guide or online help for details.
- WbfTreeView, WbfToolbar, and WbfTabStrip test objects are not supported for browser control applications.
- Text checkpoints are not supported for WbfTreeView, WbfToolbar, and WbfTabStrip objects.
- Active Screen operations are not supported for WbfTreeView, WbfToolbar, and WbfTabStrip objects.
- Performing a Select or Expand operation on a WbfTreeView object that causes page navigation may fail due to a synchronization problem.
Workaround: Try running the test on the WbfTreeView object step-by-step, meaning instead of using WbfTreeView.Select "item1;item2;item3;"
Use
WbfTreeView.Expand "item1"
WbfTreeView.Expand "item1;item2"
WbfTreeView.Select "item1;item2;item3;"- The Active Screen image for a WbfCalendar object is always saved before navigation. For example, if you click a NextMonth link, the Active Screen displays the current month. Therefore, if you create a checkpoint from the Active Screen and insert it after the Calendar.ShowNextMonth line, the checkpoint will fail.
Workarounds:
Insert checkpoints on calendar objects while recording.
Or
While editing your test, edit the expected value for the checkpoint or insert the checkpoint before the current step.- Working on a .NET Web Forms application that has calendars with more than one unified style is not fully supported.
- The value of the Selected Date and Selected Range test object properties is always none for WbfCalendar objects in selection mode none.
- To retrieve correct values for WbfCalendar Selected Date and Selected Range test object properties, the selected date or range must be currently visible in your Web Forms application.
- All operations on grouping areas in WbfUltraGrid objects (Infragistics UltraWebGrid) are not recorded.
- Operations performed in a rapid sequence on WbfUltraGrid objects may not be recorded.
Workaround: Try to limit the recording to 1-2 operations per second.
- WbfUltraGrid column names are comprised of the inner HTML of the column header, and therefore may include extraneous information.
- Table checkpoints are supported for WbfUltraGrid objects only while recording.
- WbfUltraGrid may fail to sort columns in a descending direction when the column is not already sorted.
Workaround: Split the Sort call into two calls-first sort in ascending order, then Sort in descending order. For example:
Change
WbfUltraGrid("UltraWebGrid1").Sort "Model","Descending"
To
WbfUltraGrid("UltraWebGrid1").Sort "Model","Ascending"
WbfUltraGrid("UltraWebGrid1").Sort "Model","Descending"- WbfUltraGrid addresses the outermost table (the first table) for the following: rows and cols properties; RowCount and ColumnCount methods; and Table checkpoints. Note that the rows property and the RowCount method refer to the non-grouping rows.
.NET Add-in Extensibility
- When using the .NET Add-in Extensibility API with Microsoft .NET Framework 1.1, a "General Run Error" may occur while executing your test. This is caused by an "Execution Engine Exception" error in the application under test (AUT).
Workaround: Install Service Pack 1 (or later) for Microsoft .NET Framework 1.1.
© This manual, 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: U.S. Patent Nos. 5,701,139; 5,657,438; 5,511,185; 5,870,559; 5,958,008; 5,974,572; 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 and 6,754,701. Other patents pending. All rights reserved.
Mercury, Mercury Interactive, the Mercury Interactive logo, LoadRunner, LoadRunner TestCenter, QuickTest Professional, SiteScope, SiteSeer, TestDirector, Topaz and WinRunner are trademarks or registered trademarks of Mercury Interactive Corporation or its subsidiaries, in the United States and/or other countries. The absence of a trademark from this list does not constitute a waiver of Mercury Interactive's intellectual property rights concerning that trademark.
All other company, brand and product names are registered trademarks or trademarks of their respective holders. Mercury Interactive Corporation disclaims any responsibility for specifying which marks are owned by which companies or which organizations.
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-5300QTPNETRM8.2/01
|
Copyright 2004 Mercury Interactive Corporation |
Documentation comments or suggestions? Please send feedback to documentation@mercury.com |