{"id":986,"date":"2022-12-05T08:34:05","date_gmt":"2022-12-05T08:34:05","guid":{"rendered":"https:\/\/www.softwaretestingstuff.com\/?p=986"},"modified":"2023-03-06T06:17:47","modified_gmt":"2023-03-06T06:17:47","slug":"designing-test-object-configuration-xml-file-in-qtp","status":"publish","type":"post","link":"https:\/\/www.softwaretestingstuff.com\/2013\/09\/designing-test-object-configuration-xml.html","title":{"rendered":"Designing Test Object Configuration XML File in QTP"},"content":{"rendered":"\n
In this file, you define any custom test object classes that you want QTP to use to represent your custom controls in tests and components. Define a test object class for each custom control that cannot be adequately represented by an existing Delphi test object class. If the relevant add-in is not loaded when QTP opens, QTP does not load the information in this XML. Similarly, if the name of the environment or custom toolkit is displayed in the Add-in Manager dialog box and its check box is not selected, the information in this XML is not loaded.<\/p>\n\n\n\n A test object class definition can include the following:<\/strong><\/p>\n\n\n\n Note:<\/strong> You can also create a definition for an existing test object class in the test object configuration XML. This definition is added to the existing definition of this test object class, affecting all test objects of this class. It is therefore not recommended to modify existing test object classes in this way. In this file, you define any custom test object classes that you want QTP to use to represent your custom controls in tests and components. Define a test object class for each custom control that cannot be adequately represented by an existing Delphi test object class.In a test object configuration XML, you define the test […]<\/p>\n","protected":false},"author":1,"featured_media":2362,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"site-sidebar-layout":"default","site-content-layout":"","ast-site-content-layout":"","site-content-style":"default","site-sidebar-style":"default","ast-global-header-display":"","ast-banner-title-visibility":"","ast-main-header-display":"","ast-hfb-above-header-display":"","ast-hfb-below-header-display":"","ast-hfb-mobile-header-display":"","site-post-title":"","ast-breadcrumbs-content":"","ast-featured-img":"","footer-sml-layout":"","theme-transparent-header-meta":"","adv-header-id-meta":"","stick-header-meta":"","header-above-stick-meta":"","header-main-stick-meta":"","header-below-stick-meta":"","astra-migrate-meta-layouts":"default","ast-page-background-enabled":"default","ast-page-background-meta":{"desktop":{"background-color":"var(--ast-global-color-4)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"ast-content-background-meta":{"desktop":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"footnotes":""},"categories":[14],"tags":[],"table_tags":[],"class_list":["post-986","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-software-testing-certification"],"yoast_head":"\n
In a test object configuration XML, you define the test object classes (for example, their identification properties, the test object methods they support, and so on). To do this you define a ClassInfo<\/strong> element for each test object class. In addition, you define the name of the environment or custom toolkit for which the test object classes are intended (in the TypeInformation\\PackageName<\/strong> attribute), and the QTP add-in which these test object classes extend (in theTypeInformation\\AddinName<\/strong> attribute).<\/p>\n\n\n\n\n
If you add a test object method, it appears in the list of test object methods in QTP, but if you use the test object method in a test, and it is not implemented for the specific object, a run-time error occurs.
If you add test object methods to existing test object classes, you might add a prefix to the method name that indicates the toolkit support for which you added the method (for example, CustomButtonClick<\/strong>, CustomEditSet<\/strong>). This enables test designers to easily identify the custom methods and use them in test steps only if they know that the custom method is supported for the specific object.<\/p>\n","protected":false},"excerpt":{"rendered":"