Rapise uses a heuristics-based approach to distinguish
meaningful activity from lower-level actions that can be ignored. In some cases
this leads to a result that some required user activity is not automatically
is easy to illustrate this with a simple mouse activity example. Suppose you
press the button using a mouse.
The low-level activity is as follows:
if we record the button as an object 'OK' and record all the activity in such a
low level the resulting script will contain at least following:
// Move mouse to the center of OK button
// Press left mouse button
// Wait a bit (50 msec)
// Release left mouse button
most cases such level of details is not actually needed. What we really need is
to have a concise description of the overall activity:
will just click on the center of the button.
There is a broad range of available UI platforms and
libraries. This variety of graphical widgets makes user interfaces responsive
and intuitive. Rapise tries to recognize as many of these objects as possible.
However this range is growing and there may be times when widgets in the AUT
are not recorded by Rapise.
This can sometimes happen with certain user interfaces. You can extract the
text using OCR
You can use the extensibility features of Rapise to create a
custom library that will be able
to recognize the new object.