This is a discussion on QTP tips within the Testing Tools forums, part of the Software Quality Assurance category; How to add a standard checkpoint in your test ? 1. Start QuickTest and open your test. In the Open Test ...
| |||||||
| Register | FAQ | Members List | Calendar | Mark Forums Read |
| |||
| How to add a standard checkpoint in your test ? 1. Start QuickTest and open your test. In the Open Test dialog box, locate and select your test, then click Open. 2. Save the test as Checkpoint. Select File > Save As. Save the test as Checkpoint. 3. Confirm that the Active Screen option is enabled. If you do not see the Active Screen at the bottom of the QuickTest window, click the Active Screen button, or choose View > Active Screen. 4. Locate the page where you want to add a standard checkpoint. 5 Create a standard checkpoint. In the Active Screen, right-click element in your application and choose Insert Standard Checkpoint. 6 Save the test. - Vignesh ![]() |
| Sponsored Links |
| |||
| How to add a page checkpoint to your test? "The page checkpoint checks that the number of links and images in the page when you run your test is the same as when you recorded your test. 1 Locate the page where you want to add a page checkpoint. 2 Create a page checkpoint. Right-click anywhere in the Active Screen, and choose Insert Standard Checkpoint. The Object Selection - Checkpoint Properties dialog box opens. Note that this dialog box may include different elements, depending on where you click in the Active Screen. 3 Save the test. " - Vignesh ![]() |
| |||
| 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. " - Vignesh ![]() |
| |||
| What is keyword view and Expert view in QTP? "QuickTest’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 QuickTest Professional automatically generates. Any changes made in the Expert View are automatically synchronized with the Keyword View. " - Vignesh ![]() |
| |||
| How QTP recognizes Objects in AUT? "QuickTest stores the definitions for application objects in a file called the Object Repository. As you record your test, QuickTest will add an entry for each item you interact with. Each Object Repository entry will be identified by a logical name (determined automatically by QuickTest), and will contain a set of properties (type, name, etc) that uniquely identify each object. Each line in the QuickTest 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." - Vignesh ![]() |
| |||
| What are the types of Object Repositorys in QTP? "QuickTest 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, QuickTest 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. " - Vignesh ![]() |
| |||
| How to "Turn Off" QTP results after running a Script? "Goto "Tools > Options > Run Tab" and Deselect "View results when run session ends". But this supresses only the result window, but a og will be created and can viewed manulaly which cannot be restricted from getting created. " - Vignesh ![]() |
| |||
| Explain about the Test Fusion Report of QTP ? "Once a tester has run a test, a TestFusion 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 TestFusion reports with QuickTest Professional, you can share reports across an entire QA and development team. " - Vignesh ![]() |
| |||
| To which environments does QTP supports ? "QuickTest 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." - Vignesh ![]() |
| |||
| What's QuickTest Window? Before you begin creating tests, you should familiarize yourself with the main QuickTest window. The QuickTest window contains the following key elements: . Title bar—Displays the name of the currently open test. . Menu bar—Displays menus of QuickTest commands. . File toolbar—Contains buttons to assist you in managing your test. . Testing toolbar—Contains buttons to assist you in the testing process. . Debug toolbar—Contains buttons to assist you in debugging tests. . Test pane—Contains the Keyword View and Expert View tabs. . Active Screen—Provides a snapshot of your application as it appeared when you performed a certain step during the recording session. . Data Table—Assists you in parameterizing your test. . Debug Viewer pane—Assists you in debugging your test. The Debug Viewer pane contains the Watch Expressions, Variables, and Command tabs. (The Debug Viewer pane is not displayed when you open QuickTest for the first time. You can display the Debug Viewer by choosing View < Debug Viewer.) . Status bar—Displays the status of the QuickTest application. - Vignesh ![]() |
| |||
| How does QTP identifes the object in the application "QTP identifies the object in the application by LogicalName and Class. For example : The Edit box is identified by Logical Name : PSOPTIONS_BSE_TIME20 Class: WebEdit " - Vignesh ![]() |
| |||
| Table and DB Checkpoints: By adding table checkpoints to your tests or components, you can check that a specified value is displayed in a cell in a table on your application. By adding database checkpoints to your tests or components, you can check the contents of databases accessed by your application. The results displayed for table and database checkpoints are similar. When you run your test or component, QuickTest compares the expected results of the checkpoint to the actual results of the run session. If the results do not match, the checkpoint fails. You can check that a specified value is displayed in a cell in a table by adding a table checkpoint to your test or component. For ActiveX tables, you can also check the properties of the table object. To add a table checkpoint, you use the Checkpoint Properties dialog box. Table checkpoints are supported for Web and ActiveX applications, as well as for a variety of external add-in environments. You can use database checkpoints in your test or component to check databases accessed by your Web site or application and to detect defects. You define a query on your database, and then you create a database checkpoint that checks the results of the query. Database checkpoints are supported for all environments supported by QuickTest, by default, as well as for a variety of external add-in environments. There are two ways to define a database query: (a) Use Microsoft Query. You can install Microsoft Query from the custom installation of Microsoft Office. (b) Manually define an SQL statement. The Checkpoint timeout option is available only when creating a table checkpoint. It is not available when creating a database checkpoint - Vignesh ![]() |
| |||
| What are the Features & Benefits of Quick Test Pro(QTP)..? 1. Key word driven testing 2. Suitable for both client server and web based application 3. Vb script as the scriot language 4. Better error handling mechanism 5. Excellent data driven testing features - Vignesh ![]() |
| |||
| What are the Features & Benefits of Quick Test Pro (QTP 8.0)? "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. " - Vignesh ![]() |
| |||
| How to handle the exceptions using recovery secnario manager in Qtp? "You can instruct QTP to recover unexpected events or errors that occured 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" - Vignesh ![]() |
| |||
| what is the use of Text output value in Qtp? "Output values enable to view the values that the application talkes during run time.When paramaterised, 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." - Vignesh ![]() |
| |||
| What information do the columns in the Keyword View show for each step? "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 follows: . 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 “findFlights” image. - Vignesh ![]() |
| |||
| Why use Regular Expressions? "you created a text checkpoint that searched for a specific text string. You can use regular expressions to increase the flexibility and adaptability of your tests. Regular expressions enable QuickTest to identify objects and text strings with varying values. You can use regular expressions when defining the properties of an object, the methods of an argument, when parameterizing a step, and when creating checkpoints with varying values" - Vignesh ![]() |
| |||
| Explain QTP Testing process ? The QuickTest testing process consists of 6 main phases: 1. 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. 2. Recording a session on your application: As you navigate through your application, QuickTest 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. 2. 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. 3. Debugging your test: If changes were made to the script, you need to debug it to check that it operates smoothly and without interruption. 4. Running your test on a new version of your application: You run a test to check the behavior of your application. While running, QuickTest connects to your application and performs each step in your test. 5. Analyzing the test results: You examine the test results to pinpoint defects in your application. 6. Reporting defects: As you encounter failures in the application when analyzing test results, you will create defect reports in Defect Reporting Tool. - Vignesh ![]() |
| |||
| 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. " - Vignesh ![]() |
![]() |
| Thread Tools | |
| Display Modes | |
| |