Custom Search

HP QTP Question Database: Q. 61 to 70

HP QTP Question Database: Q. 61 to 70

Q. 61: How can we perform Merge Operations among various Object Repositories?

The Object Repository Merge Tool enables us to merge test objects from the local object repository of one or more actions to a shared object repository using the Update from Local Repository option in the Object Repository Manager.

For example, we may have learned test objects locally in a specific action in our test and want to add them to the shared object repository so they are available to all actions in different tests that use that object repository. We can also use the Object Repository Merge Tool to merge two shared object repositories into a single shared object repository.

We open the Object Repository Merge Tool by choosing Tools > Object Repository Merge Tool in the Object Repository Manager.

<<<<<< =================== >>>>>>

Q. 62: How can we perform Import & Export Operations among various Object Repositories?

We can import and export object repositories from and to XML files. XML provides a structured, accessible format that enables us to make changes to object repositories using the XML editor of our choice and then import them back into QTP.

We can import and export files either from and to the file system or a Quality Center project.

We can import an XML file as an object repository. The XML file can either be an object repository that we exported to XML format using the Object Repository Manager, or an XML file created using a tool such as QTP Siebel Test Express or a custom built utility. We must adhere to the XML structure and format.

<<<<<< =================== >>>>>>

Q. 63: How can we Integrate QTP with Quality Center?

We integrate QTP with Quality Center using the Quality Center Connectivity Add-in. This add-in is installed on our QTP computer automatically when we connect QTP to Quality Center using the Quality Center Connection dialog box. We can also install it manually from the Quality Center Add-ins page (available from the Quality Center main screen) by choosing Quality Center Connectivity.

Integrating QTP with Quality Center enables us to store and access QTP tests and function libraries in a Quality Center project, when QTP is connected to Quality Center.

<<<<<< =================== >>>>>>

Q. 64: What is the use of Template Tests in QTP?

Template tests serve as the basis for all QTP tests created in Quality Center. A template test is a QTP test that contains default test settings. For example, a template test might specify the QTP add-ins, associated function libraries, and recovery scenarios that are associated with a test. We can modify these test settings in the Test Settings dialog box (File > Settings) in QTP.

In addition to default test settings, a template test can also contain any comments or steps we want to include with all new QTP tests created in Quality Center. For example, we may want to add a comment notifying users which add-ins are associated with the template test, or we may want to add a step that opens a specific Web page or application at the beginning of every test. Any steps or comments we add to a template test are included in all new tests created in Quality Center that are based on that template test.

<<<<<< =================== >>>>>>

Q. 65: How can we create a QTP Test in Quality Center?

In Quality Center, we create QTP tests in the Test Plan module. When you create a QTP test, we apply a template test to it. We can choose either the default template test stored on our QTP client, or a template test that is saved in our Quality Center project.

If we do not have any template tests saved in our Quality Center project, or if we choose in the Template box, Quality Center uses the settings defined in the template test that was installed with the QTP Add-in for Quality Center on our Quality Center client.

<<<<<< =================== >>>>>>

Q. 66: What is Business Process Testing Model?

The Business Process Testing model is role-based, allowing non-technical Experts working in Quality Center to collaborate effectively with Automation Engineers working in QTP.

Non-technical Subject Matter Experts define and document business processes, business components, and business process tests, while Automation Engineers define the required resources and settings, such as shared object repositories, function libraries, and recovery scenarios. Together, they can build, data-drive, document, and run business process tests, without requiring programming knowledge on the part of the Non-technical Subject Matter Expert.

<<<<<< =================== >>>>>>

Q. 67: What is the role of Subject Matter Expert in the Business Process Testing Model?

The Subject Matter Expert has specific knowledge of the application logic, a high-level understanding of the entire system, and a detailed understanding of the individual elements and tasks that are fundamental to the application being tested.

This enables the Subject Matter Expert to determine the operating scenarios or business processes that must be tested and identify the key business activities that are common to multiple business processes.

During the design phase, the Subject Matter Expert works with the Automation Engineer to identify the resources and settings needed to automate the components, enabling the Automation Engineer to prepare them.

The Subject Matter Expert configures the values used for business process tests, runs them in test sets, and reviews the results. The Subject Matter Expert is also responsible for maintaining the testing steps for each of the individual business components.

While defining components, Subject Matter Experts continue collaborating with the Automation Engineer.

<<<<<< =================== >>>>>>

Q. 68: What is the role of Automation Engineer in the Business Process Testing Model?

The Automation Engineer is an expert in using an automated testing tool, such as QTP. The Automation Engineer works with the Subject Matter Expert to identify the resources that are needed for the various business process tests.

The Automation Engineer then prepares the resources and settings required for testing the features associated with each specific component, and stores them in an application area within the same Quality Center project used by the Subject Matter Experts who create and run the business process tests for the specific application.

The Automation Engineer uses QTP features and functionality to create these resources from within QTP.

<<<<<< =================== >>>>>>

Q. 69: What are the Differences Between Components and Tests?

# A component is a single entity. It cannot contain multiple actions or have calls to other actions or to other components.

# When working with components, all external files are stored in the Quality Center project to which we are currently connected.

# The name of the component node in the Keyword View is the same as the saved component. We cannot rename the node.

# Business components are created in the Keyword View, not the Expert View.

# We add resources via the component's application area, and not directly to the component.

# Components use custom keywords created in function libraries to perform operations, such as verifying property values and opening the application we are testing.

<<<<<< =================== >>>>>>

Q. 70: How can we compare objects among two object repositories?

In QTP, we can compare existing assets from two object repositories using the Object Repository Comparison Tool.

The tool is accessible from the Object Repository Manager, and enables us to compare different object repository resources, or different versions of the same object repository resource, and identify similarities, variations, or changes.

Differences between objects in the two object repository files, named the First and Second files, are identified according to default rules. During the comparison process, the object repository files remain unchanged.

After the compare process, the Comparison Tool provides a graphic presentation of the objects in the object repositories, which are shown as nodes in a hierarchy.

No comments: