|
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: Test Recorder about Script Environment: Automation Inits ()
Common Functions that get into Initialization Script are
1. Usage of built-in commands to keep the test path dynamically loaded. Options to rule out the possibility of Test Path Definitions
2. Close all the object files and data files in the Initialization Script
3. Connection to the database should be done in the Inits Script
4. Always Unload and Load the Object library, and it should be done only in Inits Script.
5. Define all the "public" Variables in the Inits Script
6. Establish the db connections in the Inits Test Script
Q: Test Recorder about Script Environment: Test Scripts Elements:
Prior to the development of Test Scripts the fashion of arranging the Test Scripts needs a proper planning. Lets look at few inputs on arranging the Test ware.
|
Test Ware
|
Test Repository
|
|
Test Suite
|
Should contain Sub Folders, Exception Handlers, Global Object files, Set Data file, Driver Scripts, Initialization & Termination scripts
|
|
Driver Script
|
Object Checks, Bit Map Checks, Text Check, Web Check, User defined Functions, Global test Report Folder
|
|
Driven Script
|
GUI/Bit/Text Check, External Libraries, I/O Handlers
|
Q: Test Recorder about Control Points
In any given automation tool the overall control of AUT is by Object identification technique. By this unique feature the tool recognizes the Application as an medium to interrogate with the Tester supplied inputs and tests the mobility of the Business Logistics. Invoking this object identification technique the test tool does have certain control features that checks the application at various given point of time. Innumerous criteria, myriads of object handlers, plenty of predefined conditions are the features that determine the so-called object based features of the Functional Check points. Each tester has a different perspective of defining the Control points.
Q: Test Recorder about Control Points - If. … Else:
1. Before we start the "if else" construct the nature of the control point is commented along side.
For e.g.,
# Home Page Validation
If (<return-code> == "0")
print ("Successfully Launched");
else
print ("Operation Unsuccessful");
2. For all Data Table operation the return-code of the Open function should be handled in the "if else" construct.
Q: Test Recorder about Data Access
In automation Test Data becomes very critical to control, supplement and transfer in the application. In automation tools the Test Data is handled in data sheets of Excel format or a .csv file that is basically a character separated file using the Data driven technology. In most regression batch testing the Test Data is handled in data tables with proper allocation of test data in the sheets.
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
| 