{"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.
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

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