If, for some reason, Rapise cannot learn an object, you can create a Simulated Object. Rapise identifies a simulated object by its location in the Window or Dialog and can perform certain generic actions on it, such as Click and Fill In. This works in the reverse sense also. That is, if Rapise cannot identify an object, or, for example, you click outside any defined object in the AUT's UI, Rapise will create a simulated object to represent the action

Simulated Objects are extremely helpful to test GUI controls that are not natively supported by Rapise. You may use them for testing desktop applications developed with:

  • Microsoft Visual C++ compiler
  • Microsoft .NET Framework compilers
  • Microsoft Visual Basic 6

The main prerequisite for using Simulated Objects is the application under test must support Microsoft Active Accessibility.

At the high level Simulated Object knows how to find associated GUI control within application (determine its bounding rectangle and window handle) and is able to simulate such user activities as keyboard input and mouse actions.