Update Test Execution version using command line (via Jenkins) or in any other way

[OV]

Hi,

We are running Test Execute on an Azure vm whcih is created automatically using an image, this image has Test Execute already installed but, since it was created long ago the Test Execute version is old. we are writing the scripts in Test Complete and update it frequesntly and at some point the versions are not matching, instead of creating each time a new image that will include the latest version of test execute I thought maybe there's a way to update the test execute silently on the original image once the vm is created and loading or to do it using command line or any other way via the Jenlkins pipeline?

If there's a way to update the existing version somehow it is great.

If the re's a way to install it from scratch after downloading the latest version on a clean win 10 vm that's alos good but, in this case we will need to update the following web page- Gemalto Sentinel ACC: Configuration of where the license server sits so it can fetch the floating license. and maybe to do it on the server side as well so maybe it is more complicated?

If anyone knows of a way to do that I'll be greatful.

Thanks,

Ofer 

[Marsha_R]

This may be useful

https://support.smartbear.com/testexecute/docs/general-info/installing/installing-in-silent-mode.htm...

[OV]

Thanks Marsha,

That is very helpful.

What should I do in case I want to download the latest version and then silent install it? Test Execute will not let me silent install isn't it? it will come up with the trail version and all that or it won't?

Is there an FTP address we can download it from?

Thanks

Ofer

[Marsha_R]

The silent installation works with any version.  The highlighted number here is the version number to be changed as needed.

There is more information here about updating TestExecute

https://support.smartbear.com/testexecute/docs/general-info/installing/maintaining/index.html

https://support.smartbear.com/testexecute/docs/general-info/updates/checking.

If you still have questions, then it's best to contact Support directly at this link:

https://support.smartbear.com/testcomplete/message

[OV]

Great , thanks

I tried to run the following command line - "C:\Program Files (x86)\SmartBear\TestExecute 14\Bin\AutoUpdate.exe" /InstallAvailablePatches but, when checking the test execute version again after the upgrade, it will show the same version as before but, on the other hand it won't prompt with updates availible pop up so, I'm not sure it really did upgraded test execute, it there a different parameters to the command? as it seems like this one (/InstallAvailablePatches) is only updating the patches.

Thanks

Ofer

[Marsha_R]

as it seems like this one (/InstallAvailablePatches) is only updating the patches.

That's because you picked the command line out of the "install patches" section and that's what it's supposed to do.  Go back to the silent install link that's in my first post and follow the instructions there. 

[OV]

Thanks,

The first step saying to deploy the 

TestExecute1481_release.exe file on the target machine, I guess they mean to have the latest TE build placed on the target machine right? we can't basically do that as we are creating the vm once the pipeline is running so, the target machine hasn't been created yet. is there way to download the latest TE installer via commandline as well? this way we can download it also via the pipeline before doing the upgrade.

Thanks,

Ofer

[OV]

Hi,

Ok, I've managed to do that using this commanline - powershell "Invoke-WebRequest -OutFile c:\\temp\\TestExecute1481.exe -Uri https://my.smartbear.com/downloads/TestExecute1481.exe" 

Now we have another issue, while installing the TE on the vm it seems to log off, is it because of something to do with the installer or is it more likely to be related to Azure? that happened when i tried to run it manually and also via Jenkins.

Thanks,

Ofer

[Marsha_R]

What is it that logs off and at what point in the process does that happen?

[OV]

Hi Marsha,

We understand where it came from now, it was a problem on our Jenkins server, nothing to do with the installer.

Thanks a lot for the help.

Ofer