My Actions are Not Recorded

By design Rapise tries to record user activity on the highest possible level. This makes recorded actions more readable and universal (often several lower-level user actions are combined)

Rapise uses a heuristics to distinguish meaningful activity from low level actions. In some cases this leads to a result that some user activity is not automatically recorded (for example, a mouse click before entering text in a box). There is a broad range of available UI platforms and libraries. The variety of graphical widgets makes user interface robust and beautiful. Rapise tries to recognize as much objects as possible. However this range is growing and there are always widgets that are not being recorded.

Nothing recorded, what's next?

Try to Learn an object using Learn. If the object is successfully learned then you may use the Recording Activity Dialog to simulate required behavior or you may compose the required behavior using the Objects Tree

So nothing learned

Try using Simulated Objects to learn your objects
Try using Analog Recording to deal with problematic object

Object is learned but not found during test play

This could mean that something in the application state has changed between recording and playback, make sure the starting conditions are the same. For example if you record a test that involves logging in, then before playing it back, make sure you have logged out.

Nothing helps, what's next?

Add Support for New Object (for advanced users with developer experience only).
Use the Rapise Forum to ask others if the issue is known

Spira Helps You Deliver Quality Software, Faster and With Lower Risk