Mercury WinRunner FAQ
Part:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
Q: Is it possible to use winrunner for testing .aspx forms or dotnet forms?
You can't test dot net application using winrunner 7.6 and also from prior
version. Because winrunner do not have addin for dot net.
ASP.NET forms it is a code for server side
part of an application, if it generates on the front end normal
HTML/JavaScript/Java/ActiveX it shouldn't be a problem to test the
application using WR.
Q: Can WinRunner put the test results in a file?
Yes, You can put the results into the file format. (the
file extension is .txt) In Test Results window, you can select one option:
tools menu text report then we can get a text file.
Another option is to write out the results out into a html file.
WinRunner: What is the difference between virtual object and custom object?
Answer1:
The virtual object is an object which is not recognized by Winrunner. The
virtual object class like obj_mouse_click which works for that instance only. To
work at any time, then we should forcibly to instruct the winrunner to recognize
the virtual object with the help of Virtual Object Wizard.
Note: the virtual object must be mapped to a relavant standard classes only
avail in winruuner. Ex: button (which is avail on the toolbar in a app. window)
which is to be mapped to the standard class callled PUSH_BUTTON. when its
completed then u can observe the TSL statment would be
button_press("logicalName") which is permanent one in u r winrunner.
GUI map Configuration:
It helps when winrunner is not able locate the object by winruuner. for
ex : two or more objects will have same logical name and its physical properties
then how winrunner locate the specific object. In which case that should instruct
the winrunner to unquely identify the specific object by setting obligatory,
optional and MS_WID with the help of GUI Map config.
Answer2:
we use the virtual object wizard in winrunner to map the bitmap object while
recording winrunner generates the obj_mouse_click.
Custom object is an object which do not belong to one of the standard class of
winrunner. We use the gui map configuration to map the custom object to standard
object of the winrunner.
Answer3:
virtual object - image or portion of the window are made virtual object to use
functions available for the object just for convenience in scripting.
virtual object captures the cordinates of the object.
custom object - general object which does not belong
to winrunner class, we map this general
object to winrunner standard object, i.e.
custom object.
Q: How to create an Object of an Excel File in WinRunner?
The object part, or actual Excel table is created via the WinRunner Data
Table and it is stored inside the same directory that the WinRunner script is
stored in. Of course you may create the Excle spreadsheet yourself and reference
it from your script manually. This is also mentioned in the User Guide.
The Data Table Wizard mentioned earlier will link this object to the script
and assist in parameterizing the data from the Excel table object.
Q: How to use values returned by VB script in winrunner?
From your VB script create a file system object to write output to a
text file:
Dim fso, MyFile
Set fso = CreateObject("Scripting.FileSystemObject")
Set MyFile = fso.CreateTextFile("c:\testfile.txt", True)
MyFile.WriteLine("This is a test.")
MyFile.Close
Then use file_open and file_getline functions in WinRunner to read
the file.
Q: WinRunner: What tag is required to allow me to identify a html table?
<table id=xxxxx>.
Indeed, it is better to ask developer to put ID every
place where it is possible. It will avoid lots of trouble and help the
resuable of your script (consider localization).
Q: WinRunner: How to work with file type using WinRunner functions?
When recording, WinRunner does not record file-type objects. However,
you can manually insert file-type statements into your test script
using the web_file_browse and web_file_set functions.
Part:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
|