ContributionsMost RecentMost LikesSolutionsRe: v 15.75.22.7: 'Go to declaration' & 'Find usages' are missing FYI - The latest version of TestComplete (15.76.5.7) appears to have added these options back into the menus. Re: v 15.75.22.7: 'Go to declaration' & 'Find usages' are missing FYI - I am not sure if a ticket had been opened yet so I created one so the ball can get rolling on it. It's actually a really pain not to have those options. :) The ticket number created was '00711347' Re: v 15.75.22.7: 'Go to declaration' & 'Find usages' are missing I no longer see the 'Go to Declaration' option either. We just updated to 15.75.22.7. All I get now is Re: TestComplete logs for "passed" test cases no longer generate with Azure DevOps pipeline execution We are also seeing the logs not showing up for all tests (pass or fail) anymore. It does appear to be with the latest adapter update. I did see some tests that showed as passed but had attachments but, looking at the logs, there was a random Warning for finding of an object. Nothing that was an error but it must be seeing warnings as failures also, so it seems those are still attaching. Re: Azure Pipeline - Visual Studio Test - Test execute fails to run (but was working yesterday) We updated our DevOps Pipeline TestComplete Adapter to the latest version and we seem to be able to run our tests again. It appears they have fixed the issue. Re: Azure Pipeline - Visual Studio Test - Test execute fails to run (but was working yesterday) We have the same issue and also do not have the filter criteria option. Hopefully there will be a solution to this soon. Re: Azure DevOps Integration Test Execute version that is launched. Thanks rraghvani. I think I was running into a 'mix' of database bit versions. They have been converting things but, I don't think everything has been switched over yet. However, I am able to get things working now with some 64bit ODBC so, hopefully I can just continue down that path. Re: Azure DevOps Integration Test Execute version that is launched. I was wondering if I could rename one of those executables to try and 'trick it out' but, have not attempted that yet. I believe I have a 64bit ODBC query and setup that might work. I will just push all the setup down to the agents and hope I don't run into a conflict. If that doesn't work I will manipulate the agents more as Kitt suggested. Thanks everyone for the assistance. Re: Azure DevOps Integration Test Execute version that is launched. Thanks. I guess, we are just curious how to force a particular bit version when selecting the following in the 'TestComplete test adapter installer' (as in the image). Or, if we can confirm if the agent is setup as 32-bit, then TC/TE will be run as 32-bit. I think I will just focus on getting everything lined up with 64-bit versions. Thanks Re: Azure DevOps Integration Test Execute version that is launched. Those all appear to be 64 bit. We have a 32 application (slowly being converted) and that is why we're wanting to launch TestExecute in 32 bit so we could query Oracle 32 bit. Those images tell me about the Agent versions. I am just wanting to try and force TestExecute to be kicked of using the 32bit version.