Subscribe by Email

Wednesday, August 8, 2012

How will you synchronize tests using WinRunner? When should you synchronize? What are Synchronize settings?

Whenever a data driven test is created the fixed values of the test script language or TSL statements are parameterized. Contrary to all this there are no fixed values in the synchronization points.
Instead they consist of the following:
  1. A bit map check point statement/ bit map synchronization point statement: It contains a reference to the stored bitmap.
  2. A GUI check point statement: It contains a reference to a stored check list and expected results.
You should always remember this point that it is always better to create a single property check rather than creating a GUI check point while checking the properties of the GUI objects during a data driven test. This is recommended since a single property check does not consist of a check list and hence it is quite easy to parameterize. 
In this article we answer the following three important questions regarding synchronization in winrunner:
  1. How will you synchronize the tests using the winrunner?
  2. When should you synchronize?
  3. Synchronization settings

How to synchronize?

- First step in the synchronization of the tests is the creation of an initial test by either programming or by recording. 
- Next step, will be to use the data driver wizard. 
- Go to the table menu and select the option data driver wizard. 
- The purpose of the data driver wizard is to convert your test scripts in to a data driven test and to parameterize the data values. 
- The third step will involve the creation of column in the data table for all the synchronization points and check points whose values are to be parameterized. - Then you should enter dummy values in every row and column but all the dummy values should be unique from each other. 
- Fourth step is to open up the assign parameter dialogue box from the table menu. 
- Then you should change the expected values of the synchronization points and check points to be used from the data table. 
- Now fifth and the final step involves running your tests in update mode by selecting update mode from the run mode box. 
- Give the run command to run your tests and while the test is running the winrunner will be reading the expected values from the data table. 
- But since you have changed the expected values, Winrunner will not be able to find these and thus will recapture the values from the application software and save them as the expected values. 
- Later, you can run the same tests in verify mode for verification of the behaviour of your software system or application.

When should we synchronize the tests?

- Whenever you feel that there your software system or application is showing some inconsistencies in its performance or behaviour, you can synchronize the tests as it will compensate for these inconsistencies in your application during a test run. 
- When you introduce a synchronization point in the test scripts you are instructing your winrunner to suspend the current test run and continue the test after getting a cue.

Synchronization Settings

- Winrunner offers many testing options like delay_msec, min_diff and timeout_msec. 
- These testing options can be modified using appropriate synchronization settings.
- These testing options can be set globally by using the below mentioned corresponding options:
  1. Time out for check points and CS statements
  2. Delay for window synchronization and
  3. Threshold for difference between bitmaps
- You can get these options by going to the general options dialogue box, the selecting run, then settings, then run and then selecting synchronization categories. 

No comments:

Facebook activity