1. Advantages of Automation Tools in Testing?
· Minimum requirement of human resource.
· Accuracy.
· Reliable
· Less time consuming-Faster than manual testing.
· Reusable
· Programmable
2. What is the latest version of WinRunner?
Latest version of WinRunner is 8.0
3. What is the language used in WinRunner?
TSL-Test Scipt Language (Similar to C)
4. Explain the Testing Process in WinRunner?
a) Create a Rapid Test Script Wizard. The Wizard automatically generates a series of tests, which you can immediately run on your Application.
b) Additional tests can either be created or recorded
c) Debug the test
d) Run the test on new version to verufy the application behavior.
5. What are the components of WinRunner?
a)Test Window : This is a window where the TSL script is generated/programmed.
b)GUI Spy tool in WinRunner lets you spy on the GUI objets by recording the Properties.
6. How does WinRunner identify GUI objects?
The WR examines the GUI objects, and saves the object descriptions in a GUI Map File Later on when you run tests, Win Runner uses this file to identify and locate objects.Win Runner learns desctiption of a GUI object, it looks at the object’s physical.Eeach GUI objects has many properties such as “class”, “label”,”width”, “height”,”handle”,and “enable” to name a few However, Win Runner only learns the properties that uniquely distinguish an object from all other objects in the application
For example, when Win Runner looks at an Ok button, it might see that the butto9n is located in an Open window, belongs to the pushbutton object class, and has the test label “OK’.
7. What is GUI Spy?
GUI Spy tool in WinRunner lets you spy on the GUI object by recording the propreties.
path: Tools/GUI Spy and start recording.
8. What are all captured in GUI Spy?
a) class to which the object relates.
b)label.
c)Description of the object.
9. What is Rapid Test Script Wizard?
it performs two tasks.
a)It systematically opens the windows in your application and learns a description of Every GUI object.The wizard stores this information in a GUI map file.
b) It automatically generates tests base on the information it learned as it navigated through the application.
10. What is a User Interface test?
The User Interface test compiles an AUT in accordance with Microsoft standards.
A user interface test checks the following:
· GUI objects do not overlap
· GUI objects are aligned in windows
· Text labels on GUI objects begin with capital letters
· Text labels on GUI objects are clearly visible
· OK and Cancel buttons appear in every window
· A system menu is available in every window.
11. What are the different modes in learning an application under Rapid test script wizard?
a) Express
b) Comprehensive.
12. What are the different reocd modes?
a) Analog
b) Context Sensitive
13. What is Context Sensitive Mode?
Context Sensitive mode records the operations you perform in terms of the GUI Objects in your application. Win Runner identifies each objects you click (such as a window, menu, list, or button), and the tupe of operation you perform (such as Press, enable, move, or select)
14. What is Analog mode?
In Analog mode, WinRunner records the exact coordinates traveled buy the mouse, as well as mouse clicks and keyboard input.
15. When Context Sensitive mode is to be chosen?
a) The application contains GUI objects
b) Does not require exact mouse movements.
16. When Analog mode is to be chosen?
a) The application contains bitmap areas.
b) Does require exact mouse movements.
17. What are the different run modes?
i) verify: Use verify Mode When rnning a test to check the behaviour of your application,and when your want to save the test results.
ii) Debug: Use Debug Mode when you want to check that the test script runs smoothly without errors in syntax.
iii) Update: Use Update mode when your want to create new expected results for a GUI checkpoint or bitmap checkpoint.
18. What is Synchronization?
When you run tests. your application may not alwayus respond to input with the Same speed .For example, it might take a few seconds:
· to retrive information from a database
· for a window to pop up
· for a progress bar to reach 100%
· for a status message to appear
Win Runner waits a set amount of time for an application to respond to input. The default amount of time that win Runner waits is up to 10 seconds. If the application responds slowly during a test run, WinRunner’s default wait time may not be enough, and WinRunner may try to continue the test before the application is ready. The test run, will then unexpectedly fail. If your discover a synchronization problem between the test and your application, you can either:
. Increase the default time that the WinRunner waits. To do so, your change the value of the timeout test option tin the Options dialog box (Settings Options): This method affects all your tests and slows down many other Context Sensitive operations.
. Insert a synchronization point into the test script at the exact point that the problem occurs. A synchronization point tells Win Runner to pause the test run in order to wait for a specified response in the application.
19. How to change synchronization options?
In Settings / Options click the run tab- Increase the timeout seconds. Or Create wait bitmap option.
20. What is GUI Checkpoint?
A GUI checkpoint examines the behavior of object’s properties
21. What is a checklist?
A checklist contains information about GUI and the selected properties to check.
22. What are the prerequisites for running a test?
a) Make sure that the application under test is Open on the desktop.
b) Check the verity mode
c) Choose run from top
d) Run the test
e) Review the results.
23. When a bitmap check is failed?
When the screen settings are changed.
24. How to add functions in Win Runner?
You can quickly add these functions to a test script using Win Runner’s visual Programming tool, the Functional Generator.
The Function Generator enables you to add TSL Functions in two ways:
a) You can point to a GUI object and let Win Runner “suggest” an appropriate Function. You can then insert this function into the test script.
b) You can select a function from a list. Functions are presented both by category and alphabetically
25. What is tl_step?In most cases when you run a test, Win Runner reports an overall test result of Pass or fail. By adding tl_step statements to your test script. You can determine whether a particular operation within the test passed of failed, and send a Message to the report.
26.  How  you used WinRunner in your project?
Yes, I have been using  WinRunner for creating automated scripts for GUI, functional and regression  testing of the AUT.
Explain  WinRunner testing process? 
WinRunner testing process  involves six main stages
* Create GUI Map File so that WinRunner can  recognize the GUI objects in the application being tested
* Create test  scripts by recording, programming, or a combination of both. While recording  tests, insert checkpoints where you want to check the response of the  application being tested.
* Debug Test: run tests in Debug mode to make sure they run smoothly
* Run  Tests: run tests in Verify mode to test your application.
* View Results:  determines the success or failure of the tests.
* Report Defects: If a test  run fails due to a defect in the application being tested, you can report  information about the defect directly from the Test Results window.
What is  contained in the GUI map? 
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.
How does  WinRunner recognize objects on the application? 
WinRunner  uses the GUI Map file to recognize objects on the application. 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.
Have you created test scripts and what  is contained in the test scripts?
Yes I have created test scripts.  It contains the statement in Mercury Interactive’s Test Script Language (TSL).  These statements appear as a test script in a test window. You can then enhance  your recorded test script, either by typing in additional TSL functions and  programming elements or by using WinRunner’s visual programming tool, the  Function Generator. 
How does WinRunner evaluate test results?
Following each test run, WinRunner displays the results in a report. The report details all the major events that occurred during the run, such as checkpoints, error messages, system messages, or user messages. If mismatches are detected at checkpoints during the test run, you can view the expected results and the actual results from the Test Results window.
Have you  performed debugging of the scripts? 
Yes, I have performed  debugging of scripts. We can debug the script by executing the script in the  debug mode. We can also debug script using the Step, Step Into, Step out  functionalities provided by the WinRunner.
How do  you run your test scripts?
We run tests in Verify mode to  test your application. Each time WinRunner encounters a checkpoint in the test  script, it compares the current data of the application being tested to the  expected data captured earlier. If any mismatches are found, WinRunner captures  them as actual results.
How do  you analyze results and report the defects?
Following each  test run, WinRunner displays the results in a report. The report details all the  major events that occurred during the run, such as checkpoints, error messages,  system messages, or user messages. If mismatches are detected at checkpoints  during the test run, you can view the expected results and the actual results  from the Test Results window. If a test run fails due to a defect in the  application being tested, you can report information about the defect directly  from the Test Results window. This information is sent via e-mail to the quality  assurance manager, who tracks the defect until it is fixed.
What is the use of Test  Director software?
TestDirector is  Mercury Interactive’s software test management tool. It helps quality assurance  personnel plan and organize the testing process. With TestDirector you can  create a database of manual and automated tests, build test cycles, run tests,  and report and track defects. You can also create reports and graphs to help  review the progress of planning tests, running tests, and tracking defects  before a software release.
Have you integrated your  automated scripts from TestDirector? 
When you work with  WinRunner, you can choose to save your tests directly to your TestDirector  database or while creating a test case in the TestDirector we can specify  whether the script in automated or manual. And if it is automated script then  TestDirector will build a skeleton for the script that can be later modified  into one which could be used to test the AUT.
What are the different modes  of recording? 
There are two type of recording in  WinRunner.
Context Sensitive recording records the operations you  perform on your application by identifying Graphical User Interface (GUI)  objects.
Analog recording records keyboard input, mouse clicks, and  the precise x- and y-coordinates traveled by the mouse pointer across the  screen.
What is the purpose of  loading WinRunner Add-Ins?
Add-Ins are used in WinRunner to load  functions specific to the particular add-in to the memory. While creating a  script only those functions in the add-in selected will be listed in the  function generator and while executing the script only those functions in the  loaded add-in will be executed else WinRunner will give an error message saying  it does not recognize the function.
What are the reasons that  WinRunner fails to identify an object on the GUI? 
WinRunner fails  to identify an object in a GUI due to various reasons. The object is not a  standard windows object. If the browser used is not compatible with the  WinRunner version, GUI Map Editor will not be able to learn any of the objects  displayed in the browser window. 
What is meant by the logical name of the object?
An object’s logical name is determined by its class. In most cases, the logical name is the label that appears on an object.
If the object does not have a name then what will be the  logical name?
If the object does not have a name then the logical name  could be the attached text.
What is the different between  GUI map and GUI map files?
The GUI map is actually the sum of one  or more GUI map files. There are two modes for organizing 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.
GUI Map file is a file which contains the windows and the objects learned by the WinRunner with its logical name and their physical description.
How do you view the contents  of the GUI map? 
GUI Map editor displays the content of a GUI Map.  We can invoke GUI Map Editor from the Tools Menu in WinRunner. The GUI Map  Editor displays the various GUI Map files created and the windows and objects  learned in to them with their logical name and physical description.
When you create GUI map do  you record all the objects of specific objects? 
If we are  learning a window then WinRunner automatically learns all the objects in the  window else we will we identifying those object, which are to be learned in a  window, since we will be working with only those objects while creating scripts.  
Winrunner Userful Interview Questions:
1. Give one line answer about WinRunner?
2. How do you  define WinRunner on your own?
3. WinRunner is suitable for which type of  applications?
4. What are all the types of applications WinRunner can  use?
5. What’s the WinRunner version number you used for your  applications?
6. What are all the different types of recordings available in  WinRunner?
7. When do you go for Context Sensitive and Analog recordings?  What’s the difference between them?
8. What are all the Limitations &  Advantages of WinRunner?
9. Where you find that you can’t use WinRunner for  automation?
10. What’s the types application you working on using  WinRunner?
11. What’s your comfort level in using WinRunner?
12. What is  meant by Synchronization? How do you implement it in WinRunner?
13. What is  meant by Check points? Types of Check points? In what situation will you use  it?
14. What are all the different platforms that WinRunner can be  used?
15. Any knowledge of Test Director?
16. Difference between WinRunner  and Test Director?
17. What databases can Test Director reside on?
18.  Explain the project tree in Test Director.
19. Advantages of WinRunner over  other market tools silk, robot etc.?
20. How does Winrunner identify GUI  Objects?
21. What’s the use of GUI Map Editor?
22. Winrunner GUI map  modes?
23. What are the two GUI Map modes available in WinRunner?
24. What  is the use of rapid test script wizard?
25. How will you synchronize tests  using WinRunner? When should you synchronize? Synchronize settings?
26. How  do you check GUI objects?
27. How do you check a bitmap?
28. What is meant  by GUI Spy?
29. Besides Record and Replay what else can be done using  WinRunner?
30. What are different types of running a test?
31. When do you  use Verify/Debug/Update Modes?
32 When do you use Break Points?
33. What  is Toggle Break Points? How it differ from Break points?
34. What’s Step and  Step into?
35. What’s the role of GUI Map Editor? (Its connects logical name  in the script to the physical attributes of the object in the GUI Map  Editor).
36. What is meant by Function Generator? (F7).
37. How do you  load GUI Map Editor?
38. What is injector in load runner?
39. What is TSL?  What 4GL is it similar too?
40. How do you program tests with TSL?
41. How  do you invoke an application using TSL?
42. What is Module? What’s Compiled  Module?
43. Explain data parameterization in WinRunner.
44. What is User  Define Functions? What are all the different types of User
45. What is  Function? Types of Functions?
46. Defined Functions available in  WinRunner?
47. Name a couple of standard web function found in the function  generator? And explain their purpose.
48. Where do you use Private/Public  function in your script?
49. How do you forcibly capture an Object using  WinRunner (when WinRunner not able identify it)?
50. Can you test DB using  WinRunner?
51. What are all the different DB that WinRunner can  support?
52. How do you set a Query to get/fetch data from the DB?
53. How  TSL looks like?
54. What are all the default codes WinRunner will generates  when you start an application?
55. What are the other codes you can  write/call with in TSL? 56. What are all the different languages can be called  using TSL in between the scripts?
57. How do you handle an Exception in  WinRunner?
58. Types of Exception available in WinRunner?
59. How do you  define an Exception for complete application or for a particular  function?
60. How do you run tests on a new version of WinRunner?
61. What  are data driven tests & How Do you create it in WinRunner?
62. What’s the  File Format used in Data Table?
63. How do you link a Data Table in your  script?
64. How do you read text from an application?
65. What is a batch  test? How do you program a batch test?
66. What happens when user interface  changes?
67. Does load testing possible using WinRunner?
68. Does  WinRunner help you in web testing?
69. How do you manage test data, test  result?
70. Questions on TSL: How to generate Functions?
71. Running tests  from the command line?
72. Explain WinRunner Testing Modes?
73. Have you  completed the CPS exam? Which one?
74. Write a short compiled module which  selects random numbers; and what function is used to call your customized  compiled module?
75. What’s the purpose of the wrun.ini file?
 
 
No comments:
Post a Comment