Active TopicsActive Topics  Display List of Forum MembersMemberlist  CalendarCalendar  Search The ForumSearch  HelpHelp
  RegisterRegister  LoginLogin


 One Stop Testing ForumQuality Assurance @ OneStopTestingQuality Methodologies / Streams @ OneStopTesting

Message Icon Topic: Fundamentals of WinRunner and calling Scripts

Post Reply Post New Topic
Author Message
vidhya
Senior Member
Senior Member


Joined: 24Mar2007
Online Status: Offline
Posts: 114
Quote vidhya Replybullet Topic: Fundamentals of WinRunner and calling Scripts
    Posted: 26Mar2007 at 4:30am
 
  • WinRunner Fundamentals

  • The 5 major areas to know for WinRunner are listed below with SOME of the subtopics called out for each of the major topics:

     1) GUI Map
        - Learning objects
        - Mapping custom objects to standard objects
     2) Record/Playback
        - Record modes: Context Sensitive and Analog
        - Playback modes: (Batch), Verify, Update, Debug
     3) Synchronization
        - Using wait parameter of functions
        - Wait window/object info
        - Wait Bitmap
        - Hard wait()
     4) Verification/Checkpoints
        - window/object GUI checkpoints
        - Bitmap checkpoints
        - Text checkpoints (requires TLS)
     5) TLS (Test Script Language)
        - To enhance scripts (flow control, parameterization, data driven test, user defined functions,
     
  • Calling Scripts and Expected Results
  • 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)
    
    MBA Examination papers



    Post Resume: Click here to Upload your Resume & Apply for Jobs

    IP IP Logged
    Post Reply Post New Topic
    Printable version Printable version

    Forum Jump
    You cannot post new topics in this forum
    You cannot reply to topics in this forum
    You cannot delete your posts in this forum
    You cannot edit your posts in this forum
    You cannot create polls in this forum
    You cannot vote in polls in this forum



    This page was generated in 0.172 seconds.
    Vyom is an ISO 9001:2000 Certified Organization

    © Vyom Technosoft Pvt. Ltd. All Rights Reserved.

    Privacy Policy | Terms and Conditions
    Job Interview Questions | Placement Papers | Free SMS | Freshers Jobs | MBA Forum | Learn SAP | Web Hosting