When do you use Verify/Debug/Update Modes? (in Winrunner)

After you have developed the test scripts and finalized your test case, your next step is to run that particular test in order to check the behaviour of your software system or application. Whenever a test is executed using the winrunner, line by line the whole test is interpreted by the winrunner.  

As the TSL statements are interpreted line by line they are marked by an execution arrow which is visible in the left margin of the test script. As the test continues to be executed your software system or application is executed as if it is being controlled by a person. 

The winrunner provides 3 modes for the running your tests namely:

1. Verify run mode
2. Debug run mode
3. Update run mode

In this article we talk about the above mentioned three different types of winrunner run modes. 

- The first mode i.e., the verify run mode checks the application. 

- The second one i.e., the debug run mode debugs the test scripts.

- The third one i.e., the update run mode updates the expected results. 

- Only two modes i.e., the debug run mode and the verify run mode are available when you are using the winrunner run-time.

- Any one of these modes can be chosen from the list on the test tool bar. 

- The verify run mode represents the default run mode in winrunner. 

- You can either run the entire test or just a portion of it using the test and debug menu commands. 

- But always make sure all the necessary GUI map files have been loaded before you start with a context sensitive test. 

- You also have the choice of running individual tests or a group of tests using a batch test. 

- Batch test seems to be quite useful when you have very long tests to be executed and you need an overnight run. 

Now we will discuss about all the three run modes in detail one by one:

Verify run mode: 

- In this mode the current response of your software system or application is compared to the expected response by the winrunner.

- The results of this run mode are called verification results and enlist all the discrepancies that might have been observed in the current response and the expected response. 

- When the execution of the test stops, the verification results window is by default opened for the user to see. 

- As many sets as required of the verification results can be obtained. 

- However, you should always be ready with the expected results for the check points that you created earlier. 

- If there is any requirement for updating the expected results you just need to run the test in update mode.

Debug run mode: 

- This mode also helps in rooting out many of the bugs that might be residing in a test script. 

- The execution of a test in verify mode as well as debug is almost same, the only difference being in the folder in which the results are saved. 

- In this case the test results are saved in the debug folder. 

- Also, here only one set of debug results is stored and so the folder does not opens automatically for the user to view. 

- In this mode, the thing to be taken care of is that the time out variables must be changed to zero while the debugging 0of the test scripts take place.

Update run mode: 

- This mode helps in the updating of the expected results as well in the creation of a new expected results folder.

- Results for a GUI check point can also be updated and an additional set of expected results can also be created.