SOFTWARE TESTING METHODOLOGIES LABORATORY
(Course Code: CS615PE)
[Link]. III Year II Sem. LTPC0021
Prerequisites: A basic knowledge of programming.
Course Objectives:
To provide knowledge of Software Testing Methods.
To develop skills in software test automation and management using latest tools.
Course Outcomes:
After learning the contents of this paper the student must be able to
Design and develop the best test strategies in accordance to the development model.
List of experiments:
1. Recording in context sensitive mode and analog mode
2. GUI checkpoint for single property
3. GUI checkpoint for single object/window
4. GUI checkpoint for multiple objects
5. a) Bitmap checkpoint for object/window
b) Bitmap checkpoint for screen area
6. Database checkpoint for Default check
7. Database checkpoint for custom check
8. Database checkpoint for runtime record check
9. a) Data driven test for dynamic test data submission
b) Data driven test through flat files
c) Data driven test through front grids
d) Data driven test through excel test
10. a) Batch testing without parameter passing
b) Batch testing with parameter passing
11. Data driven batch
12. Silent mode test execution without any interruption
13. Test case for calculator in windows application
SOFTWARE TESTING METHODOLOGIES LAB
Do’s and Don’ts
Do’s
1. Come with completed observation and record.
2. Remove your shoes or wear foot socks before you enter the lab.
3. Always keep quiet. Be considerate to other lab users.
4. Report any problems with the computer to the person in charge.
5. Shut down the computer properly.
6. Wear ID card before entering into the lab.
7. Read and understand how to carry out an activity thoroughly before coming to the lab.
8. Write In time, Out time and system details in the login register
Don’ts
1. Do not touch any part of the computer with wet hands.
2. Do not change system settings.
3. Do not hit the keys on the computer too hard.
4. Don’t damage, remove, or disconnect any labels, parts, cables or equipment.
5. Do not install or download any software or modify or delete any system files on any lab computers
6. Do not disturb your neighbouring students. They may be busy in completing tasks.
7. Do not remove anything from the computer laboratory without permission.
8. Do not use pen drives.
EXPERIMENT1
Recording in Context sensitive mode and Analog mode
Context Sensitive mode records the operations you perform on your application in terms of its GUI
objects. As you record, WinRunner identifies each GUI object you click (such as a window, button, or
list), and the type of operation performed (such as drag, click, or select).
For example, if you click the Open button in an Open dialog box, WinRunner records the following:
button_press ("Open");
When it runs the test, WinRunner looks for the Open dialog box and the Open button represented in
the test script. If, in subsequent runs of the test, the button is in a different location in the Open dialog
box, WinRunner is still able to find it.
Use Context Sensitive mode to test your application by operating on its user interface.
To record a test in context sensitive mode:
1. Choose Test > Record–Context Sensitive or click the Record–Context Sensitive button. The letters Rec
are displayed in dark blue text with a light blue background on the Record button to indicate that a
context sensitive record session is active.
2. Perform the test as planned using the keyboard and mouse. Insert checkpoints and synchronization
points as needed by choosing the appropriate commands from the User toolbar or from the Insert menu
menu: GUI Checkpoint, Bitmap Checkpoint, Database Checkpoint, or Synchronization Point.
3. Tostop recording, click Test > Stop Recording or click Stop
EXPERIMENT2
GUIcheckpoint for single property
You can check a single property of a GUI object. For example, you can check whether a button is enabled
or disabled or whether an item in a list is selected. To create a GUI checkpoint for a property value, use
the Check Property dialog box to add one of the following functions to the test script:
button_check_
info scroll_check_info
edit_check_info
static_check_info
list_check_info win_check_info
obj_check_info
To create a GUI checkpoint for a property value:
1. Choose Insert > GUI Checkpoint > For Single Property. If you are recording in Analog mode, press the
CHECK
GUI FOR SINGLE PROPERTY soft key in order to avoid extraneous mouse movements. The WinRunner
window is minimized, the mouse pointer becomes a pointing hand, and a help window opens on the
screen.
2. Click an object. The Check Property dialog box opens and shows the default function for the selected
object. WinRunner automatically assigns argument values to the function
[Link] can modify the arguments for the property check.
o To modify assigned argument values, choose a value from the Attribute list. The expected value is
updated in the Expected text box.
o To choose a different object, click the pointing hand and then click an object in your application.
WinRunner automatically assigns new argument values to the function.
Note: that if you click an object that is not compatible with the selected function, a message states that
the current function cannot be applied to the selected object.
Click OK to clear the message, and then click Close to close the Check Property dialog box. Repeat steps
1 and 2.
2. Click Paste to paste the statement into your test script.