I am new to winrunner I would like to know the exact process of testing using winrunner.
I did go through the tutorials and the User GUide. They mention the first step is to record the GUI and create a GUI MAP. Is this the standard process or how can it be done otherwise.
And while performing the web test the RapidTest Wizard is disabled. In this case how to record the GUI.
Please anyone give me the details.
WinRunner documentation and tutorial provide you with the basics of how to use WinRunner and some basics about testing in the examples. The exact process of testing is a different matter altogether and is entirely independent of any automation tool. In other words if you don't know the test process, WinRunner will be of little use to you.
Entire books have been written about the test process. It may be wise for you to purchase one. Visit the "Links" tab to the upper right of this page. Also search the Functional Test forum for hints and tips about testing.
RapidTest Wizard is disabled because you have the WebTest Add-in loaded. If you are doing web test I can help you, I haven't done web test. [img]images/icons/frown.gif[/img]
Other way to learn the GUI is throught Tools->GUI Map Editor...
In that dialog is a "Learn" button. Also, when you're recording a script, WinRunner automatically learn any component that you use.
If you're new in automation testing (or QA in general) you should learn about it before using WinRunner... WinRunner is just a tool to apply what you know.
As you are new in WinRunner then you should use the approach given on tutorial, learn the GUI and the record some scripts. After that you can try some programming.
Use "GUI Map File per Test" on Settings->General Options... -> Environment. When you learn WinRunner try "Global GUI Map File" to keep all your GUI Map in a single file and use it on different scripts applied to the same application.
I hope you learn fast and start developing smart scripts soon.
[i]Debugging is twice as hard as writing the code in the first place.
Therefore, if you write the code as cleverly as possible, you are,
by definition, not smart enough to debug it.</i]- Brian W. Kernighan