|
Standard WinRunner Functions
| Topics this page:
|
Related Topics: |
File Functions
|
Microsoft COM Functions
|
Window Functions
|
Text Data
|
Graphic Controls
|
Special Controls
Note: all standard classes except toolbar have a _wait_info and _get_info function.
|
Number & String Functions
|
Array Functions
|
FIFO Queues and LIFO Stacks
|
CSOLIBS
CSOLIB1
|
Avoid the hassle of integrating Mercury's CSO libraries. Use the WRSAFS framework First log onto Mercury's FTP site ftp.merc-int.com.The username and password that used to display here were removed to avoid more pain dealing with threats from Mercury Interactive lawyers. Drill down to folders /data/ ftp/ pub/ Winrunner/ cso/ CSOLIB (1) 123,606 bytes 4/7/2000 The first CSOLIB provides several executable files (cso16lib.dll, cso32lib.dll, del_dir.exe, list_dir.exe, lv_fin.dll, message.exe, messag1.exe, msg.exe, msg1.exe) which should be copied into the /arch folder under c:\Program Files\Mercury Interactive\WinRunner. That's where WinRunner stores other executable files. The heart of CSOLIB.zip is the script which defines the new functions listed on on the right. This script adds items in the Function Generator under category “cso functions”. Press F7 or go to Create > Insert Function > From Function Generator... There are two versions of this script (compiled modules): cso16lib on 16-bit original “Windows” machines, and cso32lib on 32-bit “Windows NT” or other systems. You are instructed by the install.txt file to copy them both into the WinRunner lib folder, where other TSL scripts from WinRunner reside. The cso_init initialization script detects the OS being used and loads the compiled module. You are asked to call cso_init by adding a line to the tslinit script within the WinRunner dat folder. However, I think it's better to put it in your own initialization script. CSOLIB2 121,272 bytes 6/6/2000 (NOT 120,873 bytes May 22, 2000) Executable files csolib2.dll and clipboard.dll (which should be copied to WinRunner's /arch folder) are referenced by scripts cso2_init and cso2load (which should be put in WinRunner's /lib folder). cso2_init initiates function initcso2() from compiled module cso2load. This adds into the function generator category “cso functions 2” functions. CSOLIB3 7,856 bytes There are no executable files in this library. cso3_init initiates function initcso3() from compiled module cso3load. This adds into the function generator category “cso functions 3” functions. CSOLIBx 79,829 bytes Jun 23, 2000 Files mfcarp.dll and csolibx.dll (which should be copied to WinRunner's /arch folder) are referenced by scripts csox_init and csoxload (which should be put in WinRunner's /lib folder). csox_init initiates function csox_load() from compiled module csoxload. This adds into the function generator category “CSO Lib X” functions.
|
Custom Capture and Comparison Functions
The linkage between the query and the custom DLL file is registered using WinRunner's add_record_attr function. One of the parameters to is the name of the WinRunner standard property verification function which assesses whether the custom property being defined is really a valid string, number, or boolean expression (string_verify, num_verify, bool_verify). WinRunner's delete_record_attr function removes the property. WinRunner's add_cust_record_class function associates a custom record function that enables WinRunner to record descriptive statements into your test script, with a custom GUI object class a logical name function, that enables WinRunner to assign descriptive logical names , with a custom GUI object class Custom checks must be registered with the Windows operating system using a statement such as the following: gui_ver_add_check ( property check name, capture function, comparison function, [optional display function] ) To make a custom check appear in the GUI Checkpoint dialog box: gui_ver_add_check_to_class ( class, property check name, )
| I last picked up the WinRunner Customization Guide from an FTP of 1.3MB 132 page wrun_cus.pdf file dated 12/4/98. |
Custom Function Libraries
open_flight open_order Generic custom functions, such as date, string, and array manipulation functions, can be used by all applications, so they should be called from the WinRunner folder under Program Files.
| . |
Generic Custom Function LibrariesFerry Firmansjah's String, Array, and Queue Stack Modules You Wish Mercury Included for WinRunner. Also, generic Date and array handling functions. | As part of WinRunner installation, Mercury provides a WDiff v1.49 utility that displays differences between text files in directories (folders) or zip archives.
|
|
Function Naming Conventions
Custom functions are defined by users of WinRunner. An organization may choose to segregate the functions they create into application-specific functions which pertain only to certain uses, and generic functions common to all applications. Name functions with their ownership, object, and action To make functions easier to remember, begin names with ownership information,
|
| Your first name: Your family name: Your location (city, country): Your Email address: |
Top of Page
Thank you! |