QTP Session 2- Enhancing Your Test

Enhancing Your Test

Using QuickTest, you can include checkpoints that broaden the scope of your test. A checkpoint verifies that expected information is displayed in your application while the test is running. For example, in the course registration test described earlier, the user could have added a checkpoint that evaluated the property values of the Course Name edit box. Most checkpoints can be added to a test either while recording or after recording. Using QuickTest, you can: §  Replace fixed values with parameters. §  Add logic. §  Create conditional or loop statements.

Debugging Your Test

After you create a test, you should check that it runs smoothly, without errors in syntax and logic. You control the test run in the following ways: §  Using the step commands: Step Into, Step Out, and Step Over, to run a single step of a test. §  Using the Pause command to temporarily suspend a test run. §  Setting breakpoints to stop a test run at a pre-determined place. If QuickTest displays a run-error message during a test run, you can simply click the Debug button to suspend the test and debug it.

Running Your Test

When you run a test, QuickTest opens the web site or application and performs the steps you recorded. QuickTest always runs a test from the first step, unless you specify otherwise. For example, you could choose these options: §  Start your test run from a selected step §  Enter parameters to run the test for each row in the data table §  Run only certain data sets §  Run your test until a specific point within the test A yellow arrow in the left margin of the Keyword View indicates the step that QuickTest is running.

Analyzing Test Results

As your test runs, QuickTest captures the results of each step. When QuickTest finishes running the test, the Test Results window opens. You examine the test results to pinpoint defects in your application.

Reporting Defects

You can print test results or, if you have Mercury Quality Center installed, you can report the defects you discover to a database. Mercury Quality Center is a software test management tool. A connection button from the Test Results window lets you add defects to a specific Quality Center project.

QTP Session 1- Recording

Preparing to Record

Before you record a test, confirm that your application and QuickTest are set to match the needs of your test. 1.     Make sure your application displays elements you want to record, such as a toolbar or a special window pane. 2.     Check to see, that your application options are set for the purposes of your test. 3.     View the settings in the Test Settings dialog box (Test > Settings) to ensure that data will be recorded and stored correctly. 4.     Review the Options dialog box (Tools > Options) to ensure that QuickTest will record and store information appropriately. For example, you should confirm that the test is set to use the appropriate object repository mode. 5.     Make sure that all browsers are closed before you begin recording.

Recording a Session

As you navigate through your application or Web site, QuickTest graphically displays each step you perform as a row in the Keyword View. A step is any user action that causes or makes a change in your application, such as clicking a link or image, or entering data in a form. For example, if you wanted to test your course registration website, you would: 1.     Create a new, blank, test file. 2.     Click the Record button and enter the details about the type of application being tested. 3.     Log on to your corporate website and perform the steps to register for a class. 4.     Click the Stop button to end the test. QuickTest recorded your web browser operations from the time you clicked Record until you clicked Stop.

Review a Recording

As you recorded your test, QuickTest generated steps in the Keyword View representing each operation you performed in the web browser.

The columns in the Keyword View show different information for each step, as described in this table:

Column	Description
Item	Displays the item for the step (test object, utility object, function call, or statement) in a hierarchical icon-based tree.
Operation	The operation to be performed on the item, for example, Click or Select.
Value	The argument values for the selected operation, for example, the mouse button to use when clicking the image.
Assignment	The assignment of a value to or from a variable so you can use the value later in the test.
Comment	Any textual information you want to add regarding the step, for example, Return to page used in first step of the test.
Documentation	Auto-documentation of what the step does, in an easy-to-understand sentence, for example, Click the "See Details" icon.

Basic of Automation using QTP

Benefits of Automated Testing

If you have ever tested applications or Web sites manually, you are aware of the drawbacks. Manual testing is time-consuming and tedious, requiring a heavy investment in human resources. Time constraints often make it impossible to manually test every feature thoroughly before the application is released. Serious bugs may have gone undetected. Automated testing with QuickTest Professional addresses these problems by:

§  Dramatically speeding up the testing process.

§  Facilitating the creation of tests that check all aspects of an application or web site.

• Providing reusability for running these tests every time the site or application changes.

As QuickTest runs tests, it simulates a human user by moving the mouse cursor in
a Web page or application window, clicking Graphical User Interface (GUI) objects,
and entering keyboard input; however, QuickTest does this faster than any human user.

Optimizing Browser Settings

If you are using Internet Explorer as your browser, you should clear the option to use auto complete for user names and passwords. This will ensure that all of your operations are accurately recorded while creating your tests.
To clear the auto complete option:

§  In your Internet Explorer menu bar, choose Tools > Internet Options > Content tab.

§  Click AutoComplete in the Personal information area. The Autocomplete Settings dialog box opens.

§  In the Use AutoComplete for area, clear the User names and passwords on forms option.

§  Click OK to save your changes and close the AutoComplete Settings dialog box, then click OK again to close the Internet Options dialog box.

QuickTest Windows

Before you begin creating tests, take a moment to become familiar with the main QuickTest window. The image below shows QuickTest window as it would appear after you record a test, with all toolbars and panes (except the Debug Viewer pane) displayed. Place your mouse over the titles to display a description of these key elements.

The Testing Process

The QuickTest testing process consists of seven main phases:

1.     Preparing to record

2.     Recording a session on your application

3.     Enhancing your test

4.     Debugging your test

5.     Running your test

6.     Analyzing the test results

7.     Reporting defects

This tutorial provides you with an introduction to each of these phases.

QTP Interview Questions

1. What are the Features & Benefits of Quick Test Pro Operates stand-alone, or integrated into Mercury Business Process Testing and Mercury Quality Center. Introduces next-generation zero-configuration Keyword Driven testing technology in Quick Test Professional 8.0 allowing for fast test creation, easier maintenance, and more powerful data-driving capability. Identifies objects with Unique Smart Object Recognition, even if they change from build to build, enabling reliable unattended script execution. Collapses test documentation and test creation to a single step with Auto-documentation technology. Enables thorough validation of applications through a full complement of checkpoints.
2. How to handle the exceptions using recovery scenario manager in QTP? - There are 4 trigger events during which a recovery scenario should be activated. A pop up window appears in an opened application during the test run: A property of an object changes its state or value, A step in the test does not run successfully, An open application fails during the test run, These triggers are considered as exceptions.You can instruct QTP to recover unexpected events or errors that occurred in your testing environment during test run. Recovery scenario manager provides a wizard that guides you through the defining recovery scenario. Recovery scenario has three steps: 1. Triggered Events 2. Recovery steps 3. Post Recovery Test-Run
3. What is the use of Text output value in QTP? - Output values enable to view the values that the application talks during run time. When parameterized, the values change for each iteration. Thus by creating output values, we can capture the values that the application takes for each run and output them to the data table.
4. How to use the Object spy in QTP 8.0 version? - There are two ways to Spy the objects in QTP: 1) Thru file toolbar, In the File Toolbar click on the last toolbar button (an icon showing a person with hat). 2) True Object repository Dialog, In Object repository dialog click on the button object spy. In the Object spy Dialog click on the button showing hand symbol. The pointer now changes in to a hand symbol and we have to point out the object to spy the state of the object if at all the object is not visible. or window is minimized then, hold the Ctrl button and activate the required window to and release the Ctrl button.
5. How Does Run time data (Parameterization) is handled in QTP? - You can then enter test data into the Data Table, an integrated spreadsheet with the full functionality of Excel, to manipulate data sets and create multiple test iterations, without programming, to expand test case coverage. Data can be typed in or imported from databases, spreadsheets, or text files.
6. What is keyword view and Expert view in QTP? - Quick Test’s Keyword Driven approach, test automation experts have full access to the underlying test and object properties, via an integrated scripting and debugging environment that is round-trip synchronized with the Keyword View. Advanced testers can view and edit their tests in the Expert View, which reveals the underlying industry-standard VBScript that Quick Test Professional automatically generates. Any changes made in the Expert View are automatically synchronized with the Keyword View.
7. Explain about the Test Fusion Report of QTP? - Once a tester has run a test, a Test Fusion report displays all aspects of the test run: a high-level results overview, an expandable Tree View of the test specifying exactly where application failures occurred, the test data used, application screen shots for every step that highlight any discrepancies, and detailed explanations of each checkpoint pass and failure. By combining Test Fusion reports with Quick Test Professional, you can share reports across an entire QA and development team.
8. Which environments does QTP support? - Quick Test Professional supports functional testing of all enterprise environments, including Windows, Web,..NET, Java/J2EE, SAP, Siebel, Oracle, PeopleSoft, Visual Basic, ActiveX, mainframe terminal emulators, and Web services.
9. What is QTP? - Quick Test is a graphical interface record-playback automation tool. It is able to work with any web, java or windows client application. Quick Test enables you to test standard web objects and ActiveX controls. In addition to these environments, Quick Test Professional also enables you to test Java applets and applications and multimedia objects on Applications as well as standard Windows applications, Visual Basic 6 applications and.NET framework applications
10. Explain QTP Testing process? - Quick Test testing process consists of 6 main phases:
11. Create your test plan - Prior to automating there should be a detailed description of the test including the exact steps to follow, data to be input, and all items to be verified by the test. The verification information should include both data validations and existence or state verifications of objects in the application.
12. Recording a session on your application - As you navigate through your application, Quick Test graphically displays each step you perform in the form of a collapsible icon-based test tree. A step is any user action that causes or makes a change in your site, such as clicking a link or image, or entering data in a form.
13. Enhancing your test - Inserting checkpoints into your test lets you search for a specific value of a page, object or text string, which helps you identify whether or not your application is functioning correctly. NOTE: Checkpoints can be added to a test as you record it or after the fact via the Active Screen. It is much easier and faster to add the checkpoints during the recording process. Broadening the scope of your test by replacing fixed values with parameters lets you check how your application performs the same operations with multiple sets of data. Adding logic and conditional statements to your test enables you to add sophisticated checks to your test.
14. Debugging your test - If changes were made to the script, you need to debug it to check that it operates smoothly and without interruption.
15. Running your test on a new version of your application - You run a test to check the behavior of your application. While running, Quick Test connects to your application and performs each step in your test.
16. Analyzing the test results - You examine the test results to pinpoint defects in your application.
17. Reporting defects - As you encounter failures in the application when analyzing test results, you will create defect reports in Defect Reporting Tool.
18. Explain the QTP Tool interface. - It contains the following key elements: Title bar, displaying the name of the currently open test, Menu bar, displaying menus of Quick Test commands, File toolbar, containing buttons to assist you in managing tests, Test toolbar, containing buttons used while creating and maintaining tests, Debug toolbar, containing buttons used while debugging tests. Note: The Debug toolbar is not displayed when you open Quick Test for the first time. You can display the Debug toolbar by choosing View — Toolbars — Debug. Action toolbar, containing buttons and a list of actions, enabling you to view the details of an individual action or the entire test flow. Note: The Action toolbar is not displayed when you open Quick Test for the first time. You can display the Action toolbar by choosing View — Toolbars — Action. If you insert a reusable or external action in a test, the Action toolbar is displayed automatically. Test pane, containing two tabs to view your test-the Tree View and the Expert View ,Test Details pane, containing the Active Screen. Data Table, containing two tabs, Global and Action, to assist you in parameterizing your test. Debug Viewer pane, containing three tabs to assist you in debugging your test-Watch Expressions, Variables, and Command. (The Debug Viewer pane can be opened only when a test run pauses at a breakpoint.) Status bar, displaying the status of the test
19. How does QTP recognize Objects in AUT? - Quick Test stores the definitions for application objects in a file called the Object Repository. As you record your test, Quick Test will add an entry for each item you interact with. Each Object Repository entry will be identified by a logical name (determined automatically by Quick Test), and will contain a set of properties (type, name, etc) that uniquely identify each object. Each line in the Quick Test script will contain a reference to the object that you interacted with, a call to the appropriate method (set, click, check) and any parameters for that method (such as the value for a call to the set method). The references to objects in the script will all be identified by the logical name, rather than any physical, descriptive properties.
20. What are the types of Object Repositories in QTP? - Quick Test has two types of object repositories for storing object information: shared object repositories and action object repositories. You can choose which type of object repository you want to use as the default type for new tests, and you can change the default as necessary for each new test. The object repository per-action mode is the default setting. In this mode, Quick Test automatically creates an object repository file for each action in your test so that you can create and run tests without creating, choosing, or modifying object repository files. However, if you do modify values in an action object repository, your changes do not have any effect on other actions. Therefore, if the same test object exists in more than one action and you modify an object’s property values in one action, you may need to make the same change in every action (and any test) containing the object.
21. Explain the check points in QTP? - A checkpoint verifies that expected information is displayed in an Application while the test is running. You can add eight types of checkpoints to your test for standard web objects using QTP. A page checkpoint checks the characteristics of an Application. A text checkpoint checks that a text string is displayed in the appropriate place on an Application. An object checkpoint (Standard) checks the values of an object on an Application. An image checkpoint checks the values of an image on an Application. A table checkpoint checks information within a table on a Application. An Accessibilityy checkpoint checks the web page for Section 508 compliance. An XML checkpoint checks the contents of individual XML data files or XML documents that are part of your Web application. A database checkpoint checks the contents of databases accessed by your web site
22. In how many ways we can add check points to an application using QTP? - We can add checkpoints while recording the application or we can add after recording is completed using Active screen (Note : To perform the second one The Active screen must be enabled while recording).
23. How does QTP identify objects in the application? - QTP identifies the object in the application by Logical Name and Class.
24. What is Parameterizing Tests? - When you test your application, you may want to check how it performs the same operations with multiple sets of data. For example, suppose you want to check how your application responds to ten separate sets of data. You could record ten separate tests, each with its own set of data. Alternatively, you can create a parameterized test that runs ten times: each time the test runs, it uses a different set of data.
25. What is test object model in QTP? - The test object model is a large set of object types or classes that Quick Test uses to represent the objects in your application. Each test object class has a list of properties that can uniquely identify objects of that class and a set of relevant methods that Quick Test can record for it. A test object is an object that Quick Test creates in the test or component to represent the actual object in your application. Quick Test stores information about the object that will help it identify and check the object during the run session.
26. What is Object Spy in QTP? - Using the Object Spy, you can view the properties of any object in an open application. You use the Object Spy pointer to point to an object. The Object Spy displays the selected object’s hierarchy tree and its properties and values in the Properties tab of the Object Spy dialog box.
27. What is the Diff between Image check-point and Bit map Check point? - Image checkpoints enable you to check the properties of a Web image. You can check an area of a Web page or application as a bitmap. While creating a test or component, you specify the area you want to check by selecting an object. You can check an entire object or any area within an object. Quick Test captures the specified object as a bitmap, and inserts a checkpoint in the test or component. You can also choose to save only the selected area of the object with your test or component in order to save disk Space. For example, suppose you have a Web site that can display a map of a city the user specifies. The map has control keys for zooming. You can record the new map that is displayed after one click on the control key that zooms in the map. Using the bitmap checkpoint, you can check that the map zooms in correctly. You can create bitmap checkpoints for all supported testing environments (as long as the appropriate add-ins are loaded). Note: The results of bitmap checkpoints may be affected by factors such as operating system, screen resolution, and color settings.
28. How many ways we can parameterize data in QTP? - There are four types of parameters: Test, action or component parameters enable you to use values passed from your test or component, or values from other actions in your test. Data Table parameters enable you to create a data-driven test (or action) that runs several times using the data you supply. In each repetition, or iteration, Quick Test uses a different value from the Data Table. Environment variable parameters enable you to use variable values from other sources during the run session. These may be values you supply, or values that Quick Test generates for you based on conditions and options you choose. Random number parameters enable you to insert random numbers as values in your test or component. For example, to check how your application handles small and large ticket orders, you can have Quick Test generate a random number and insert it in a number of tickets edit field.
29. How do u do batch testing in WR & is it possible to do in QTP, if so explain? - Batch Testing in WR is nothing but running the whole test set by selecting Run Test set from the Execution Grid. The same is possible with QTP also. If our test cases are automated then by selecting Run Test set all the test scripts can be executed. In this process the Scripts get executed one by one by keeping all the remaining scripts in Waiting mode.
30. If I give some thousand tests to execute in 2 days what do u do? - Adhoc testing is done. It Covers the least basic functionalities to verify that the system is working fine.
31. What does it mean when a check point is in red color? what do u do? - A red color indicates failure. Here we analyze the cause for failure whether it is a Script Issue or Environment Issue or a Application issue.
32. What is Object Spy in QTP? - Using the Object Spy, you can view the properties of any object in an open application. You use the Object Spy pointer to point to an object. The Object Spy displays the selected object’s hierarchy tree and its properties and values in the Properties tab of the Object Spy dialog box.
33. What is the file extension of the code file & object repository file in QTP? - Code file extension is.vbs and object repository is.tsr
34. Explain the concept of object repository & how QTP recognizes objects? - Object Repository: displays a tree of all objects in the current component or in the current action or entire test (depending on the object repository mode you selected). We can view or modify the test object description of any test object in the repository or to add new objects to the repository. Quicktest learns the default property values and determines in which test object class it fits. If it is not enough it adds assistive properties, one by one to the description until it has compiled the unique description. If no assistive properties are available, then it adds a special Ordinal identifier such as objects location on the page or in the source code.
35. What are the properties you would use for identifying a browser & page when using descriptive programming? - Name would be another property apart from title that we can use.
36. Give me an example where you have used a COM interface in your QTP project? - com interface appears in the scenario of front end and back end. for eg:if you r using oracle as back end and front end as VB or any language then for better compatibility we will go for an interface. of which COM will be one among those interfaces. Create object creates handle to the instance of the specified object so that we program can use the methods on the specified object. It is used for implementing Automation(as defined by Microsoft).
37. Explain in brief about the QTP Automation Object Model. - Essentially all configuration and run functionality provided via the Quick Test interface is in some way represented in the Quick Test automation object model via objects, methods, and properties. Although a one-on-one comparison cannot always be made, most dialog boxes in Quick Test have a corresponding automation object, most options in dialog boxes can be set and/or retrieved using the corresponding object property, and most menu commands and other operations have corresponding automation methods. You can use the objects, methods, and properties exposed by the Quick Test automation object model, along with standard programming elements such as loops and conditional statements to design your program.

Automation Object Model - Sample QTP Script

'AOM
'Code for Automating the QTP Operation by using Automation Object Model

Option Explicit
Dim qtapp,qtrep,qtfun,qttest
set qtapp=CreateObject("QuickTest.Application")
qtapp.Launch
qtapp.Visible=true
qtapp.ActivateView "ExpertView"
qtapp.ShowpaneScreen "Datatable",True
qtapp.ShowpaneScreen "ActiveScreen",True
qtapp.ShowpaneScreen "DebugViewer",True
qtapp.Open "C:\Documents and Settings\Administrator\Desktop\Recovery"
set qtrep=qtapp.Test.Actions("Action1").ObjectRepositories
qtrep.Add "C:\Documents and Settings\Administrator\Desktop\Rep123.tsr"
set qtfun=qtapp.Test.Settings.Resources.Libraries
qtfun.Add "C:\Documents and Settings\Administrator\Desktop\funlib.vbs"
set qttest=qtapp.Test
qttest.Run
qtapp.windowstate="maximized"
qtapp.quit
set qtapp=Nothing
set qtrep=nothing
set qtfun=nothing
set qttest=nothing
'**********************************************************