Suppose we have a situation that a thick-client (desktop) application under test (AUT) is based on a technology
that is too old or not completely supported by Rapise. Rapise has a number of
libraries for different types of apps. Usually Rapise finds the correct libraries using its auto-detection, but sometimes an application is unusual and
the auto-detection fails.
When Auto-Detection FailsIn this case it is worth helping the Rapise Application Chooser find the best possible library for the application being tested.
We recommend that you try the following path:
- Select the "UIAutomation Object" Spy and try to inspect the
application. If the Spy shows the real content of the application (i.e. you see object names and IDs) then it is worth trying to record a test
with the corresponding library called "UIAutomation" - using the record application dialog box. This library is best for modern Windows application.
If the recording is not picked up or does not play back correctly then the
next step is to try recording with the "Generic" library. This is designed for older Windows Win32 applications. There is also a Spy tool for this library called the "Accessible Object" Spy.
If the recording is not sufficient then the last step is to try and record with
the "Advanced Accessibility" library. This library contains definitions of
accessible controls at a very basic level. It is not very sophisticated, but it is often sufficient for many cases and works across a wide range of applications.
If neither of options below satisfy then it may be worth to try low level