Forum Discussion

bknutson's avatar
bknutson
Contributor
3 years ago
Solved

Azure 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 ...
Integrations
  • bknutson's avatar
    bknutson
    3 years ago

    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.

bknutson's avatar
bknutson
Contributor
3 years ago

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's avatar
Kitt
Regular Contributor
3 years ago

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's avatar
    bknutson
    Contributor
    3 years ago

    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's avatar
      Kitt
      Regular Contributor
      3 years ago

      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's avatar
        bknutson
        Contributor
        3 years ago

        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