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