[Spoorthi]

1)[/b] How you used
WinRunner in your project?

[/b]2) Explain WinRunner testing process?

[/b]3) What
in contained in the GUI map?

[/b]4)How
does WinRunner recognize objects on the application?

[/b]5)Have
you created test scripts and what is contained in the test scripts?

[/b]6)How
does WinRunner evaluates test results?

[/b]7)Have
you performed debugging of the scripts?

[/b]8)How
do you run your test scripts?

[/b]9)How
do you analyze results and report the defects?

[/b]10)What
is the use of Test Director software?[/b]

[Spoorthi]

1)[/b] How you used
WinRunner in your project?[/b]


a. For
creating automated scripts for GUI, functional and regression testing of the
AUT.

[Spoorthi]

[/b]


2) Explain WinRunner testing process?[/b]


[/b] WinRunner testing process
involves six main stages :




i.Create GUI Map [/b]File so that WinRunner can
recognize the GUI objects in the application being tested.[/b]


ii.Create Test[/b] Scripts[/b] 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.[/b]


iii.Debug Test [/b]run tests in Debug mode to
make sure they run smoothly.[/b]


iv.Run Tests [/b]run tests in Verify mode to
test your application.[/b]


v.View Results [/b]determines the success or
failure of the tests.[/b]


vi.Report Defects [/b]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.

[Spoorthi]

3) What in contained in the GUI map?[/b]


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[/b]. Global GUI Map file :[/b] A single GUI Map file for the
entire application.


ii. GUI Map File per Test : [/b]WinRunner automatically
creates a GUI Map file for each test created.[/b]

[Spoorthi]

4) How does WinRunner recognize objects on the application?[/b]


.
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

[Spoorthi]

5) Have you created test scripts and what is contained in the test
scripts?[/b]


Yes
I have created test scripts. It contains the statements 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[/b].

[Spoorthi]

6) How does WinRunner evaluates test results?[/b]


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.

[Spoorthi]

7) Have you performed debugging of the scripts?[/b]


Yes, 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.

[Spoorthi]

8) How do you run your test scripts?[/b]


We
run tests in Verify mode to test the 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.

[Spoorthi]

9) How do you analyze results and report the defects?[/b]


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.

[Spoorthi]

10) What is the use of Test Director software?[/b]


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 create reports and graphs to help review the progress of
planning tests, running tests, and tracking defects before a software release.

[raghu]

Thanks spoorthi !


Really good info.[img]smileys/smiley32.gif[/img]

[Spoorthi]

thanks i'm hvng lots of good stuff (all interview que faced by various companies ) i'll gve daily[img]smileys/smiley1.gif[/img]