Win Runner Related some Questions .

Win Runner Related some Questions .

  • Q: What is contained in the GUI map?
  • Ans: WinRunner stores information it learns about a window or object in a GUI Map. When WinRunner runs a test, it uses the GUI map to locate objects. It reads an object’s description in the GUI map and then looks for an object with the same properties in the application being tested. Each of these objects in the GUI Map file will be having a logical name and a physical description. There are 2 types of GUI Map files. Global GUI Map file: a single GUI Map file for the entire application. GUI Map File per Test: WinRunner automatically creates a GUI Map file for each test created.
  • Q: How Win Runner identifies the GUI objects?
  • Ans: Win Runner identifies the objects based on their Logical name & Physical properties.
  • Q: What browsers are supported by Win Runner 7.x?
  • Ans:Win Runner 7.x supports Internet Explorer 4.x-5.5, Netscape Navigator 4.0-6.1 (excluding versions 6.0 and 6.01) and AOL 5 and 6.
  • Q: What is GUI Spy?
  • Ans: GUI Spy is an integrated tool for spying on standard, ActiveX and Java controls. It displays the properties of standard controls and the properties and methods of ActiveX and Java controls. You can copy and paste functions for activating Java methods from the GUI Spy into your test script.
  • Q:What is the use of GUI Map File per Test mode? Ans: This mode automatically manages GUI map files., so we do not have to load or save GUI map files in your test. GUI map files per test can be combined into the Global GUI map file if needed.
  • Q:What add-ins are available for Win Runner 7.x?
  • Ans:Add-ins are available for Java, ActiveX, WebTest, Siebel, Terminal Emulator, Forte, Oracle and PowerBuilder.
  • Q:Can WR automatically back up test scripts?
  • Ans:Yes, Win Runner 7.x can automatically create a backup copy of your test script at intervals you specify.
  • Q: What are the different run modes?
  • Ans: Three modes for running test:
  • Verify (default): To check your application against expected results. Win Runner compares the current response of the application to its expected response. Any discrepancies between the current and expected response are captured and saved as verification results.
  • Debug: The debug mode helps you identify bugs in test scripts. Running a test in the debug mode is the same as running a test in the Verify mode, expect that debug results are always saved in the debug directory.
  • Update: The update mode to update the expected results a test.
  • Q: What is GUI checkpoint?
  • Ans: GUI Checkpoints allows to verify the current state or attributes of GUI objects. When we insert GUI checkpoint in script, Win Runner captures the current value of the object properties and saves them in the expected result directory (exp) of the test. When we run the test Win Runner compares the current state of the object in the application to the expected state and detects and reports any mismatches.
  • Q: When we need to update the GUI map?
  • Ans: We need to update the GUI map when objects in the application have changed. This usually happens when a new major version of the application is released.
  • Q:What is the need for Data Driven Tests?
  • Ans:‘Parameterizing’ the test allows to run the same test with different data each time. In addition the test is expandable and easier to maintain.
  • Q:What is the purpose of the set_window function?
  • Ans:The set_window function sets the focus of the window in the application as well as sets the scope of the window in the GUI map.
  • Q: What is the difference between call() and load() function?
  • Ans: Call functions invokes a test from within a test script but load is used for loading a compiled module into memory.
  • Q:What is compiled module? Why do you create a complied module?
  • Ans: 1 Compiled module is library of frequently used functions. We can save user defined functions in compiled module and then call them in the test scripts.
  • 2 Compiled module improves the organization and performance of the tests.
  • 3 Compiled modules are debugged before using; they will require less error checking.
  • 4 Calling a function whose is already compiled is significantly faster than interpreting a function in test script.
  • 5 Complied module does not support analog recoding and checkpoints.
  • Q: How do you create user-defined functions?
  • Ans:User Defined functions enhance the efficiency and reliability of test scripts. Easy way to create a function is
  • 1. Create the process by recording the TSL functions
  • 2. Enclose it into the function header
  • 3. Replace values with parameters
  • 4. Declare local variable
  • 5. Handle errors
  • Q: What is database checkpoint?
  • Ans:Database checkpoint is used to check the contents of database in different versions of the application.
  • Q:What do Runtime Database Record Checkpoints do?
  • Ans: Runtime Database Record Checkpoints enable you to check that your application inserts, deletes, updates or retrieves data in a database correctly. By mapping application controls to database fields, you can check that the values in your application are correctly read from or written to the matching database fields when you run your test.
  • Q:What is Startup script? What is role of Startup script?
  • Ans: A startup script is a test scripts that is automatically run each time we start WinRunner. We can create startup tests that load GUI map, compiled modules, configuring recording options and staring AUT.
  • Q: What is Function Generator and how it is used?
  • Ans: In Function Generator functions are grouped in categories according to the object class (list, button) or the type of function (input/output, system, file, etc).
  • In Function Generator we choose a function, then expand the dialog box (by pressing the Args>> button) to fill in the argument values and paste it to script.
  • Q:If you want to run the same script 100 times, what is the syntax? Ans: for(i=1;i<=100;i++) { TSL statements }
  • Q:What is a virtual object?How do you handle Virtual Objects in WinRunner?
  • Ans:Our applications may contain bitmaps that look and behave like GUI objects. WinRunner record operations on these objects using win_mouse_click statements. We can define these objects as virtual objects and instruct WinRunner to treat them as GUI objects when we record or run the tests. Using Virtual Object wizard we can assign a bitmap to a standard object class, define the coordinates of that object, and assign it a logical name.
  • Q:What are the different Checkpoints that you can insert in a WinRunner Script?
  • Ans: Four types of checkpoints can be added to any WinRunner script.
  • 1. GUI Checkpoint
  • 2. Bitmap Checkpoint
  • 3. Database Checkpoint
  • 4. Text Checkpoint (only for Web scripts)
  • Q:How do you check for the database table contents?
  • Ans:Using ‘Database checkpoint’
  • Q:How do you handle Web Exceptions?
  • Ans:We can instruct WinRunner to handle the appearance of specific dialog box in the web site during the test run. WinRunner contains a list of exceptions that it supports in the Web Exception Editor. We can modify the list and configure additional exceptions that we would like WinRunner to support.
  • Q:What is the difference between Main Test and a Compile Module file?
  • Ans:Main test contains the TSL script to test the AUT. Compiled module is library of frequently used functions. We can save user defined functions in compiled module and then call them in the main test scripts.
  • Q:How do you start client/server applications from the script?
  • Ans:Using following TSL function: invoke_application ( file, command_option, working_dir, show );
  • Q:When do you run a test in batch mode?
  • Ans:Batch testing is execution of a suite of test scripts towards an overall testing goal. We need to run a batch test when we want to test the overall AUT.
  • Win Runner Navigation
  • http://testingsolution.blogspot.com/2006/12/win-runner-navigation.html
  • Software Testing Books

1 comment:

Unknown said...

Thanks a lot Manish,its really a great creation.