Azure DevOps Integration Test Execute version that is launched.

[bknutson]

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 Knutson

[rraghvani]

Have you read through Integration With Azure DevOps and Team Foundation Server via TestComplete Test Adapter ?

[bknutson]

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.

Thanks

[rraghvani]

If you see https://learn.microsoft.com/en-us/azure/devops/pipelines/agents/v2-windows?view=azure-devops, section Download and configure the agent mentions changing the processor architecture to either x86 or x64 of the agent.

[bknutson]

All of the agents have Windows 64 bit on them.  But, are you thinking that if the Agent is setup as x86, then when TestExecute is kicked off, it will run the 32 bit version?

[Kitt]

you should see what bitness is used in your vs test task log:

or go to your agent pools in Azure and check the capabilities from there:

[bknutson]

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.

[Kitt]

You would need to reconfigure your agent to use 32 bit or create a new agent; all tasks run under that agent should be performed under the same bitness. The x64 agent version is intended for 64-bit Windows, whereas the x86 version is intended for 32-bit Window - found in the link @rraghvani provided.

You could also look into using Session Creator w/command line parameters [here]. More info on TC bitness [here].

[bknutson]

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

[Kitt]

So, you can force the runner to use either 32/64 (command line parameters, session creator, envt variable, agent config, etc). You can also tell which version the runner is using from the screenshots I provided - just open your own agent pool config in Azure DevOps (under Project Settings > Agent Pools).

TestComplete x86 & TestComplete x64 can test both 32-bit and 64-bit applications, so maybe I'm not entirely sure what your goal is or how we can help clarify?