Your test failed to simulate some actions that open the needed window. It’s quite possible that the needed window or control, or some of its parent objects didn’t exist in the system at the needed time. The object didn’t exist at the time TestComplete tried to obtain it. See the description of the VideoRecorder extension for information on how to do this. A possible alternative is to record a video of your test run. You can find these images on the Picture tab of the test log. If the object exists, then, to find the cause of the error, explore properties of the problematic object:īy default, the test engine logs images of the tested application for every simulated test command to help you understand what happened in the application during the test run. If the object does not exist in the application, re-record your test or update its commands to match the tested application. See how it works.Īfter you select the object, the Object Spy will display its properties. If you need to select a hint, menu item or another popup object, use the “Point and fix” mode. You typically select a window or control by dragging the target icon ( ) to it. Use the Object Spy to select the needed object on the screen: ![]() In TestComplete, select Display Object Spy from the Tools toolbar. See instructions for desktop, mobile tests, and web tests that run on your local computer See instructions for desktop, mobile tests, and web tests that run on your local computer For example, earlier test steps have failed and the needed window or control didn’t appear on the screen, the parent object of the target object didn’t exist, the recognition attributes of the object changed, and so on (see the possible reasons below). The “Object Does Not Exist” message indicates that the tested application differs from the state it had during test recording or test creation. Otherwise, it will post the error message to the test log. Depending on whether the self-healing mode is enabled, it either uses the replacement object to continue the test run or posts information on the replacement object to the test log. If applicable, TestComplete will try to find an object similar to the missing one. If the recognition criteria match completely and the object is found, TestComplete executes the test command on it. To do this, it uses the recognition criteria set for the object in the Name Mapping repository. Before running a test command on some object, TestComplete first finds this object in the system. ![]() ![]() TestComplete considers processes, windows, and controls as objects.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |