|
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: Online Vs Batch Execution - Online Test Scripts
How do we use Online Scripts?
Using Dialog functions we can use the Interactive Testing
accomplished.
In Mercury Interactive the following code is
SSN = create_input_dialog ("Please Enter the SSN Number");
In Compuware's QARun the following code is
Dialog "Array_A" Array_A []
USER = Array_A["Userid"]
Pass = Array_A["Password"]
Q: Online Vs Batch Execution - User Input
. Where should the input_dialog_box function exist - in the driver file or in individual script?
. The input dialog function should be used within the driver files (Master driver and within each of the Type driver files)
Q: Online Vs Batch Execution - Test Results
. Is it necessary to pass results back to the driver script even if scripts are not
dependent? How should the results be passed back?
No need to pass the result back to the driver script if your scripts are independent
Q: Online Vs Batch Execution - TRe-Runnable Tests
Should setup scripts be made re-runnable? If yes then why? Also what is the best way to make them re-runnable (should it be attaching a random-number string or should it be, 'if' statements to check if data already exists)
It is best to create scripts that are re-runnable but we understand that it may not be possible for all cases for Set-Up type.
Q: Online Vs Batch Execution - TRe-Runnable Tests
Calling a driver file from within a driver file? Is this advisable?
No.
Q: Online Vs Batch Execution - Functions & Compiled Modules-Load Library
Loading libraries and memory issues, i.e. if a library contains 100 functions and only one function is used then unnecessarily we are loading all the function into memory. Should we make multiple smaller libraries and load and unload libraries frequently or just have one big library and keep it loaded all throughout the execution of master driver
Known Issue
We will run into memory issues when loading 100 functions into memory
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
| 