ContributionsMost RecentMost LikesSolutionsRe: Slow performance while identifying the object properties Enabling extended search by default can indeed affect the performance. Use extended search for a control only if we cannot identify a parent control associated with the control uniquely( May be the properties that can be used to identify the control gets changed dynamically at run time). In this case we will try to define the object hierarchy based on a parent control which can be identified uniquely. This is accomplished by enabling Extended Search for the control and by dragging the control just under the parent control that can be identified uniquely. In this case what happens is that TC will try to locate the control at all level below the parent control that can be identified uniquely. This can have an impact on performance. Also we will have problem if we have more than one control having the same set of property any where in the hierarchy below parent control. Re: I was wondering how to test (check properties) windowless objects such as this one. Can you please add a screen shot of what is returned on applying ObjectSpy over the pop up? What do we mean by Object spy was not able to identify it? Is the pop up basically a grid control? Re: How to change property of an object in run time while executing the test. "Top of object" property is not a good choice for identifying the control uniquely. If we cannot use the wndCaption because of multilanguage support we should try to identify another set of properties using which the control can be identified uniquely. If it it not possible to do this with out the language dependent properties we need to use the name mapping configuration feature in test complete. Using this we can use different namemapping configuration for each language and this name mapping configuration selection can be done from script using the NameMapping.CurrentConfigurationName = Namemapping configuration name script. More info can be found in https://support.smartbear.com/testcomplete/docs/testing-with/object-identification/name-mapping/configurations/switching.html Re: Failure in playback but successful record!! I guess the problem is related to automatic name mapping used while recording the script. While recording test complete will select a set of properties using which it guess it can identify the control uniquely during playback. But this will not be the case during playback. We can see the properties test completes selected to identify it from the name mapping file. Now we can run the application and right click over the control in name mapping tree and select Highlight on screen. The control will be highlighted over the UI if it can be identified uniquely. If we cannot identify the control, use the Object spy and drag over the control and identify the property that got a different value compared to name mapping file. Remove this property and try to identify a set of properties using which the control can be identified uniquely. Best practice might be to map the control manually to the namemapping file and then do a record if at all required Re: TestComplete Name Mapping Issues - Microsoft Dynamics CRM 2016 I think we should use Extended find only if one or more of the parent components in the object hierarchy cannot be identified uniquely(For EG : Property values get changed dynamically). In this case we will identify a parent object that can be identified uniquely and will enable Extended Find for the child object we are trying to map and child will be dragged and placed under the parent control that can be identified uniquely. But this have the following short falls : It will search all the child controls under the parent control that can be uniquely identified for a match which will be indeed time consuming. Also this approach will have an issue if we have more than one control matching the property value selected for the child control even at a different object hierarchy Re: Identical Instances of an Object in same window - Same Mapped Name. The two controls are having different object hierarchy. We can see this clearly in the Object Browser. If we map both the controls starting from their highest level parent control we can see that at some level both the controls will have a different parent and hence we will be able to identify the controls uniquely if we can find properties combination that can identify this parent control uniquely Re: Running the GeneralEvents_OnStopTest event Events are triggered automatically when some conditions are met. For Eg : OnLogerror, OnUnexpectedwindow etc. They are used to manage things that happens dynamically during runtime. For example if we need to do something specific when a error is logged. We don't know when this is going to happen. When ever an error is logged from any part of the project suite this even will be triggered. 2. At the endo of the test suite/start of a test suit. : We exactly does know when this is going to happen and we candefined a method that can perform the actions to be done and just call those at the Start/End of test suite. Hope this helps 3. At the end of an individual test run/start of an individual test run. We exactly does know when this is going to happen and we candefined a method that can perform the actions to be done and just call those at the Start/End of test suite. Hope this helps Re: object recognition problem in 11.31 Can you please check how these controls are shown in object browser in the two condition? Please check if there is a change in hirarchy of the object when we try to focus it a second time after clicing over the link Re: Issues with Aliases when using objects with groupboxes We sholud use only unique property associated with the control to map the control. In your case the WndCaption property gets changed depending on some other changes. So we shoult not use that property to identify the control. Instead we should identify the properties that are not changed even if we add or delete rows in child datagridview. Hope this helps Re: With error message "The process ... was not found" Runner.Stop(true) stop the whold test. .Is it a good idea to check whether the tested app is still running before calling the Runner.stop call? If(myprocess.Exists) { Runner.Stop(true) }