Win Runner

Content

1. Automation
2. GUIMAP - how manage, what if script runs fine on one machine but not another?
3. Code organization, frequently used commands?
4. Test Director – database?
5. Source control?
6. How use/test GUI checkpoints and dynamicly changing items?
7. Database checkpoints?
8. Synchronization?
9. Data driven tests?
10. How handle unexpected events or errors?
11. Regular expressions?
12. Use of external libraries?
13. Java and web test addins? It will be very helpful.

Questions

1. Give one line answer about WR?

Ans. WinRunner helps you automate the testing process, from test development to
execution. You can create adaptable and reusable test scripts that challenge the
functionality of your application. Prior to a software release, you can run these
tests in a single overnight run—enabling you to detect defects and ensure
superior software quality.

2. How do you define WR on your own?

Ans. WR can be used for functional testing for both the Desktop and Web based applications.

3. WR is suitable for which type of applications?

Ans. WinRunner is suitable for any type of application whether it is a desktop application, web application or a client server application.

4. What kind of applications WR suits?
Ans. Visual Basic, Power Builder, Active-X, Java and Web Applications

5. What are all the different types of recordings available in WR?
Ans. WinRunner has 2 types of recording modes namely
a. Context Sensitive Recording mode : identifies the GUI objects with their logical names
b. Analog Recording Mode : identifies the GUI objects based on the screen coordinates

6. When do you go for Context Sensitive and Analog? What's the difference between them?
Ans. Analog is opted when we perform GUI Testing and Context sensitive for Functionality testing.

7. What's the WR version no you used for your applications?
Ans. I have been working with WinRunner Version Number 7.0.

8. What is Module? What's Compiled Module?
Ans. Compiled modules are libraries of frequently-used functions. You can save user defined functions in compiled modules and then call the functions from your test scripts.
A compiled module is a script containing a library of user-defined functions that you want to call frequently from other tests. When you load a compiled module,
its functions are automatically compiled and remain in memory. You can call them directly from within any test.
A module is a separable part of the system which can be executed individually.

9. What are User Defined Functions? What are all the different types of Functions available in WR? What is Function? Types of Functions?
Ans. The Functions which are written by the user to accomplish a specific functionality of his requirement are called user defined functions. The user defined functions are stored in a compiled module so that any test can use this function after loading the compiled module.
The different types of functions in WinRunner are
a. Context Sensitive Functions
b. Analog Functions
c. Standard Functions
d. Custom Functions

10. Where do you use Private/Public function in your script?
Ans. A private function defined in a script can be used/called from only that script where as a public function can be used/called from any script.

11. How do you forcibly capture an Object using WR (when WR not able identify it)?
Ans. GUI Map Configuration

12. How TSL looks like? What are all the default files does WR generate when you create a script?
Ans. TSL looks like c language. In fact its c only. The files/folders that are generated by WinRunner when a script is created is db, exp and res.

13. What is the extension for the check points?
Ans. The extension for the checklist are .ckl

14. How do you invoke an application using TSL?
Ans. Using Invoke_application function.

15. What's the use of GUI Map Editor?
Ans. GUI Map Editor is used to record the objects in the Current Window of your application.

16. What's Data Driven Test?
Ans. Testing the same set of functionality using WinRunner with different inputs is called Data Driven Testing.

17. What's the File Format used in Data Table?
Ans. The File Format used for Data Table in Data Driven Testing in WinRunner is Microsoft Excel.


18. How do you link a Data Table in your script?
Ans. Using the ddt_open function in TSL we will be linking to the data table from our script.

19. What are all the different languages that can be called using TSL in between the scripts?
Ans. Mostly C language

20. What are all the Limitations & Advantages of WR?
Ans. You cannot install WinRunner 7.0 over network installations of previous versions of WinRunner.

Workaround: When performing a network installation of WinRunner, either remove installations of previous versions first, or install the new version in a different location.

Refer ReadMe document ….for more number of limitations

21. Where do you find that WR cannot be used for automation?
Ans. Automation is not preferred if the project size is small, manual intervention is necessary.

22. What is meant by Synchronization? How do you implement it in WR?
Ans. A synchronization point in your test script instructs WinRunner to
suspend running the test until the application being tested is ready, and then to
continue the test.


23. What is meant by Checkpoints? Types of Checkpoints? In what situation will you use it?
Ans. Checkpoints allow you to compare the current behavior of the application being
tested to its behavior in an earlier version. Various check points are

· GUI Checkpoint
· Bitmap Checkpoint
· Database Checkpoint
· Text checkpoints

24. How do you handle an Exception in WR? Types of Exception available in WR?
Ans. Exceptions in WinRunner are handled using the Exceptional Handling Concepts. And the different types of exceptions available in WinRunner are as follows:
· Pop-up exceptions: Instruct WinRunner to detect and handle the appearance of a specific window.
· TSL exceptions: Instruct WinRunner to detect and handle TSL functions that return a specific error code.
· Object exceptions: Instruct WinRunner to detect and handle a change in a property for a specific GUI object.
· Web exceptions: When the Web Test add-in is loaded, you can instruct WinRunner to handle unexpected events and errors that occur in your Web site during a test run.

25. How do you define an Exception for complete application or for a particular function?
Ans. We first define a TSL Function and then write a handler function in the compiled module for that exception and load that particular compiled module in the script in which you want to handle the exception through out the application…mostly in the main script.

26. What are all the different platforms that WR can be used?
Ans. WinRunner can be used only on Windows Platforms namely Windows 95, Windows 98, Windows NT, Windows 2000 and XP(wr ver 7.5).

27. What does GUI Spy mean?
Ans. GUI Spy is used to identify the properties of an object on the desktop.
You can use the Spy pointer to point to an object, and the GUI Spy displays the properties and their values in the GUI Spy dialog box. You can choose to view all the properties
of an object, or only the selected set of properties that WinRunner learns.

28. Can you test DB using WR? What are all the different DB Checkpoints that WR can support?
Ans. Yes we can check the database using WinRunner. There are all together 3 types of database checkpoints in WinRunner namely Default Database Checkpoint, Custom Database Checkpoint, and Runtime Database Checkpoint.