Print Page | Close Window

Calling Scripts and Expected Results

Printed From: One Stop Testing
Category: Testing Tools @ OneStopTesting
Forum Name: WinRunner @ OneStopTesting
Forum Discription: WinRunner is an automated functional GUI testing tool that allows a user to record and play back UI interactions as test scripts using a proprietary Test Script Language (TSL).
URL: http://forum.onestoptesting.com/forum_posts.asp?TID=316
Printed Date: 24Dec2024 at 9:01am


Topic: Calling Scripts and Expected Results
Posted By: vidhya
Subject: Calling Scripts and Expected Results
Date Posted: 26Mar2007 at 4:34am
 
  • Calling Scripts and Expected Results and Run Modes
  • When running in non-batch mode, WinRunner will always look in the calling scripts \exp directory for the checks. When running in batch mode, WinRunner will look in the called script's \exp directory.

    There is a limitation, though. WinRunner will only look in the called script's \exp directory one call level deep. For example, in bacth mode:

       script1:
       gui_check(...);  #will look in script1\exp
       call "script2" ();
    
       script2:
       gui_check(...); #will look in script2\exp
       call "script3" ();
    
       script3:
       gui_check(...); #will look in script2\exp (and cause an error)
    
       In non bacth mode:
    
       script1:
       gui_check(...);  #will look in script1\exp
       call "script2" ();
    
       script2:
       gui_check(...); #will look in script1\exp (and cause an error)
       call "script3" ();
    
       script3:
       gui_check(...); #will look in script1\exp (and cause an error)
    

  • Run Modes
  • Batch mode will write results to the individual called test.
  • Interactive (non-batch) mode writes to the main test.


  • -------------
    MBA Examination papers



    Print Page | Close Window