Contributions
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.472Views0likes0CommentsRe: 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.486Views1like0CommentsRe: 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.517Views0likes0CommentsRe: 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. Thanks1KViews0likes2CommentsRe: 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.1.1KViews0likes4CommentsRe: Azure DevOps Integration Test Execute version that is launched.
Hi rraghvani, Yes, we have used those instructions to get things running and currently have tests running fine. We are just not seeing where in the TestComplete Adapter we can tell it which bit version to launch. We are adding some Oracle query functionality and getting errors referring to having different 'bit versions'. We are not seeing how to specify which version to run in the adapter. Can we remove the 64bit version from our agents and then it will default to 32bit? Or vice versa? The option 'Preferred test runner' allows the selection of 'TestExecute' or 'TestComplete' but, we are not seeing how we can specify what bit version to run or, how to force it to run 32 or 64 bit. Thanks1.1KViews0likes0CommentsAzure DevOps Integration Test Execute version that is launched.
When integrating with Azure DevOps using the TestComplete Test Adapter, you select the 'Preferred test runner' of either 'TestExecute' or 'TestComplete'. Where would we specify whether the 32bit or 64bit version should be run? Thanks Brad KnutsonSolved1.7KViews0likes14Comments