This page is maintained for older versions of Rapise only. The latest documentation can be found at: https://rapisedoc.inflectra.com
Object Libraries

Purpose

Object libraries define what objects and interactions Rapise understands during Recording and Learning.  Most Object Libraries are specific to an application or a set of applications.

 

Usage

Rapise comes with several different object libraries:

1.Auto

2.Core Technologies

oGeneric

oInternet Explorer HTML

oFirefox HTML

oJava

oJava SWT

oManaged

oUI Automation

oQt Framework

oActiveX

oWeb Services

oUser

oAdvanced Accessibility

oConsole

3.Mobile Libraries

oAndroid (via. Appium)

oiOS (via. Applium)

4.Widget Toolkits

oDOM Dynamics CRM

oDOM GWT

oDOM GWT-Ext

oDOM SmartGWT

oDOM YUI

oDOM jQuery UI

oHTML 5

oDevExpress

oInfragistics

oTelerik

oActiveX ComponentOne

oSyncFusion

oFarPoint

oDynamics AX

You can add your own Recording library--one that understands the objects in your application.

 

Selecting Auto as the application recording library will cause Rapise to select the one that it deems is most appropriate.

UIAutomation: Use this library with .NET, WPF, and Silverlight applications. When used with .NET 2.0+ applications you should also include the Managed library as well. When used with older .NET applications, you should use the Generic library instead.

Internet Explorer HTML , Chrome HTML and Firefox HTML are used with Internet Explorer, Google Chrome and Firefox respectively.  They understand only the DOM (document object model) and therefore capture interactions with the web application, not the browser.  They also have access to passwords.  Tests recorded with either of the libraries can be run in any of the three browsers.  See Cross Browser Testing for more details.

User refers to Custom Libraries.

The DOM GWT library uses the Document Object Model to learn or record objects found in the Google Web Toolkit.

The DOM GWT-Ext library uses the Document Object Model to learn or record objects found in the Google GWT-Ext library.

The DOM SmartGWT library uses the Document Object Model to learn or record objects found in the Google SmartGWT library.

The DOM jQuery UI library uses the Document Object Model to learn or record objects found in the jQuery UI widget library.

The HTML5 library uses the Document Object Model to learn or record objects found in the HTML 5 extensions library.

The DOM YUI library uses the Document Object Model to learn or record objects found in the Yahoo! User Interface library.

The Generic library uses Microsoft's MSAA event model to capture user actions. The Generic library should be used if there is no library more specific to the AUT available.  The Generic library will record a large set of applications, but it has drawbacks; it may skip some actions and/or record unintended actions.  Passwords are not visible to the Generic library, and must be manually entered into the test after recording.

The Advanced Accessibility library is for recording with Internet Explorer.  In general, you will want to use the Internet Explorer HTML library.  However, there is some information available through Advanced Accessibility that is unavailable when looking solely at the DOM.  For example: the absolute screen position of an object.  Advanced Accessibility is not precise, as Internet Explorer HTML is, and may miss actions or record unintended actions.

The Java SWT library is for use with the Eclipse Java Standard Widget Toolkit (SWT) applications.

The Console library is for use with Windows Console Applications that run in the command-line.

The Java library is for use with Java GUI applications that are written using either AWT or SWING. Use the SWT library instead if your application was written using SWT.

The Managed library is for use with Microsoft .NET 2.0 + applications. It adds some additional .NET 2.0+ specific-controls to the list supported in the Generic and UIAutomation libraries.

The DevExpress library allows you to record and learn using the various controls provided in the DevExpress DXperience v1.0 component library. This allows you to save time by having the system recognize the various controls directly.

The Infragistics library allows you to record and learn using the various controls provided in the Infragistics component library. This allows you to save time by having the system recognize the various controls directly.

The Telerik library allows you to record and learn using the various controls provided in the Telerik RadControls for Winforms component library. This allows you to save time by having the system recognize the various controls directly.

The Qt Framework library is for use with applications that are written using the cross-platform Qt Framework.

 

·The Web Services library is for use with API tests that connect to either REST or SOAP web services. See the web service testing topic for more information.

·The Dynamics AX library is for use with the Microsoft Dynamics AX ERP package. See the Dynamics AX topic for more information

·The DOM Dynamics CRM library is for use with the Microsoft Dynamics CRM package. See the Dynamics CRM topic for more information

 

See Also

Recording

To write an Object library specific to your application, see Custom Libraries.

If you interact with an object that is not defined in your chosen recording library, it will be treated as a Simulated Object.