Explore topic-wise InterviewSolutions in .

YES, you can have problems with OBJECT REPOSITORY while identifying the objects. Also, if you are USING Shared Repository, then if you are changing properties of an object which you want to reflect only in that PARTICULAR action, will be reflected in all other actions of that test.

Yes, you can have problems with Object repository while identifying the objects. Also, if you are using Shared Repository, then if you are changing properties of an object which you want to reflect only in that particular action, will be reflected in all other actions of that test.

Two types of OBJECT REPOSITORIES are

• Per-Action (default)
• SHARED

We are USING Shared Object Repository.

Two types of Object Repositories are

We are using Shared Object Repository.

An Object Repository is an INTERFACE between QTP script and the Application.
QUICK Test stores all its OBJECTS information in Object Repository to identify them later.

An Object Repository is an interface between QTP script and the Application.
Quick Test stores all its objects information in Object Repository to identify them later.

• In Copy to ACTION you will copy the SCRIPT of an Action and hence can make NECESSARY modifications to the script.
• In Call to Action you are directly calling an Action EITHER from the same test or from some other test. So, you can’t make any changes to the script. If you WANT to do any changes to the script, you need to go to that particular test and make changes.

An Action is a SERIES of operations to do some work. There are 3 types of Actions in QTP. They are
i) Non-REUSABLE Action (default)
II) Reusable Action
III) External Action

An Action is a series of operations to do some work. There are 3 types of Actions in QTP. They are
i) Non-Reusable Action (default)
ii) Reusable Action
iii) External Action

• Test object are basic and GENERIC OBJECTS that QTP RECOGNIZE.
• RUNTIME object means the actual object to which a test object maps

Two TYPES.

• TEST Objects and
• Run Time Objects.

Two types.

• Test SETTINGS are settings of that PARTICULAR test only.
• Global Settings are settings that REFLECT any test in QTP.

TEST RUN MODE, UPDATE Run Mode and DEBUG Run Mode

Test Run Mode, Update Run Mode and Debug Run Mode

No

No

• Analog Mode is used for SIGNATURES.
• LOW – LEVEL Mode is used when your QUICK test is not RECOGNIZING certain objects in your Application.

ANALOG RECORDING will record the Mouse & Keyboard movements with RESPECT to the Window or Application co-ordinates. Whereas low-level recording will record the all the objects in the Application whether or not QUICK Test RECOGNIZES them.

Analog recording will record the Mouse & Keyboard movements with respect to the Window or Application co-ordinates. Whereas low-level recording will record the all the objects in the Application whether or not Quick Test recognizes them.

THREE MODES. They are NORMAL, ANALOG, and Low-level

Three modes. They are Normal, Analog, and Low-level

Both. DEVELOPING the SCRIPT DEPENDS on the TEST SCENARIO.

Both. Developing the Script depends on the Test Scenario.

YES. UNI-CODE is a 16-bit MACHINE UNDERSTANDABLE LANGUAGE.

Yes. UNI-CODE is a 16-bit machine understandable language.

ACTIVEX, VISUAL BASIC, WEB, MULTIMEDIA

ActiveX, Visual Basic, Web, Multimedia

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.

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.

CODE FILE EXTENSION is.vbs and OBJECT REPOSITORY is.tsr

Code file extension is.vbs and object repository is.tsr

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 IDENTIFIES and checks the object during the RUN session.

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 identifies and checks the object during the run session.

QTP IDENTIFIES the object in the APPLICATION by LOGICAL Name and CLASS.

QTP identifies the object in the application by Logical Name and Class.

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 Accessibility 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 website.

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.

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.

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.

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.

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.