The Action Recording feature can be used to quickly create test cases by simply reproducing the actions the test should take. However, there may be a situation where the recorded action does not play back during the test run as intended.
Although the Action Recorder is very useful in capturing basic control actions, there may be scenarios where controls would have to be mapped manually. An example of such a situation is shown below:
Notice how the click action has been recorded and the interface entity “main window” has been created. However, there is no value for the “control” argument. Instead, the click location is utilizing a coordinate value. This type of approach is not idea, since the coordinates of a control can vary based upon many different factors.
In order for the test to run properly, the control would need to be manually identified. You can find more information on how to map an interface entity here.