ContributionsMost RecentMost LikesSolutionsRe: Unable to load content document in Object Browser We use the Script.eval functionality of contentDocument, and experienced the same issue where it stopped working in version 15.58 (and also 15.59). I opened a case over a week ago. Perhaps open a case with them as well. Re: Changing xpath trying to wildcard it possible? As indicated you cannot use a dynamic number in the namemap. You could use it in code and make a call to FindElement. However, it appears as if the data you are looking for is in a table that can change. Additionally any xpath with something such as //td/th[64] means that it is looking for the 64th instance of that object within the HTML. In my opinion, this xpath is very susceptible to changes (especially if it is in a table). I would not map objects in a table, but rather write code that can be used to find the items that you are looking for. Re: Bug with the "improve performance" message ? This feature has never worked for me since it was first introduced many months ago. If I have 2 options in my selectors (XPaths) and switch to what is suggested, I get the same or an opposite error. Here is a link to a thread that discusses this and also a work-around about how to suppress the messages: https://community.smartbear.com/t5/TestComplete-Questions/Remove-the-quot-improve-your-test-performance-quot-in-test-log/m-p/236940 IMO this feature has never worked and there should be an option to disable the checking for the performance improvement all together rather than test Complete to spend time identifying an improvement that is not correct and then having to ignore/suppress the messages to the log file. Re: Repeat Exists (Avoid Writing Log Errors) Python I think the call to FindElement is probably the one that is logging the error. You can use other alternatives such as FindElementsand then get a list of elements (list would contain nothing in this case) and go from there. I do agree that when FindElement cannot find something it logging an error is problematic, and it would be good if they had an optional parameter to log an error or not. Re: Test compete does not communicating with Chrome. It might be related to the issue with https://community.smartbear.com/t5/TestComplete-Questions/TestComplete-issues-with-Chrome-113/m-p/249733#M108752 Re: Problems with TestComplete 15 and Chrome 113 We have been encountering Memory Issues since late January. With specific tests the memory issues happen probably about 80% of the time. Other tests they do not happen at all. The symptoms we see is that at a certain point the memory being used by Chrome increases rather rapidly until it crashes the system (or we kill Chrome). We currently have an open case, but have not heard much. And specifically related to this thread, I tried to see which version of Chrome was installed and as soon as I went into About Chrome I saw that it was 112, but it immediately started updating. Re: Chrome updated, now TC can't find browser I am getting similar issues with Chrome 113 as well. Re: Python Arrays Not sure if this is causing any of the issues or not, but the string you provided a = ["one', "two", "three", "four"] contains a single quote after one instead of a double quote. Re: Remove the "improve your test performance" in test log Kittit appears that this ability to enable/disable steps is for keyword tests. We are using Scripted tests. Is there something similar for Scripted tests that you know of? Re: Remove the "improve your test performance" in test log Tried adding the event handler as suggested by Kittand it works. Good to know that we can get around this issue that SmartBear has created. TestComplete, should really have an option to turn off the checking of the performance and producing the error in the first place. So, now there are checks for optimization, (that will make the current code slower for all XPath lookups). We do not want those all the time. It is good to have the capability, but allow us to turn them off/on as desired. IMO the event handler is a work around.