ContributionsMost RecentMost LikesSolutionsRe: Object Spy problems We had a physical meeting with them about the subject, but they evaded the issue and talked about other stuff. And the meeting was limited time. Re: Object Spy problems I did not accept anything as a solution. Not sure why it is saying I did? Re: Object Spy problemsChrome = Version 104.0.5112.81 Edge = Version 103.0.1264.77 (Official build) (64-bit) NOTICE OF CONFIDENTIALITY: Information included in and/or attached to this transmission may be confidential. This transmission is intended for the addressee(s) only. Any unauthorized disclosure, reproduction, or distribution of and /or any unauthorized action taken in reliance on the information in this transmission is prohibited. If you believe that you received this transmission in error, please notify the sender by reply transmission and destroy the transmission without copying or disclosing it. We may also need to contact you for additional information as required by HIPAA or state law.Re: Object Spy problems We did get this response from smart Bear: 1. TestComplete v.14.93 and higher supports Edge v100 and higher. As of now we do not have any updates for TestComplete versions lower than 14.93 to support Edge v100 or higher. Object Spy problems As you know, IE was recently replaced with Edge. We also updated to Test Complete 14.93.312.7x64 Anyway now, when using Object Spy on Chrome and on Edge in IE mode, it does not work. It highlights in red the entire browser window, and won't drill down to individual objects (input boxes, buttons, etc) on the screen, though it still works on IE (for the few machines here that have IE), and seemingly on Exdge windows not in IE mode. Has anyone had this problem? TcCrHost.exe is running, and we have the TC extension. It seems also, when running Test Complete through C# it also cannot find objects. (We are running TC through C# in Visual Studio, but of course, Object Spy stands on its own). Re: Test Complete Edge VersionsYet? So they will in the future? NOTICE OF CONFIDENTIALITY: Information included in and/or attached to this transmission may be confidential. This transmission is intended for the addressee(s) only. Any unauthorized disclosure, reproduction, or distribution of and /or any unauthorized action taken in reliance on the information in this transmission is prohibited. If you believe that you received this transmission in error, please notify the sender by reply transmission and destroy the transmission without copying or disclosing it. We may also need to contact you for additional information as required by HIPAA or state law.Test Complete Edge Versions A search shows these versions of Edge supported by Test Complete: Microsoft Edge 83 - 99 (Chromium-based, both 32-bit and 64-bit versions) Was this made when 99 was the highest version, or or later versions of Edge not supported by Test Complete? It seemed to work at least partially with like 102. Re: Upgrade to TC 14 problems with Connect being null (Windows 10) hank you, everyone. Re: Upgrade to TC 14 problems with Connect being null (Windows 10) I did but no answer, which is why I entered here. Upgrade to TC 14 problems with Connect being null (Windows 10) We had a VS/TC test running (Visual Studio 11 and TC 12) which worked fine. I do a Connect.StopTest() to stop a test before doing the StartTest(). I surround the StopTest() with a try{} catch{} in case no test is running. We recently updated to TC14. Rebuilt everything and replaced those 3 Automated dll's with the TC14 ones.(when we first ran TC 14 it converted our project noted by "tpath" above to tc14): Occasionally, the test works, but most of the time at the lines Connect.StopTest() andConnect.RunTest(GetTestName(), "Generic", tpath); we get the following below (when we first ran TC 14 it converted our project noted by "tpath" above to tc14): Result Message: Initialization method ErepriceClassLibrary.NewReprice.Before threw exception. System.NullReferenceException: System.NullReferenceException: Object reference not set to an instance of an object.. Result StackTrace: at Multiplan.Scripts.WorkFlow.BaseClasses.AbstractTestCase.Before() in c:\VS_Projects\ERepricerTC14\EERepriceFrameworkClassLibrary\BaseClass\AbstractTestCase.cs:line 89 When I do a quickwatch on Connect it certainly is not null (see attached picture). Originally the StopTest() was in the Before() method but I moved it to the line before I start the test as I thought that would fix it. I can't understand why it says Connect is null. Anyone have an idea? See attached picture. Solved