Software QA FYI - SQAFYI

Mercury WinRunner FAQ

Part:   1   2  3  4  5  6  7  8  9  10  11  12  13  14  15  16  17  18  19  20  21  22  23  24  25  26  27  28  29  30  31  32  33  34  35  36  37  38  39  40  41  42  43  44  45  46  47  48  49  50  51 

WinRunner automated software functionality test tool from Mercury Interactive for functional and regression testing


Q: For new users, how to use WinRunner to test software applications automately ?

A: The following steps may be of help to you when automating tests

  1. MOST IMPORTANT - write a set of manual tests to test your application - you cannot just jump in with WR and expect to produce a set of meaningful tests. Also as you will see from the steps below this set of manual tests will form your plan to tackle automation of your application.
  2. Once you have a set of manual tests look at them and decide which ones you can automate using your current level of expertise. NOTE that there will be tests that are not suitable for automation, either because you can't automate them, or they are just not worth the effort.
  3. Automate the tests selected in step 2 - initially you will use capture/replay using the steps in the manual test, but you will soon see that to produce meaningful and informative tests you need to add additional code to your test eg. use tl_step() to give test results. As this process continues you will soon see that there are operations that you repeatedly do in multiple tests - these are then candidates for user-defined functions and compiled modules
  4. Once you have completed step 3 go back to step 2 and you will find that the knowledge you have gained in step 3 will now allow you to select some more tests that you can do.

If you continue going through this loop you will gradually become more familiar with WR and TSL, in fact you will probably find that eventually you do very little capture/replay and more straight TSL coding.


Q: How to use WinRunne to check whether the record was updated or the record was delelte or the record was inserted or not?

Using WinRunner check point features: Create->dDB checkpoint->Runtime Record check

Q: How to use WinRunner to test the login screen

A: When you enter wrong id or password, you will get Dialog box.

   1. Record this Dialog box
   2. User win_exists to check whether dialog box exists or not
   3. Playback: Enter wrong id or password, if win_exists is
                true, then your application is working good.
                Enter  good id or password, if win_exists is false,
                then your application is working perfectly.

Q: After clicking on "login" button, they opens other windows of the web application, how to check that page is opened or not

When your expecting "Window1" to come up after clicking on Login...

Capture the window in the GUI Map. No two windows in an web based 
application can have the same html_name property. Hence, this would 
be the property to check.

First try a simple win_exists("window1", 

(Continued on next part...)

Part:   1   2  3  4  5  6  7  8  9  10  11  12  13  14  15  16  17  18  19  20  21  22  23  24  25  26  27  28  29  30  31  32  33  34  35  36  37  38  39  40  41  42  43  44  45  46  47  48  49  50  51 

Mercury WinRunner FAQ