Different Stages in Testing with WinRunner
Create a GUI Map: Here
we teach WinRunner all the GUI elements present in our application and
how to identify them and also assign them some logical names. This can
be done using Rapid Test Script Wizard or more conveniently in GUI Map
Editor. Multiple test procedures might use the same GUI map file. So if
the GUI changes we can just change the map file and all the tests are
ready for testing the new version.
Create Tests: We
can create the test scripts in WinRunner by using either recording or
we can manually key in the TSL script. We can also introduce many
checkpoints like GUI checkpoint, Bitmap checkpoint, Database checkpoint
etc.
Debug Tests: You
run tests in Debug mode to make sure they run smoothly. You can set
breakpoints, monitor variables, and control how tests are run to
identify and isolate defects. Test results are saved in the debug
folder, which you can discard once you finished debugging the test.
Run Tests:
You 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.
View Results:
You determine the success or failure of the tests. 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. In cases
of bitmap mismatches, you can also view a bitmap that displays only the
difference between the expected and actual results.
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
|