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 many different object libraries. See the list of libraries and supported control types below.
Note: Selecting Auto as the application recording library will cause Rapise to select the one that it deems is most appropriate.
Note: You can add your own Recording library - one that understands the objects in your application.
Libraries¶
- Auto
- Generic
- UIAutomation
- Managed
- DevExpress
- Infragistics
- Syncfusion
- Telerik
- Advanced Accessibility
- ActiveX
- ActiveXC1
- ActiveXSft
- FarPoint
- VSFlexGrid
- Java
- SWT
- Qt
- Web
- HTML5
- Selenium
- jQuery
- GWT
- GWTExt
- DomSmartGwt
- YUI
- Web Services
- Mobile
- DynamicsAX
- DynamicsNAV
- NavPOSControls
- DomDynamicsNAV
- DomDynamicsAX
- DomDynamicsCrm
- DomSalesforce
See Also¶
- Recording
- To write an Object library specific to your application, see Custom Libraries.
- Cross Browser Testing
- If you interact with an object that is not defined in your chosen recording library, it will be treated as a Simulated Object.