http://quicktesthp.blogspot.com

QTP VBScript new series + Interview Question Bank on QTP for enrichment of Knowledge in QTP

This Site has been brought to you by HP Certified Expert of QTP.

Exciting new articles for October:

1) QTP Tip:Deselect all Radio Buttons

2) HP QTP Crypt Object

3)Adding Hyperlinks in Excel Spreadsheet

Best of Luck Friends ! ! !

Expert QTP
expert.qtp@gmail.com

All Articles are Copyright Protected. These are Free for Reading & Personal Use. Reproduction in Any Form without the Permission is Illegal & Strictly Prohibited.

Copyright © 2009 ExpertQTP

Google Search

Wednesday, October 8, 2008

QTP - Interview Question Bank : Part 9

Q. 81: What is the use of Keyword View in QTP?=====================================

The Keyword View enables you to create and view the steps of your test in a modular, table format. Each step is a row in the Keyword View that is comprised of individual, modifiable parts. You create and modify steps by selecting items and operations in the Keyword View and entering information as required. Each step is automatically documented as youcomplete it, enabling you to view a description of your test in understandable sentences.

===================================================
Q. 82: What are the Conditional and Loop Statements used in the Keyword View in QTP?
===================================================

Using conditional statements, you can incorporate decision making into the tests. Using loop statements, you can run a group of steps repeatedly, either while or until a condition is true. You can also use loop statements to repeat a group of steps a specific number of times. A few conditional & Loop statements are given below:
1) If...Then statement
2) ElseIf...Then statement
3) Else statement
4) While...Wend statement
5) For...Next statement
6) Do...While statement
7) Do...Until statement

=================================================
Q. 83: What is the use of a Comment in the Comment cell of a step in QTP?
=================================================

A Comment is free text entry which can help improve readability and make a test easier to update. For example,you may want to add a comment step at the beginning of each action to specify what that section includes.

QTP does not process comments when it runs a test.

============================================
Q. 84: What are Nesting Actions & what is the use of them?============================================

Sometimes you may want to call an action from within an action. This is called nesting. By nesting actions, you can:

1) Maintain the modularity of your test.
2) Run one or more actions based on the results of a conditional statement.

=============================================
Q. 85: Splitting Actions option is not available under what circumstances in QTP?=============================================

You cannot split an action, and the option is disabled when:
1) An external action is selected
2) The first step of an action is selected
3) You are working with a read-only test
4) Recording a test
5) Running a test

=========================================
Q. 86: What is the use of Action Parameters in QTP?=========================================

Action parameters enable you to transfer input values from your test to a top-level action, from a parent action to a nested action, or from an action to a sibling action that occurs later in the test.

You can use action parameters in any step in your action including function calls.


===================================================
Q. 87: What are the various types of Exit Action Statements in QTP?===================================================

There are four types of exit action statements you can use:
1) ExitAction: Exits the current action, regardless of its iteration attributes.
2) ExitActionIteration: Exits the current iteration of the action.
3) ExitRun: Exits the test, regardless of its iteration attributes.
4) ExitGlobalIteration: Exits the current global iteration.

=====================================
Q. 88: What is the use of check points in QTP?=====================================

A checkpoint is a verification point that compares a current value for a specified property with the expected value for that property. This enables you to identify whether your application is functioning correctly.

When you run the test, QTP compares the expected results of the checkpoint to the current results. If the results do not match, the checkpoint fails. You can view the results of the checkpoint in the Test Results window.

==================================================
Q. 89: What are the situations best suited for using an existing Check Point?==================================================

1) If each page of your application contains your organization’s logo, you can reuse a bitmap checkpoint to verify each occurrence in the application.

2) If your application contains multiple edit boxes, you can reuse a checkpoint to confirm the enabled status of these edit boxes throughout your test.

===================================================
Q. 90: What is the reason that "Add Existing Checkpoint" dialog box is not visible?===================================================

"Add Existing Checkpoint" dialog box option is available only if at least one of the object repositories associated with the current action (including the local object repository) contains at least one checkpoint.

Keyword: QTP Interview Questions, FAQ QTP




Read more...


QTP - Interview Question Bank : Part 8

Q. 71: What are the various types of objects identified by the comparison tool in QTP?
================================================

1) Identical: Objects that appear in both object repository files. There is no difference in their name or in their properties.

2) Matching description, different name: Objects that appear in both object repository files that have different names, but the same description properties and values.

3) Similar description: Objects that appear in both object repository files that have similar, but not identical, description properties and values. One of the objects always has a subset of the properties set of the other object. This implies that it is likely to be a less detailed description of the same object. For example, an object named Button_1 in the second object repository has the same description properties and values as an object named Button_1 in the first object repository, but also has additional properties and values.

Objects that do not have a description, such as Page or Browser objects, are compared by name only. If the same object is contained in both the object repositories but with different names, they will be shown in the object repositories as two separate objects.

4) Unique to first file, or Unique to second file. Objects that appear in only one of the object repository files.

=================================================
Q. 72: What are the situations best suited to Recording in QTP?
=================================================
Recording can be useful in the following situations:

# Recording helps novice QuickTest users learn how QTP interprets the operations you perform on your application, and how it converts them to QTP objects and built-in operations.

# Recording can be useful for more advanced QTP users when working with a new application or major new features of an existing application (for the same reasons described above). Recording is also helpful while developing functions that incorporate built-in QTP keywords.

# Recording can be useful when you need to quickly create a test that tests the basic functionality of an application or feature, but does not require long-term maintenance.

===================================================
Q. 73: What are the advantages of Keyword Driven testing in QTP?
===================================================

1) Keyword-driven testing enables you to design your tests at a business level rather than at the object level.

2) By incorporating technical operations, such as a synchronization statement that waits for client-server communications to finish, into higher level keywords, tests are easier to read and easier for less technical application testers to maintain when the application changes.

3) Keyword-driven testing naturally leads to a more efficient separation between resource maintenance and test maintenance. This enables the automation experts to focus on maintaining objects and functions while application testers focus on maintaining the test structure and design.

4) When you record tests, you may not notice that new objects are being added to the local object repository. This may result in many testers maintaining local object repositories with copies of the same objects. When using a keyword-driven methodology, you select the objects for your steps from the existing object repository. When you need a new object, you can add it to your local object repository temporarily, but you are also aware that you need to add it to the shared object repository for future use.

=========================================
Q. 74: What are Absolute and Relative Paths in QTP?
=========================================

You can save QuickTest resources, such as shared object repositories, function libraries, recovery scenarios or environments, using absolute or relative paths.

1) An absolute path: Describes the full path to a specific file starting from a fixed location such as the root directory, or the drive on which the file is located, and contains all the other sub-directories in the path. An absolute path always points to the specified file, regardless of the current directory.

2) A relative path: Describes the path to a specific file starting from a given directory, and is generally only a portion of the absolute path. A relative path therefore specifies the location of the file relative to the given location in the file system.

Using relative paths means that the paths remain valid when files or folders containing files are moved or copied to other locations or computers, provided that they are moved within the same folder structure. For this reason, we recommend that you use relative paths when saving resources in QTP.

===============================================
Q. 75: What are the situations best suited to keyword-driven methodology in QTP?
===============================================
The keyword-driven methodology is especially useful for organizations that have both technical and less technical users because it offers a clear division of automation tasks. This enables a few experts to maintain the resource framework while less technical users design and maintain automated test steps. Additionally, once the basic infrastructure is in place, both types of users can often do their tasks simultaneously.

===============================================
Q. 76: What are the various categories of output values in QTP?===============================================
we can create following categories of output values:

1) Standard output values
2) Text and text area output values
3) Table output values
4) Database output values
5) XML output values

=================================================
Q. 77: How do you analyze your application to determine your testing needs using QTP?.
=================================================

1) Determine the development environments that QuickTest needs to support:Your application comprises of windows containing a hierarchy of objects that were created in one or more development environments. QTP provides support for these environments using add-ins. You load QTP add-ins when QTP opens by using the Add-in Manager dialog box. You can check which add-ins are loaded by choosing Help > About QuickTest Professional.

2) Prepare the information that QTP needs to identify objects in your application and to open your application at the beginning of a run session. You need to know the URL, the executable file name and path, or other command-line information. Later, you will enter this in Record and Run Settings dialog box.

3) Navigate through your application from a customer’s perspective and perform the tasks that customers might perform. You create an action for each sub-process, or task, a customer might perform. Each process you perform in your application will be represented as a test in QTP. You can create your tests now.

===================================================
Q. 78: In what situations recording mechanism shall be useful in creating the tests in QTP?

===================================================
1) You are new to QTP and want to learn how QTP interprets the operations you perform on your application and how it converts them to QTP objects and built-in operations.

2) You need to quickly create a test that tests the basic functionality of an application or feature, and the test does not require long-term maintenance.

3) You are working with a new application or with major new features of an existing application, and you want to learn how QTP interacts with the application.

4) You are developing functions that incorporate built-in QTP keywords.

==========================================
Q. 79: What are the various recording modes in QTP?==========================================

1) Normal or the default recording mode: This records the objects in your application and the operations performed on them. This mode takes full advantage of the QTP object model, recognizing the objects in your application regardless of their location on the screen.

2) Analog Recording: This enables you to record the exact mouse and keyboard operations you perform in relation to either the screen or the application window. In this recording mode, QTP records and tracks every movement of the mouse as you drag the mouse around a screen or window.

3) Low Level Recording:This enables you to record on any object in your application, whether or not QTP recognizes the specific object or the specific operation. This mode records at the object level and records all run-time objects as Window or WinObject test objects.

===================================================
Q. 80: How can we switch to Low Level Recording mode while editing a test?===================================================

You can switch to Low Level Recording mode only while recording a test. The option is not available while editing a test.

Keyword: QTP Interview Questions, FAQ QTP


Read more...


Tuesday, October 7, 2008

Usage of &_ in QTP Script

We use &_ to separate multiple lines inside our script whom we want to execute as a single command by clubbing together. Lets see the below mentioned example to make the point more clearer.


As you must have observed above, the character “&” is used to concatenate the strings while the character “_” is used to concatenate multiple lines. So on combining these two characters ie “&_” we are instructing QTP to concatenate strings spanning across multiple lines.

We could have wrote the “f.Write…………” in single line but it would have been very hard to read.

A more simple example to illustrate the usage can be:

Browser(“QTP”).Page(“QTP”). WebEdit("TextField").Set “Expert”&_
"loves QTP" &_
"Any Doubts?"

Keywords: QTP


Read more...


 
Copyright © 2009 ExpertQTP