|
1)
How you used WinRunner in your project?
a)
Yes, I have been using WinRunner
for creating automated scripts for GUI, functional and regression testing of the
AUT.
2)
Explain WinRunner testing process?
a)
WinRunner testing process involves
six main stages
i.
Create GUI Map File so that
WinRunner can recognize the GUI objects in the application being tested
ii.
Create test scripts by
recording, programming, or a combination of both. While recording tests, insert
checkpoints where you want to check the response of the application being
tested.
iii.
Debug Test: run tests in Debug
mode to make sure they run smoothly
iv.
Run Tests: run tests in Verify
mode to test your application.
v.
View Results: determines the
success or failure of the tests.
vi.
Report Defects: If a test run
fails due to a defect in the application being tested, you can report
information about the defect directly from the Test Results window.
3)
What is contained in the GUI map?
a)
WinRunner stores information it
learns about a window or object in a GUI Map. When WinRunner runs a test, it
uses the GUI map to locate objects. It reads an object’s description in the GUI
map and then looks for an object with the same properties in the application
being tested. Each of these objects in the GUI Map file will be having a logical
name and a physical description.
b)
There are 2 types of GUI Map files.
i.
Global GUI Map file: a single
GUI Map file for the entire application
ii.
GUI Map File per Test:
WinRunner automatically creates a GUI Map file for each test created.
4)
How does WinRunner recognize objects on the application?
a)
WinRunner uses the GUI Map file to
recognize objects on the application. When WinRunner runs a test, it uses the
GUI map to locate objects. It reads an object’s description in the GUI map and
then looks for an object with the same properties in the application being
tested.
5)
Have you created test scripts and what is contained in the test scripts?
a)
Yes I have created test scripts. It
contains the statement in Mercury Interactive’s Test Script Language (TSL).
These statements appear as a test script in a test window. You can then enhance
your recorded test script, either by typing in additional TSL functions and
programming elements or by using WinRunner’s visual programming tool, the
Function Generator.
6)
How does WinRunner evaluates test results?
a)
Following each test run, WinRunner
displays the results in a report. The report details all the major events that
occurred during the run, such as checkpoints, error messages, system messages,
or user messages. If mismatches are detected at checkpoints during the test run,
you can view the expected results and the actual results from the Test Results
window.
7)
Have you performed debugging of the scripts?
a)
Yes, I have performed debugging of
scripts. We can debug the script by executing the script in the debug mode. We
can also debug script using the Step, Step Into, Step out functionalities
provided by the WinRunner.
8)
How do you run your test scripts?
a)
We run tests in Verify mode to test
your application. Each time WinRunner encounters a checkpoint in the test
script, it compares the current data of the application being tested to the
expected data captured earlier. If any mismatches are found, WinRunner captures
them as actual results.
9)
How do you analyze results and report the defects?
a)
Following each test run, WinRunner
displays the results in a report. The report details all the major events that
occurred during the run, such as checkpoints, error messages, system messages,
or user messages. If mismatches are detected at checkpoints during the test run,
you can view the expected results and the actual results from the Test Results
window. If a test run fails due to a defect in the application being tested, you
can report information about the defect directly from the Test Results window.
This information is sent via e-mail to the quality assurance manager, who tracks
the defect until it is fixed.
10)
What is the use of Test Director software?
TestDirector is Mercury
Interactive’s software test management tool. It helps quality assurance
personnel plan and organize the testing process. With TestDirector you can
create a database of manual and automated tests, build test cycles, run tests,
and report and track defects. You can also |
