Forum Discussion

dhundley's avatar
dhundley
Regular Contributor
2 years ago
Solved

TestExecute Settings Export

the smartbear support web page https://support.smartbear.com/testcomplete/docs/reference/options/exporting-user-settings.html explains how to export settings for TestComplete using Tools->Settings->E...
  • Kitt's avatar
    Kitt
    2 years ago

    Thanks for posting Smartbear's reply, that will help others with the same issue, and thanks for giving the file update a shot. Thankfully TestComplete gives us plenty of opportunities to create fun scripts. Although there are a fair share that are needed for "workarounds", the same could be said for most automation tools. Despite what TE is showing as correct, did you try to run any tests through those ports after saving the file? VM reboot wouldn't hurt either. 

     

    As for fun scripts, you can use a powershell script or batch file to open a port in your firewall so you don't have to do it manually every time. And it you want to go crazy, write another script to check for TE version updates, and if true execute the batch file. Here's a starting point for going down that rabbit hole: [open ports w/netsh] and [tc/te auto updates].

Kitt's avatar
Kitt
Regular Contributor

Gottcha, I would suggest contacting Support to see if there is a workaround. If this port configuration is stored somewhere within the local TC project files, then you could potentially create a script to update that file before your tests start.

 

So far I was only able to find a potential reference in the TC 14 Global.aqview file stored here >> C:\Users\<username>\AppData\Local\SmartBear\TestComplete\14.0. There's a section where this setting is configured - just search for value="Options - Network Suite (TestExecute)". See if you can update this file on your agent VM and rerun your test with the updated port.

 

 

 

dhundley's avatar
dhundley
Regular Contributor
2 years ago

i already did open a case with support. the solution they proposed was to go back through the port setup portion of the configuring windows firewall process and define the port range 6105 through 6107 so that the ports in the firewall match what testexecute is going to default to every time we have to install a new smartbear update. i replied back to them that, if it were just me, i'd do that, but i'd also have to explain what to do to several other people in my organization who have already defined the 6095 - 6097 port range in the firewalls of their workstations and VM's. who knows? i still might do that but i was hoping to find a quicker fix if one existed. 

 

as for your suggestion, i exited out of test execute on my testexecute agent VM, edited the numbers in the Global.aqview file from the correct values of 6095, 6096 and 6097 to 6105, 6106 and 6107, saved the changes and then started testexecute back up. when i went into tools-options-engines-network suite, they still reflected the correct values so it doesn't seem like changes to that file affect what comes up in testexecute (unless i did something wrong). would a Vm restart be required for the changes to take effect? I love the idea, though, if i could get it to work. i love creating scripts to do things. let me know if you can think of anything else. thanks!

  • Kitt's avatar
    Kitt
    Regular Contributor
    2 years ago

    Thanks for posting Smartbear's reply, that will help others with the same issue, and thanks for giving the file update a shot. Thankfully TestComplete gives us plenty of opportunities to create fun scripts. Although there are a fair share that are needed for "workarounds", the same could be said for most automation tools. Despite what TE is showing as correct, did you try to run any tests through those ports after saving the file? VM reboot wouldn't hurt either. 

     

    As for fun scripts, you can use a powershell script or batch file to open a port in your firewall so you don't have to do it manually every time. And it you want to go crazy, write another script to check for TE version updates, and if true execute the batch file. Here's a starting point for going down that rabbit hole: [open ports w/netsh] and [tc/te auto updates].