How to solve the problem that AutoRunner found that the object could not be recorded in the process of recording script

Sometimes, when we use AR for automated testing, we will find that some objects can not be recorded by conventional methods. At this time, we can use AR to forcibly acquire objects to achieve object acquisition. Then use the drag-and-drop method in view mode to add objects to the editing area of the script, which can solve the situation in which most objects cannot be recorded! Let's take a look at how it works:

1. Suppose I was recording a script for the login page of the system under test and found that the input box of the password could not be recorded, so we need to hold down the ctrl and alt keys at the same time, drag the mouse to the location of the object, until a red box appears on the object, and the object is acquired by us.

The object acquired here will be saved directly to the object library, and the script generates comments. In this case, we need to drag and drop the object in the view to the script editing area:

Then change the object's operation "clickControl" to "setValue":

Then execute the script:

The manual recording of the object was successful and the script was executed successfully!